You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/11 17:42:59 UTC

[jira] [Commented] (COUCHDB-3234) Track open shard timeouts with a counter instead of logging

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

ASF GitHub Bot commented on COUCHDB-3234:
-----------------------------------------

GitHub user davisp opened a pull request:

    https://github.com/apache/couchdb-fabric/pull/74

    Track open_shard timeouts with a counter

    The open_shard RPC endpoint is used to grab security docs. There are
    fairly aggressive timeouts on these requests so that when a node is too
    busy it'll try the next shard. Rather than log everytime these fail
    (which can be substantial under load) lets just use a counter that can
    be graphed and alerted on.
    
    COUCHDB-3234

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

    $ git pull https://github.com/cloudant/couchdb-fabric COUCHDB-3234-open-shard-timeout-counter

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

    https://github.com/apache/couchdb-fabric/pull/74.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 #74
    
----
commit 4fcfecf720791f400169c6823aac1abc2d85c47e
Author: Paul J. Davis <pa...@gmail.com>
Date:   2016-11-11T17:34:11Z

    Track open_shard timeouts with a counter
    
    The open_shard RPC endpoint is used to grab security docs. There are
    fairly aggressive timeouts on these requests so that when a node is too
    busy it'll try the next shard. Rather than log everytime these fail
    (which can be substantial under load) lets just use a counter that can
    be graphed and alerted on.
    
    COUCHDB-3234

----


> Track open shard timeouts with a counter instead of logging
> -----------------------------------------------------------
>
>                 Key: COUCHDB-3234
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3234
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>            Reporter: Paul Joseph Davis
>
> Fabric uses the open_shard RPC method to get security objects for every request. These calls have very short timeouts on them which can cause massive amounts of log spam when a node is under load. Rather than log a whole bunch of garbage when each one fails lets just use a counter instead.
> PR incoming



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