855298 - Change elasticsearch indexing for the 2008 processor

Status: RESOLVED WONTFIX

(Socorro :: Backend, task, P1)

Description

[[DEACTIVATED] Adrian Gaudebert]

We're still using the old, 2008 processor in stage and production. As we want to turn elasticsearch on asap, we need to port the elasticsearch changes to the old processor.

Comment 1

[K Lars Lohn [:lars] [:klohn]]

the processor currently in use is the Chimera Processor: an amalgam of both the 2008 and 2012 processors.  It uses the old system configuration at .../scripts/config/processorconfig.py.   Within that configuration is an option to select either the 2008 or 2012 algorithm.  With the default at 2008, the processor uses the algorithms of the old processor with the new processor's back end storage.  It uses the old style ES method.  If you switch the algorithm to 2012, it is essentially the new processor that uses the latest ES codebase.  To accomplish running the new processor with the old configuration, the .../scripts/startProcessor.py adapts the old configuration to the new configman style standards.

If you update the  .../scripts/config/processorconfig.py to the new ES style, modify .../scripts/startProcessor.py to copy the config into configman (see other values for examples), then select the 2012 algorithm in that config, you can likely get away without having to backport your new ES stuff to the old processor. 

Please note that the actual new 2012 processor (not the Chimera) is slated to go to staging this week and then on to production next week.  If that schedule is quick enough for your deadlines, you might be able to just wait and do nothing and ES will make it into production next week.

Comment 2

[[DEACTIVATED] Adrian Gaudebert]

processor2012 is coming on stage/production sooner than we expected -- there is no need to do this. Hopefully.