[ 
https://issues.apache.org/jira/browse/SOLR-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083111#comment-15083111
 ] 

Nirmala Venkatraman commented on SOLR-8470:
-------------------------------------------

After applying the ttl patch and setting to 60sec, one of the nodes hit this 
error. Most likely culprit is slightly longer GC pauses . Do you think we 
should set autoReplicaFailoverWorkLoopDelay to a greater # than default of 10sec

2016-01-04 23:05:37.205 ERROR 
(OverseerHdfsCoreFailoverThread-239245611805900804-sgdsolar7.swg.usma.ibm.com:8984_solr-n_0000000133)
 [   ] o.a.s.c.OverseerAutoReplicaFailoverThread 
OverseerAutoReplicaFailoverThread had an error in its thread work 
loop.:org.apache.solr.common.SolrException: Error reading cluster properties
        at 
org.apache.solr.common.cloud.ZkStateReader.getClusterProps(ZkStateReader.java:732)
        at 
org.apache.solr.cloud.OverseerAutoReplicaFailoverThread.doWork(OverseerAutoReplicaFailoverThread.java:152)
        at 
org.apache.solr.cloud.OverseerAutoReplicaFailoverThread.run(OverseerAutoReplicaFailoverThread.java:131)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.InterruptedException
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:502)
        at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1342)
        at org.apache.zookeeper.ZooKeeper.exists(ZooKeeper.java:1040)
        at 
org.apache.solr.common.cloud.SolrZkClient$5.execute(SolrZkClient.java:311)
        at 
org.apache.solr.common.cloud.SolrZkClient$5.execute(SolrZkClient.java:308)
        at 
org.apache.solr.common.cloud.ZkCmdExecutor.retryOperation(ZkCmdExecutor.java:61)
        at 
org.apache.solr.common.cloud.SolrZkClient.exists(SolrZkClient.java:308)
        at 
org.apache.solr.common.cloud.ZkStateReader.getClusterProps(ZkStateReader.java:725)
        ... 3 more

2016-01-04 23:05:37.218 ERROR (OverseerExitThread) [   ] o.a.s.c.Overseer could 
not read the data
org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = 
Session expired for /overseer_elect/leader
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:127)
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
        at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1155)
        at 
org.apache.solr.common.cloud.SolrZkClient$7.execute(SolrZkClient.java:345)
        at 
org.apache.solr.common.cloud.SolrZkClient$7.execute(SolrZkClient.java:342)
        at 
org.apache.solr.common.cloud.ZkCmdExecutor.retryOperation(ZkCmdExecutor.java:61)
        at 
org.apache.solr.common.cloud.SolrZkClient.getData(SolrZkClient.java:342)
        at 
org.apache.solr.cloud.Overseer$ClusterStateUpdater.checkIfIamStillLeader(Overseer.java:300)
        at 
org.apache.solr.cloud.Overseer$ClusterStateUpdater.access$300(Overseer.java:87)
        at 
org.apache.solr.cloud.Overseer$ClusterStateUpdater$2.run(Overseer.java:261)
2016-01-04 23:05:37.206 ERROR (qtp829053325-487) [c:collection33 s:shard1 
r:core_node2 x:collection33_shard1_replica1] o.a.s.c.SolrCore 
org.apache.solr.common.SolrException: Cannot talk to ZooKeeper - Updates are 
disabled.


> Make TTL of PKIAuthenticationPlugin's tokens configurable through a system 
> property
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-8470
>                 URL: https://issues.apache.org/jira/browse/SOLR-8470
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>             Fix For: 5.3.2, 5.5, Trunk
>
>         Attachments: SOLR-8470.patch
>
>
> Currently the PKIAuthenticationPlugin has hardcoded the ttl to 5000ms. There 
> are users who have experienced timeouts. Make this configurable



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to