[SOLR-9440] ZkStateReader on a client can cache collection state and never refresh it

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.2, 8.0
• Component/s: SolrCloud
• Assignee: Shalin Shekhar Mangar
• Reporter: Shalin Shekhar Mangar
• Created: 24/Aug/16 21:17
• Updated: 02/Oct/19 17:24
• Resolved: 08/Nov/17 06:39

Description

I saw this while writing a test case for SOLR-9438. The collection1 collection which was in stateFormat=2 was somehow caching the CloudSolrClient's ZkStateReader such that the returned cluster state contained the collection state. However this collection was neither watched nor lazy so any call to waitForRecoveriesToFinish would see stale state and loop until timeout.

Issue Links

• breaks: SOLR-10878 MOVEREPLICA command may lose data when replicationFactor==1
• relates to: SOLR-12544 ZkStateReader can cache deleted collections and never refresh it