[jira] [Updated] (SOLR-8837) Duplicate leader elector node detection is broken

2016-05-10 Thread Hoss Man (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-8837:
---
Fix Version/s: master (7.0)
   6.1


Manually correcting fixVersion per Step #S6 of LUCENE-7271


> Duplicate leader elector node detection is broken
> -
>
> Key: SOLR-8837
> URL: https://issues.apache.org/jira/browse/SOLR-8837
> Project: Solr
>  Issue Type: Bug
>Affects Versions: 6.0
>Reporter: Alan Woodward
>Assignee: Alan Woodward
> Fix For: 5.5.1, 6.0, 6.1, master (7.0)
>
> Attachments: SOLR-8837.patch
>
>
> LeaderElector.checkIfIAmLeader checks to see if it has duplicate 
> registrations in under its election node, but it does this by prefix 
> checking, which means that if core_node1 registers itself after core_node11, 
> it will think it's a duplicate, and delete the core_node11 node.
> This is causing regular failures in UnloadDistributedZkTest.



--
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-8837) Duplicate leader elector node detection is broken

2016-04-21 Thread Anshum Gupta (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anshum Gupta updated SOLR-8837:
---
Fix Version/s: 5.5.1

> Duplicate leader elector node detection is broken
> -
>
> Key: SOLR-8837
> URL: https://issues.apache.org/jira/browse/SOLR-8837
> Project: Solr
>  Issue Type: Bug
>Affects Versions: master, 6.0
>Reporter: Alan Woodward
>Assignee: Alan Woodward
> Fix For: 6.0, 5.5.1
>
> Attachments: SOLR-8837.patch
>
>
> LeaderElector.checkIfIAmLeader checks to see if it has duplicate 
> registrations in under its election node, but it does this by prefix 
> checking, which means that if core_node1 registers itself after core_node11, 
> it will think it's a duplicate, and delete the core_node11 node.
> This is causing regular failures in UnloadDistributedZkTest.



--
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-8837) Duplicate leader elector node detection is broken

2016-03-13 Thread Scott Blum (JIRA)

 [ 
https://issues.apache.org/jira/browse/SOLR-8837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Blum updated SOLR-8837:
-
Attachment: SOLR-8837.patch

Seems like a pretty simple fix for the exact case you mentioned.  But you're 
right about this being a weird edge case; I definitely don't fully understand 
why it's there.

> Duplicate leader elector node detection is broken
> -
>
> Key: SOLR-8837
> URL: https://issues.apache.org/jira/browse/SOLR-8837
> Project: Solr
>  Issue Type: Bug
>Affects Versions: master, 6.0
>Reporter: Alan Woodward
> Attachments: SOLR-8837.patch
>
>
> LeaderElector.checkIfIAmLeader checks to see if it has duplicate 
> registrations in under its election node, but it does this by prefix 
> checking, which means that if core_node1 registers itself after core_node11, 
> it will think it's a duplicate, and delete the core_node11 node.
> This is causing regular failures in UnloadDistributedZkTest.



--
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