Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 25 Nov 2013 13:01:37 +0000 (UTC)
From: "Ramkumar Aiyengar (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12681023.1385383488620.23636.1385384497712@arcas>
In-Reply-To: <JIRA.12681023.1385383488620@arcas>
References: <JIRA.12681023.1385383488620@arcas>
Subject: [jira] [Commented] (SOLR-5499) Real-time /get handler is required
 when using Solr Cloud
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831433#comment-13831433 ] 

Ramkumar Aiyengar commented on SOLR-5499:
-----------------------------------------

There is a precedent in {{CoreAdminHandler}} where the handler is registered in code rather than being left to configuration since it's needed by Solr cloud. Should the same be done for {{/get}}? (well, technically it's not necessary still but it does have it's repercussions..)

> Real-time /get handler is required when using Solr Cloud
> --------------------------------------------------------
>
>                 Key: SOLR-5499
>                 URL: https://issues.apache.org/jira/browse/SOLR-5499
>             Project: Solr
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 4.4, 4.5, 4.5.1
>            Reporter: Daniel Collins
>            Priority: Minor
>
> Noticed during some leadership election when we shutdown Solr nodes.  
> Delving through the code it seems that PeerSync uses the /get handler (with some very ugly code explicitly creating an HTTP request by hand). If that isn't configured, then any election change will cause a full sync in ALL replicas for the shard in question.
> {noformat}
> 2013-11-25 06:35:39,766 INFO [main-EventThread] o.a.s.c.SyncStrategy [SyncStrategy.java:94] Sync replicas to http://xxxxx:xxx/solr/xxxx_shard74_replica1/
> 2013-11-25 06:35:39,766 INFO [main-EventThread] o.a.s.u.PeerSync [PeerSync.java:186] PeerSync: core=xxx_shard74_replica1 u
> rl=http://xxxxxxx:xxxxx/solr START replicas=[http://xxxxxxx:xxxx/solr/xxx_shard74_replica2/, http://xxxx:xxx/sol
> r/xxx_shard74_replica3/] nUpdates=100
> 2013-11-25 06:35:39,768 WARN [main-EventThread] o.a.s.u.PeerSync [PeerSync.java:321] PeerSync: core=xxx_shard74_replica1 u
> rl=http://xxx:xxx/solr  got a 404 from http://xxx:xxx/solr/xxx_shard74_replica2/, counting as success
> 2013-11-25 06:35:39,769 INFO [main-EventThread] o.a.s.u.PeerSync [PeerSync.java:273] PeerSync: core=xxx_shard74_replica1 u
> rl=http://nsrchnj2:10650/solr DONE. sync succeeded
> 2013-11-25 06:35:39,769 INFO [main-EventThread] o.a.s.c.SyncStrategy [SyncStrategy.java:134] Sync Success - now sync replicas to me
> 2013-11-25 06:35:39,769 INFO [main-EventThread] o.a.s.c.SyncStrategy [SyncStrategy.java:191] http://xxx:xxx/solr/xxx_shard74_replica1/: try and ask http://xxx:xxx/solr/xxx_shard74_replica2/ to sync
> 2013-11-25 06:35:39,771 ERROR [main-EventThread] o.a.s.c.SyncStrategy [SolrException.java:129] Sync request error: org.apache.solr.client.
> solrj.impl.HttpSolrServer$RemoteSolrException: Server at http://xxx:xxx/solr/xxx_shard74_replica3 returned non ok 
> status:404, message:Not Found
> 2013-11-25 06:35:39,771 INFO [main-EventThread] o.a.s.c.SyncStrategy [SyncStrategy.java:211] http://xxx:xxx/solr/xxx_shard74_replica1/: Sync failed - asking replica (http://xxx:xxx/solr/xxx_shard74_replica2/) to recover.
> {noformat}
> The triggers here (for me) were the 404 response codes, but we should just make it clear in the docs that the /get handler is required and shouldn't be removed (if using Solr Cloud)


--
This message was sent by Atlassian JIRA
(v6.1#6144)

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