Hi, It is interesting that node reports healthy despite store access issue. That node should be marked down if it can't open the core backing up sharded collection.
Maybe if you could share exceptions/errors that you see in console/logs. I have experienced issues with replica node not responding in timely manner due to performance issues but that does not seem to match your case. -- Jaroslaw Rozanski On Wed, 15 Nov 2017, at 22:49, kasinger, james wrote: > Hello folks, > > > > To start, we have a sharded solr cloud configuration running solr version > 5.1.0 . During shard to shard communication there is a problem state > where queries are sent to a replica, and on that replica the storage is > inaccessible. The node is healthy so it’s still taking requests which get > piled up waiting to read from disk resulting in a latency increase. We’ve > tried resolving this storage inaccessibility but it appears related to > AWS ebs issues. Has anyone encountered the same issue? > > thanks
