When client queue start growing/full; it will impact the publisher thread/client... There is an option to kick-out the slow or unresponsive client...
Here is the info on it: remove-unresponsive-client When this property is set to true, the primary server drops unresponsive clients from all secondaries and itself. Clients are deemed unresponsive when their messaging queues become full on the server. While a client's queue is full, puts that would add to the queue block on the server. -Anil. On Wed, Oct 14, 2015 at 2:29 PM, Eric Pederson <[email protected]> wrote: > Dear all: > > I was tracking down an issue with a client that was receiving events late > (receipt time minutes later than sending time) and started spuriously > connecting/reconnecting to the server, ultimately losing some events. > > In the server log I saw this during the same time period: > > [warning 2015/10/13 16:28:48.551 EDT server-psclxfiprdsp104 > <ServerConnection on port 37386 Thread 696> tid=0x66b] Client queue for > _gfe_non_durable_client_with_id_NYCWD28244(:loner):62826:929faf61_1_queue > client is full. > > > > [info 2015/10/13 16:28:48.693 EDT server-psclxfiprdsp104 <ServerConnection > on port 37386 Thread 696> tid=0x66b] Resuming with processing puts ... > > > The client that was full was a different client from the one that was > getting its events late. > > > Is it possible that if a client is slow consuming its events (via CQ) and > its server-side queue becomes full that other clients will be effected? GC > activity looked normal on that server during the time period. > > > Thanks, > > -- Eric >
