Uploaded image for project: 'CouchDB'
  1. CouchDB
  2. COUCHDB-3150

Update all shards with stale=update_after

Details

    • Story
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • Database Core
    • None

    Description

      Stale=update_after should update shards that won't participate in the response due to not being a ushard.

      Discussed with Paul Davis and he suggested the following approach.

      For this ticket we should just need to add a fabric_view:maybe_update_others/3 that we call just after [1,2] with fabric_view:maybe_update_others(DbName, Shards, Args). And then if stable=true and update=(true or lazy) we do mem3:shards(DbName) – ShardsInvolved, and throw a message at them to trigger an update.

      [1] https://github.com/apache/couchdb-fabric/blob/master/src/fabric_view_map.erl#L27
      [2] https://github.com/apache/couchdb-fabric/blob/master/src/fabric_view_reduce.erl#L28

      Attachments

        Activity

          People

            Unassigned Unassigned
            kbkreddy Bala Kolla
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment