On Thu, Aug 11, 2016 at 5:19 PM, Ian Boston <[email protected]> wrote: > correct. > Documents are shared by ID so all updates hit the same shard. > That may result in network traffic if the shard is not local.
Focusing on ordering part as that is the most critical aspect compared to other. (BAckup and Restore with sharded index is a separate problem to discuss but later) So even if there is a single master for a given path how would it order the changes. Given local changes only give partial view of end state. Also in such a setup would each query need to consider multiple shards for final result or each node would "eventually" sync index changes from other nodes (complete replication) and query would only use local index For me ensuring consistency in how index updates are sent to ES wrt Oak view of changes was kind of blocking feature to enable parallelization of indexing process. It needs to be ensured that for concurrent commit end result in index is in sync with repository state. Current single thread async index update avoid all such race condition. Chetan Mehrotra
