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

Jan Høydahl commented on SOLR-6677:
-----------------------------------

Here is what I see on one of the nodes when starting a 3-node cloud setup with 
the current master:
{noformat}
INFO  - 2016-09-27 20:44:46.881; [   ] org.apache.solr.cloud.ZkController; 
Register node as live in ZooKeeper:/live_nodes/192.168.0.11:8983_solr
INFO  - 2016-09-27 20:44:46.886; [   ] 
org.apache.solr.common.cloud.ZkStateReader; Updated live nodes from 
ZooKeeper... (0) -> (1)
...
INFO  - 2016-09-27 20:44:51.654; [   ] 
org.apache.solr.common.cloud.ZkStateReader; Updated live nodes from 
ZooKeeper... (1) -> (2)
INFO  - 2016-09-27 20:44:57.451; [   ] 
org.apache.solr.common.cloud.ZkStateReader; Updated live nodes from 
ZooKeeper... (2) -> (3)
...
INFO  - 2016-09-27 20:45:46.723; [   ] 
org.apache.solr.common.cloud.ZkStateReader$StateWatcher; A cluster state 
change: [WatchedEvent state:SyncConnected type:NodeDataChanged 
path:/collections/gettingstarted/state.json] for collection [gettingstarted] 
has occurred - updating... (live nodes size: [3])
{noformat}

I think this is sufficient.

> Reduce logging during startup and shutdown
> ------------------------------------------
>
>                 Key: SOLR-6677
>                 URL: https://issues.apache.org/jira/browse/SOLR-6677
>             Project: Solr
>          Issue Type: Bug
>          Components: logging
>            Reporter: Noble Paul
>            Assignee: Jan Høydahl
>             Fix For: 6.3, master (7.0)
>
>         Attachments: SOLR-6677-part-2.patch, SOLR-6677-part-4.patch, 
> SOLR-6677-part3.patch, SOLR-6677.patch, SOLR-6677.patch
>
>
> most of what is printed is neither helpful nor useful. It's just noise



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