Christine Poerschke created SOLR-13366:
------------------------------------------
Summary: 'Invalid stage name' warnings after upgrade
Key: SOLR-13366
URL: https://issues.apache.org/jira/browse/SOLR-13366
Project: Solr
Issue Type: Bug
Components: AutoScaling
Reporter: Christine Poerschke
I noticed WARNings like this in some of our logs:
{code:java}
... OverseerAutoScalingTriggerThread ... o.a.s.c.s.c.a.AutoScalingConfig
Invalid stage name '.auto_add_replicas.system' in listener config, skipping:
{beforeAction=[], afterAction=[], trigger=.auto_add_replicas, stage=[WAITING,
STARTED, ABORTED, SUCCEEDED, FAILED, BEFORE_ACTION, AFTER_ACTION],
class=org.apache.solr.cloud.autoscaling.SystemLogListener}
{code}
After some detective work I think I've tracked this down to 7.1.0
[TriggerEventProcessorStage|https://github.com/apache/lucene-solr/blob/releases/lucene-solr/7.1.0/solr/solrj/src/java/org/apache/solr/client/solrj/cloud/autoscaling/TriggerEventProcessorStage.java]
having a {{WAITING}} stage and that stage having been removed in 7.2.0
[TriggerEventProcessorStage|https://github.com/apache/lucene-solr/blob/releases/lucene-solr/7.2.0/solr/solrj/src/java/org/apache/solr/client/solrj/cloud/autoscaling/TriggerEventProcessorStage.java]
via the SOLR-11320 changes. Haven't tried to reproduce it but my theory is
that the listener got auto-created (with the {{WAITING}} stage) when the cloud
was running pre-7.2.0 code and then after upgrading the warnings start to
appear.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
