lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cao Manh Dat (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-11269) Node gone after reconnecting to ZK
Date Tue, 22 Aug 2017 10:31:00 GMT

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

Cao Manh Dat updated SOLR-11269:
--------------------------------
    Attachment: SOLR-11269.patch

Updated patch, in some test, CoreContainer.load() never being called, therefore ZkContainer.coreZkRegister
never being initialized. This patch add a null check inside ZkContainer.close()

> Node gone after reconnecting to ZK
> ----------------------------------
>
>                 Key: SOLR-11269
>                 URL: https://issues.apache.org/jira/browse/SOLR-11269
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Cao Manh Dat
>            Assignee: Cao Manh Dat
>         Attachments: SOLR-11269.patch, SOLR-11269.patch
>
>
> I have seen some failures, related to {{ZkController.OnReconnect}} that made the node
"gone" ( it is not present in "/live_nodes" ). In fact any exception during {{OnReconnect.command()}}
execution will made the node "gone". Some of them are
> - {{ZkController.createEphemeralLiveNode()}} can throw NodeExistsException
> - {{OutOfMemoryError : unable to create new native Thread}} during adding core to {{executorService}}
for recovering



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message