lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-5474) Have a new mode for SolrJ to support stateFormat=2
Date Wed, 16 Apr 2014 08:38:19 GMT


ASF subversion and git services commented on SOLR-5474:

Commit 1587834 from in branch 'dev/trunk'
[ ]

SOLR-5473: Make one state.json per collection ,  SOLR-5474: Have a new mode for SolrJ to support

> Have a new mode for SolrJ to support stateFormat=2
> --------------------------------------------------
>                 Key: SOLR-5474
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Noble Paul
>         Attachments: SOLR-5474.patch, SOLR-5474.patch, SOLR-5474.patch
> In this mode SolrJ would not watch any ZK node
> It fetches the state  on demand and cache the most recently used n collections in memory.
> SolrJ would not listen to any ZK node. When a request comes for a collection ‘xcoll’
> it would first check if such a collection exists
> If yes it first looks up the details in the local cache for that collection
> If not found in cache , it fetches the node /collections/xcoll/state.json and caches
the information
> Any query/update will be sent with extra query param specifying the collection name ,
shard name, Role (Leader/Replica), and range (example \_target_=xcoll:shard1:L:80000000-b332ffff)
. A node would throw an error (INVALID_NODE) if it does not the serve the collection/shard/Role/range
> If SolrJ gets INVALID_NODE error it would invalidate the cache and fetch fresh state
information for that collection (and caches it again)
> If there is a connection timeout, SolrJ assumes the node is down and re-fetch the state
for the collection and try again

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message