[jira] [Commented] (SOLR-6459) Log all Overseer operations, queue size

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on SOLR-6459:
--------------------------------------

GitHub user andyetitmoves opened a pull request:

    https://github.com/apache/lucene-solr/pull/91

    Log all Overseer operations, queue size

    Patch for SOLR-6459

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bloomberg/lucene-solr trunk-overseer-logging

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/lucene-solr/pull/91.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #91
    
----
commit 2b33aefe214587e26a65bdf94f6547517ab8182e
Author: Ramkumar Aiyengar <ra...@bloomberg.net>
Date:   2014-09-01T10:01:07Z

    Normalize logging of operations at Overseer

----


> Log all Overseer operations, queue size
> ---------------------------------------
>
>                 Key: SOLR-6459
>                 URL: https://issues.apache.org/jira/browse/SOLR-6459
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Ramkumar Aiyengar
>            Priority: Minor
>
> Currently the logging done by Overseer is inconsistent, some operations like cluster state changes are logged, while others like leadership transfers are not. Also, Overseer doesn't quite log how backlogged it is.These make it difficult to backtrack any issues with Overseer slowness.



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

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