[
https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Blum updated SOLR-8696:
-
Attachment: SOLR-8696-followup.patch
> Start the Overseer before actions that need the overseer on init
[
https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Blum updated SOLR-8696:
-
Attachment: (was: SOLR-8696-followup.patch)
> Start the Overseer before actions that need the overseer
[
https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Blum updated SOLR-8696:
-
Attachment: SOLR-8696-followup.patch
> Start the Overseer before actions that need the overseer on init
[
https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-8696:
--
Attachment: SOLR-8696.patch
New patch. Fixes the same overseer situation on zk reconnect (I've seen the
[
https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-8696:
--
Summary: Start the Overseer before actions that need the overseer on init
and when reconnecting after zk