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

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

GitHub user tsutsu opened a pull request:

    https://github.com/apache/couchdb-couch-mrview/pull/41

    Get running total workload size from work queue

    Given the accompanying change to `couch_index_updater`, the total workload 
processed in an index update is now unbounded. To ensure that the 
`couch_task_status` remains meaningful in cases where work continues to be 
found after the first `couch_index_updater` update-loop, `couch_mrview_updater` 
has been modified to dynamically find the total amount of work discovered and 
queued so far and use update the `couch_task_status` with it. To do this, it 
uses a new counter which has been introduced to `couch_work_queue` (`total_in`) 
in an accompanying PR.
    
    COUCHDB-2955
    BugzID: 14036

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

    $ git pull https://github.com/cloudant/couchdb-couch-mrview 
14036-loop-updater-until-caught-up

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

    https://github.com/apache/couchdb-couch-mrview/pull/41.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 #41
    
----
commit 42a3f5af31d7687a0c70b6dc347a8e676743359f
Author: Levi McAuley <[email protected]>
Date:   2016-02-27T01:31:34Z

    Get running total workload size from work queue

----


> Reopen DBs in couch_index_updater
> ---------------------------------
>
>                 Key: COUCHDB-2955
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2955
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>            Reporter: Levi McAuley
>
> When couch_index_updater finishes streaming couch_db:enum_docs_since we 
> should reopen the db and stream again until we reopen with zero updates. This 
> should theoretically improve latency for things waiting for view updates.



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

Reply via email to