[
https://issues.apache.org/jira/browse/GEODE-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337596#comment-16337596
]
Vahram Aharonyan commented on GEODE-4322:
-----------------------------------------
Hi [~bschuchardt],
Thanks for the info.
Actually yes, we are shutting down whole cluster.
BTW, lets assume we have 2 locators(Loc-1 and Loc-2). We stop Loc-1 and remove
its dat file before start (while Loc-2 remains alive) , will this cause
problems? Or we should remove all the dat files from all locator nodes only
when whole cluster is powered off?
Thanks,
Vahram.
> Locator fails to start with NPE during join to the distributed system
> ---------------------------------------------------------------------
>
> Key: GEODE-4322
> URL: https://issues.apache.org/jira/browse/GEODE-4322
> Project: Geode
> Issue Type: Bug
> Components: membership
> Affects Versions: 1.2.0
> Reporter: Vahram Aharonyan
> Assignee: Bruce Schuchardt
> Priority: Major
>
> Found out that after setting security-udp-dhalgo=AES:128 in prorperties files
> sometimes locator is failing to come online with the following Exception:
> [severe 2018/01/19 04:22:12.194 PST <locator request thread[20]> tid=0x45]
> Exception in processing request from 10.144.248.41
> java.lang.RuntimeException: Not found public key for member
> 16nodedata6(d4b4f5d4-47d2-44b1-a07c-6a7f5755e52d:11493)<ec><v2>:10002
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:177)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger.getPublicKey(JGroupsMessenger.java:1365)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processRequest(GMSLocator.java:271)
> at
> org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1256)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:401)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175)
> ... 7 more
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NullPointerException
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPeerEncryptor(GMSEncrypt.java:258)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.GMSEncrypt.getPublicKey(GMSEncrypt.java:175)
> ... 7 more
> Please note, that generally this issue is hit after cluster restart. This is
> important, as during poweroff locator can go offline first and one of other
> members will become coordinator and update view file accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
