There are a single persistent HTTP connection open from the leader to each replica in the shard. All updates coming to the leader are expanded (for atomic updates) and streamed over that single connection. When using in-place docvalues updates, there is a possibility of the replica making a request to the leader if updates has been re-ordered and the replica does not have enough context to process the update.
Can you quantify the "tons of internal traffic"? Are you seeing higher number of open connections as well? On Fri, Aug 17, 2018 at 11:17 PM Walter Underwood <wun...@wunderwood.org> wrote: > How many messages are sent back and forth between a leader and replica > with NRT? > > We have a collection that gets frequent updates and we are seeing a ton of > internal > cluster traffic. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > > -- Regards, Shalin Shekhar Mangar.
