[
https://issues.apache.org/jira/browse/SOLR-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528997#comment-15528997
]
Jan Høydahl commented on SOLR-8611:
-----------------------------------
Could not reproduce this. Can you provide instructions on how to reproduce from
scratch?
Also please state what exactly you mean is wrong in the log, is it the content
of the {{\[c:offers_suggest_topsearch s:shard1...\]}} section you mean? Think
that is produced from MDC logging, so the issue could be lack of updating
{{MDCLoggingContext.setCoreDescriptor(descriptor);}} in the for-loop of core
descriptors?
> Incorrect logging in ZkController
> ---------------------------------
>
> Key: SOLR-8611
> URL: https://issues.apache.org/jira/browse/SOLR-8611
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.4
> Reporter: Stephan Lagraulet
> Priority: Minor
> Labels: logging
>
> When a new Zookeeper Session is created all cores publish a "down" status.
> Then a call to "waitForLeaderToSeeDownState" is made.
> Unfortunately, the logged info inside this method is not correct, keeping the
> last published core:
> {code}
> 2016-01-28 10:19:36.296 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [ ]
> o.a.s.c.ZkController ZooKeeper session re-connected ... refreshing core
> states after session expiration.
> 2016-01-28 10:19:36.296 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr)
> [c:offers_suggest_marketing s:shard1 r:core_node3
> x:offers_suggest_marketing_shard1_replica5] o.a.s.c.ZkController publishing
> state=down
> 2016-01-28 10:19:36.300 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr)
> [c:offers_suggest_topsearch s:shard1 r:core_node4
> x:offers_suggest_topsearch_shard1_replica2] o.a.s.c.ZkController publishing
> state=down
> 2016-01-28 10:19:36.301 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [c:offers_storage
> s:shard3 r:core_node8 x:offers_storage_shard3_replica2] o.a.s.c.ZkController
> publishing state=down
> 2016-01-28 10:19:36.302 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [c:offers_lean
> s:shard3 r:core_node6 x:offers_lean_shard3_replica2] o.a.s.c.ZkController
> publishing state=down
> 2016-01-28 10:19:36.305 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [c:offers_lean
> s:shard3 r:core_node6 x:offers_lean_shard3_replica2] o.a.s.c.ZkController
> Replica core_node3 NOT in leader-initiated recovery, need to wait for leader
> to see down state.
> 2016-01-28 10:19:36.313 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [c:offers_lean
> s:shard3 r:core_node6 x:offers_lean_shard3_replica2] o.a.s.c.ZkController
> Replica core_node4 NOT in leader-initiated recovery, need to wait for leader
> to see down state.
> 2016-01-28 10:19:36.317 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [c:offers_lean
> s:shard3 r:core_node6 x:offers_lean_shard3_replica2] o.a.s.c.ZkController
> Replica core_node8 NOT in leader-initiated recovery, need to wait for leader
> to see down state.
> {code}
> It should be
> {code}
> 2016-01-28 10:19:36.296 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [ ]
> o.a.s.c.ZkController ZooKeeper session re-connected ... refreshing core
> states after session expiration.
> 2016-01-28 10:19:36.296 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr)
> [c:offers_suggest_marketing s:shard1 r:core_node3
> x:offers_suggest_marketing_shard1_replica5] o.a.s.c.ZkController publishing
> state=down
> 2016-01-28 10:19:36.300 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr)
> [c:offers_suggest_topsearch s:shard1 r:core_node4
> x:offers_suggest_topsearch_shard1_replica2] o.a.s.c.ZkController publishing
> state=down
> 2016-01-28 10:19:36.301 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [c:offers_storage
> s:shard3 r:core_node8 x:offers_storage_shard3_replica2] o.a.s.c.ZkController
> publishing state=down
> 2016-01-28 10:19:36.302 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [c:offers_lean
> s:shard3 r:core_node6 x:offers_lean_shard3_replica2] o.a.s.c.ZkController
> publishing state=down
> 2016-01-28 10:19:36.305 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr)
> [c:offers_suggest_marketing s:shard1 r:core_node3
> x:offers_suggest_marketing_shard1_replica5] o.a.s.c.ZkController Replica
> core_node3 NOT in leader-initiated recovery, need to wait for leader to see
> down state.
> 2016-01-28 10:19:36.313 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr)
> [c:offers_suggest_topsearch s:shard1 r:core_node4
> x:offers_suggest_topsearch_shard1_replica2] o.a.s.c.ZkController Replica
> core_node4 NOT in leader-initiated recovery, need to wait for leader to see
> down state.
> 2016-01-28 10:19:36.317 INFO
> (zkCallback-3-thread-37-processing-n:node054:8983_solr) [c:offers_storage
> s:shard3 r:core_node8 x:offers_storage_shard3_replica2] o.a.s.c.ZkController
> Replica core_node8 NOT in leader-initiated recovery, need to wait for leader
> to see down state.
> {code}
--
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
