Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Tue, 31 Dec 2013 20:11:50 +0000 (UTC)
From: "Timothy Potter (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12680289.1384957478894.27458.1388520710766@arcas>
In-Reply-To: <JIRA.12680289.1384957478894@arcas>
References: <JIRA.12680289.1384957478894@arcas>
Subject: [jira] [Updated] (SOLR-5474) Have a new mode for SolrJ to not watch
 any ZKNode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/SOLR-5474?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Potter updated SOLR-5474:
---------------------------------

    Attachment: SOLR-5474.patch

Previous patch file was created incorrectly with git ...

> Have a new mode for SolrJ to not watch any ZKNode
> -------------------------------------------------
>
>                 Key: SOLR-5474
>                 URL: https://issues.apache.org/jira/browse/SOLR-5474
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Noble Paul
>         Attachments: 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 collec=
tions in memory.
> SolrJ would not listen to any ZK node. When a request comes for a collect=
ion =E2=80=98xcoll=E2=80=99
> it would first check if such a collection exists
> If yes it first looks up the details in the local cache for that collecti=
on
> 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 colle=
ction name , shard name, Role (Leader/Replica), and range (example \_target=
_=3Dxcoll:shard1:L:80000000-b332ffff) . A node would throw an error (INVALI=
D_NODE) if it does not the serve the collection/shard/Role/range combo.
> 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-f=
etch the state for the collection and try again


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org