[jira] [Updated] (SOLR-9030) The 'downnode' command can trip asserts in ZkStateWriter
[ https://issues.apache.org/jira/browse/SOLR-9030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-9030: --- Fix Version/s: (was: 6.0) master (7.0) > The 'downnode' command can trip asserts in ZkStateWriter > > > Key: SOLR-9030 > URL: https://issues.apache.org/jira/browse/SOLR-9030 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Reporter: Shalin Shekhar Mangar >Assignee: Shalin Shekhar Mangar > Fix For: 6.1, master (7.0) > > Attachments: SOLR-9030.patch, SOLR-9030.patch > > > While working on SOLR-9014 I came across a strange test failure. > {code} >[junit4] ERROR 16.9s | > AsyncCallRequestStatusResponseTest.testAsyncCallStatusResponse <<< >[junit4]> Throwable #1: > com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an > uncaught exception in thread: Thread[id=46, > name=OverseerStateUpdate-95769832112259076-127.0.0.1:51135_z_oeg%2Ft-n_00, > state=RUNNABLE, group=Overseer state updater.] >[junit4]> at > __randomizedtesting.SeedInfo.seed([91F68DA7E10807C3:CBF7E84BCF328A1A]:0) >[junit4]> Caused by: java.lang.AssertionError >[junit4]> at > __randomizedtesting.SeedInfo.seed([91F68DA7E10807C3]:0) >[junit4]> at > org.apache.solr.cloud.overseer.ZkStateWriter.writePendingUpdates(ZkStateWriter.java:231) >[junit4]> at > org.apache.solr.cloud.Overseer$ClusterStateUpdater.run(Overseer.java:240) >[junit4]> at java.lang.Thread.run(Thread.java:745) > {code} > The underlying problem can manifest by tripping the above assert or a > BadVersionException as well. I found that this was introduced in SOLR-7281 > where a new 'downnode' command was added. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9030) The 'downnode' command can trip asserts in ZkStateWriter
[ https://issues.apache.org/jira/browse/SOLR-9030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-9030: Summary: The 'downnode' command can trip asserts in ZkStateWriter (was: The 'downnode' command can trip asserts in ZkStateWriter or cause BadVersionException in Overseer) > The 'downnode' command can trip asserts in ZkStateWriter > > > Key: SOLR-9030 > URL: https://issues.apache.org/jira/browse/SOLR-9030 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Reporter: Shalin Shekhar Mangar > Fix For: 6.1, master > > Attachments: SOLR-9030.patch, SOLR-9030.patch > > > While working on SOLR-9014 I came across a strange test failure. > {code} >[junit4] ERROR 16.9s | > AsyncCallRequestStatusResponseTest.testAsyncCallStatusResponse <<< >[junit4]> Throwable #1: > com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an > uncaught exception in thread: Thread[id=46, > name=OverseerStateUpdate-95769832112259076-127.0.0.1:51135_z_oeg%2Ft-n_00, > state=RUNNABLE, group=Overseer state updater.] >[junit4]> at > __randomizedtesting.SeedInfo.seed([91F68DA7E10807C3:CBF7E84BCF328A1A]:0) >[junit4]> Caused by: java.lang.AssertionError >[junit4]> at > __randomizedtesting.SeedInfo.seed([91F68DA7E10807C3]:0) >[junit4]> at > org.apache.solr.cloud.overseer.ZkStateWriter.writePendingUpdates(ZkStateWriter.java:231) >[junit4]> at > org.apache.solr.cloud.Overseer$ClusterStateUpdater.run(Overseer.java:240) >[junit4]> at java.lang.Thread.run(Thread.java:745) > {code} > The underlying problem can manifest by tripping the above assert or a > BadVersionException as well. I found that this was introduced in SOLR-7281 > where a new 'downnode' command was added. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9030) The 'downnode' command can trip asserts in ZkStateWriter or cause BadVersionException in Overseer
[ https://issues.apache.org/jira/browse/SOLR-9030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-9030: Attachment: SOLR-9030.patch I made the znode version final as well. I'll commit this now. > The 'downnode' command can trip asserts in ZkStateWriter or cause > BadVersionException in Overseer > - > > Key: SOLR-9030 > URL: https://issues.apache.org/jira/browse/SOLR-9030 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Reporter: Shalin Shekhar Mangar > Fix For: 6.1, master > > Attachments: SOLR-9030.patch, SOLR-9030.patch > > > While working on SOLR-9014 I came across a strange test failure. > {code} >[junit4] ERROR 16.9s | > AsyncCallRequestStatusResponseTest.testAsyncCallStatusResponse <<< >[junit4]> Throwable #1: > com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an > uncaught exception in thread: Thread[id=46, > name=OverseerStateUpdate-95769832112259076-127.0.0.1:51135_z_oeg%2Ft-n_00, > state=RUNNABLE, group=Overseer state updater.] >[junit4]> at > __randomizedtesting.SeedInfo.seed([91F68DA7E10807C3:CBF7E84BCF328A1A]:0) >[junit4]> Caused by: java.lang.AssertionError >[junit4]> at > __randomizedtesting.SeedInfo.seed([91F68DA7E10807C3]:0) >[junit4]> at > org.apache.solr.cloud.overseer.ZkStateWriter.writePendingUpdates(ZkStateWriter.java:231) >[junit4]> at > org.apache.solr.cloud.Overseer$ClusterStateUpdater.run(Overseer.java:240) >[junit4]> at java.lang.Thread.run(Thread.java:745) > {code} > The underlying problem can manifest by tripping the above assert or a > BadVersionException as well. I found that this was introduced in SOLR-7281 > where a new 'downnode' command was added. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-9030) The 'downnode' command can trip asserts in ZkStateWriter or cause BadVersionException in Overseer
[ https://issues.apache.org/jira/browse/SOLR-9030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-9030: Attachment: SOLR-9030.patch Patch which uses Integer.MAX_VALUE as the default znodeVersion and removes the assert in ZkStateWriter. The 'downnode' still has the problem that I described above but with this patch it will cause a BadVersionException which the Overseer is designed to recover from. > The 'downnode' command can trip asserts in ZkStateWriter or cause > BadVersionException in Overseer > - > > Key: SOLR-9030 > URL: https://issues.apache.org/jira/browse/SOLR-9030 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Reporter: Shalin Shekhar Mangar > Fix For: 6.1, master > > Attachments: SOLR-9030.patch > > > While working on SOLR-9014 I came across a strange test failure. > {code} >[junit4] ERROR 16.9s | > AsyncCallRequestStatusResponseTest.testAsyncCallStatusResponse <<< >[junit4]> Throwable #1: > com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an > uncaught exception in thread: Thread[id=46, > name=OverseerStateUpdate-95769832112259076-127.0.0.1:51135_z_oeg%2Ft-n_00, > state=RUNNABLE, group=Overseer state updater.] >[junit4]> at > __randomizedtesting.SeedInfo.seed([91F68DA7E10807C3:CBF7E84BCF328A1A]:0) >[junit4]> Caused by: java.lang.AssertionError >[junit4]> at > __randomizedtesting.SeedInfo.seed([91F68DA7E10807C3]:0) >[junit4]> at > org.apache.solr.cloud.overseer.ZkStateWriter.writePendingUpdates(ZkStateWriter.java:231) >[junit4]> at > org.apache.solr.cloud.Overseer$ClusterStateUpdater.run(Overseer.java:240) >[junit4]> at java.lang.Thread.run(Thread.java:745) > {code} > The underlying problem can manifest by tripping the above assert or a > BadVersionException as well. I found that this was introduced in SOLR-7281 > where a new 'downnode' command was added. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org