[jira] [Commented] (SOLR-3273) 404 Not Found on action=PREPRECOVERY
[
https://issues.apache.org/jira/browse/SOLR-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239419#comment-13239419
]
Per Steffensen commented on SOLR-3273:
--
Seems to work much better with adminPath="/admin/cores"
Regards, Per Steffensen
> 404 Not Found on action=PREPRECOVERY
>
>
> Key: SOLR-3273
> URL: https://issues.apache.org/jira/browse/SOLR-3273
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
>Affects Versions: 4.0
> Environment: Any
>Reporter: Per Steffensen
>Assignee: Mark Miller
>Priority: Minor
>
> We have an application based on a recent copy of 4.0-SNAPSHOT. We have a
> preformance test setup where we performance test our application (and
> therefore indirectly Solr(Cloud)). When we run the performance test against a
> setup using SolrCloud without replication, everything seems to run very
> nicely for days. When we add replication to the setup the same performance
> test shows some problems - which we will report (and maybe help fix) in
> distinct issues here in jira.
> About the setup - the setup is a little more complex than described below,
> but I believe the description will tell "enough":
> We have two solr servers which we start from /example using
> this command (ZooKeepers have been started before) - we first start solr on
> server1, and then starts solr on server2 after solr on server1 finished
> starting up:
> {code}
> nohup java -Xmx4096m -Dcom.sun.management.jmxremote
> -DzkHost=server1:2181,server2:2181,server3:2181
> -Dbootstrap_confdir=./myapp/conf -Dcollection.configName=myapp_conf
> -Dsolr.solr.home=./myapp -Djava.util.logging.config.file=logging.properties
> -jar start.jar >./myapp/logs/stdout.log 2>./myapp/logs/stderr.log &
> {code}
> The ./myapp/solr.xml looks like this on server1:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The ./myapp/solr.xml looks like this on server2:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The first thing we observe is that Solr server1 (running collA_slice1_shard1)
> seems to start up nicely, but when Solr server2 (running collA_slice1_shard2)
> is started up later it quickly reports the following in its solr.log an keeps
> doing that for a long time:
> {code}
> SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
> Not Found
> request:
> http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2
> at
> org.apache.solr.common.SolrExceptionPropagationHelper.decodeFromMsg(SolrExceptionPropagationHelper.java:40)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:445)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:264)
> at
> org.apache.solr.cloud.RecoveryStrategy.sendPrepRecoveryCmd(RecoveryStrategy.java:188)
> at
> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:285)
> at
> org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:206)
> {code}
> Please note that we have changed a little bit in the way errors are logged,
> but basically this means that Solr server2 gets an "404 Not Found" on its
> request
> "http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2";
> to Solr server1.
> Seems like there is not a common agreement among the Solr servers on
> how/where to send those requests and how/where to listen for them.
> Regards, Per Steffensen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
Re: [jira] [Commented] (SOLR-3273) 404 Not Found on action=PREPRECOVERY
bq: I am talking about the built-in replication of SolrCloud
Ahhh, thanks for the clarification, I as way off in the weeds.
Erick
On Mon, Mar 26, 2012 at 9:42 AM, Per Steffensen (Commented) (JIRA)
wrote:
>
> [
> https://issues.apache.org/jira/browse/SOLR-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238384#comment-13238384
> ]
>
> Per Steffensen commented on SOLR-3273:
> --
>
> @Mark Miller: Thanks. We will try that. I would be very helpful if you could
> state exactly what you expect in adminPath. Does it have to be exactly
> "/admin/cores" or is "/admin/cores/myapp" allowed or does it have to be
> something else. Thanks!
>
> @Erick Erickson: Please note that I am talking about the built-in replication
> of SolrCloud and not "the old replication" described at
> http://wiki.apache.org/solr/SolrReplication
>
>> 404 Not Found on action=PREPRECOVERY
>>
>>
>> Key: SOLR-3273
>> URL: https://issues.apache.org/jira/browse/SOLR-3273
>> Project: Solr
>> Issue Type: Bug
>> Components: SolrCloud
>> Affects Versions: 4.0
>> Environment: Any
>> Reporter: Per Steffensen
>> Assignee: Mark Miller
>> Priority: Minor
>>
>> We have an application based on a recent copy of 4.0-SNAPSHOT. We have a
>> preformance test setup where we performance test our application (and
>> therefore indirectly Solr(Cloud)). When we run the performance test against
>> a setup using SolrCloud without replication, everything seems to run very
>> nicely for days. When we add replication to the setup the same performance
>> test shows some problems - which we will report (and maybe help fix) in
>> distinct issues here in jira.
>> About the setup - the setup is a little more complex than described below,
>> but I believe the description will tell "enough":
>> We have two solr servers which we start from /example using
>> this command (ZooKeepers have been started before) - we first start solr on
>> server1, and then starts solr on server2 after solr on server1 finished
>> starting up:
>> {code}
>> nohup java -Xmx4096m -Dcom.sun.management.jmxremote
>> -DzkHost=server1:2181,server2:2181,server3:2181
>> -Dbootstrap_confdir=./myapp/conf -Dcollection.configName=myapp_conf
>> -Dsolr.solr.home=./myapp -Djava.util.logging.config.file=logging.properties
>> -jar start.jar >./myapp/logs/stdout.log 2>./myapp/logs/stderr.log &
>> {code}
>> The ./myapp/solr.xml looks like this on server1:
>> {code:xml}
>>
>>
>> > hostContext="solr">
>> > dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>>
>>
>> {code}
>> The ./myapp/solr.xml looks like this on server2:
>> {code:xml}
>>
>>
>> > hostContext="solr">
>> > dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>>
>>
>> {code}
>> The first thing we observe is that Solr server1 (running
>> collA_slice1_shard1) seems to start up nicely, but when Solr server2
>> (running collA_slice1_shard2) is started up later it quickly reports the
>> following in its solr.log an keeps doing that for a long time:
>> {code}
>> SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
>> Not Found
>> request:
>> http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2
>> at
>> org.apache.solr.common.SolrExceptionPropagationHelper.decodeFromMsg(SolrExceptionPropagationHelper.java:40)
>> at
>> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:445)
>> at
>> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:264)
>> at
>> org.apache.solr.cloud.RecoveryStrategy.sendPrepRecoveryCmd(RecoveryStrategy.java:188)
>> at
>> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:285)
>> at
>> org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:206)
>> {code}
>> Please note that we have changed a little bit in the way errors are logged,
>> but basically this means that Solr server2 gets an "404 Not Found" on its
>> request
>> "http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2";
>> to Solr server1.
>> Seems like there is not a common agreement among the Solr servers on
>> how/where to send those requests and how/where to listen for them.
>> Regards, Per Steffensen
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https:
[jira] [Commented] (SOLR-3273) 404 Not Found on action=PREPRECOVERY
[
https://issues.apache.org/jira/browse/SOLR-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238410#comment-13238410
]
Per Steffensen commented on SOLR-3273:
--
Thanks a lot. It is ok for us just to use "/admin/cores". We really do not
mind. But at least it needs some documentation, or maybe share admin-path in
ZK, so that a remote solr can acutally look it up. Well you decide that.
Regards, Per Steffensen
> 404 Not Found on action=PREPRECOVERY
>
>
> Key: SOLR-3273
> URL: https://issues.apache.org/jira/browse/SOLR-3273
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
>Affects Versions: 4.0
> Environment: Any
>Reporter: Per Steffensen
>Assignee: Mark Miller
>Priority: Minor
>
> We have an application based on a recent copy of 4.0-SNAPSHOT. We have a
> preformance test setup where we performance test our application (and
> therefore indirectly Solr(Cloud)). When we run the performance test against a
> setup using SolrCloud without replication, everything seems to run very
> nicely for days. When we add replication to the setup the same performance
> test shows some problems - which we will report (and maybe help fix) in
> distinct issues here in jira.
> About the setup - the setup is a little more complex than described below,
> but I believe the description will tell "enough":
> We have two solr servers which we start from /example using
> this command (ZooKeepers have been started before) - we first start solr on
> server1, and then starts solr on server2 after solr on server1 finished
> starting up:
> {code}
> nohup java -Xmx4096m -Dcom.sun.management.jmxremote
> -DzkHost=server1:2181,server2:2181,server3:2181
> -Dbootstrap_confdir=./myapp/conf -Dcollection.configName=myapp_conf
> -Dsolr.solr.home=./myapp -Djava.util.logging.config.file=logging.properties
> -jar start.jar >./myapp/logs/stdout.log 2>./myapp/logs/stderr.log &
> {code}
> The ./myapp/solr.xml looks like this on server1:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The ./myapp/solr.xml looks like this on server2:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The first thing we observe is that Solr server1 (running collA_slice1_shard1)
> seems to start up nicely, but when Solr server2 (running collA_slice1_shard2)
> is started up later it quickly reports the following in its solr.log an keeps
> doing that for a long time:
> {code}
> SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
> Not Found
> request:
> http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2
> at
> org.apache.solr.common.SolrExceptionPropagationHelper.decodeFromMsg(SolrExceptionPropagationHelper.java:40)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:445)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:264)
> at
> org.apache.solr.cloud.RecoveryStrategy.sendPrepRecoveryCmd(RecoveryStrategy.java:188)
> at
> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:285)
> at
> org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:206)
> {code}
> Please note that we have changed a little bit in the way errors are logged,
> but basically this means that Solr server2 gets an "404 Not Found" on its
> request
> "http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2";
> to Solr server1.
> Seems like there is not a common agreement among the Solr servers on
> how/where to send those requests and how/where to listen for them.
> Regards, Per Steffensen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3273) 404 Not Found on action=PREPRECOVERY
[
https://issues.apache.org/jira/browse/SOLR-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238394#comment-13238394
]
Mark Miller commented on SOLR-3273:
---
just adminPath="/admin/cores" - same as you see in the default solr.xml.
Now I could make it so that we look up what the admin path is locally - but I
don't know that we should - just because someone has changed the adminPath
locally, doesn't mean they changed it on the 'remote' node. We don't really
have a way of know what it is on the remote node. So it may be the right choice
to just require that people leave it as is for solrcloud (though of course we
should doc this).
> 404 Not Found on action=PREPRECOVERY
>
>
> Key: SOLR-3273
> URL: https://issues.apache.org/jira/browse/SOLR-3273
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
>Affects Versions: 4.0
> Environment: Any
>Reporter: Per Steffensen
>Assignee: Mark Miller
>Priority: Minor
>
> We have an application based on a recent copy of 4.0-SNAPSHOT. We have a
> preformance test setup where we performance test our application (and
> therefore indirectly Solr(Cloud)). When we run the performance test against a
> setup using SolrCloud without replication, everything seems to run very
> nicely for days. When we add replication to the setup the same performance
> test shows some problems - which we will report (and maybe help fix) in
> distinct issues here in jira.
> About the setup - the setup is a little more complex than described below,
> but I believe the description will tell "enough":
> We have two solr servers which we start from /example using
> this command (ZooKeepers have been started before) - we first start solr on
> server1, and then starts solr on server2 after solr on server1 finished
> starting up:
> {code}
> nohup java -Xmx4096m -Dcom.sun.management.jmxremote
> -DzkHost=server1:2181,server2:2181,server3:2181
> -Dbootstrap_confdir=./myapp/conf -Dcollection.configName=myapp_conf
> -Dsolr.solr.home=./myapp -Djava.util.logging.config.file=logging.properties
> -jar start.jar >./myapp/logs/stdout.log 2>./myapp/logs/stderr.log &
> {code}
> The ./myapp/solr.xml looks like this on server1:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The ./myapp/solr.xml looks like this on server2:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The first thing we observe is that Solr server1 (running collA_slice1_shard1)
> seems to start up nicely, but when Solr server2 (running collA_slice1_shard2)
> is started up later it quickly reports the following in its solr.log an keeps
> doing that for a long time:
> {code}
> SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
> Not Found
> request:
> http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2
> at
> org.apache.solr.common.SolrExceptionPropagationHelper.decodeFromMsg(SolrExceptionPropagationHelper.java:40)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:445)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:264)
> at
> org.apache.solr.cloud.RecoveryStrategy.sendPrepRecoveryCmd(RecoveryStrategy.java:188)
> at
> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:285)
> at
> org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:206)
> {code}
> Please note that we have changed a little bit in the way errors are logged,
> but basically this means that Solr server2 gets an "404 Not Found" on its
> request
> "http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2";
> to Solr server1.
> Seems like there is not a common agreement among the Solr servers on
> how/where to send those requests and how/where to listen for them.
> Regards, Per Steffensen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.ap
[jira] [Commented] (SOLR-3273) 404 Not Found on action=PREPRECOVERY
[
https://issues.apache.org/jira/browse/SOLR-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238384#comment-13238384
]
Per Steffensen commented on SOLR-3273:
--
@Mark Miller: Thanks. We will try that. I would be very helpful if you could
state exactly what you expect in adminPath. Does it have to be exactly
"/admin/cores" or is "/admin/cores/myapp" allowed or does it have to be
something else. Thanks!
@Erick Erickson: Please note that I am talking about the built-in replication
of SolrCloud and not "the old replication" described at
http://wiki.apache.org/solr/SolrReplication
> 404 Not Found on action=PREPRECOVERY
>
>
> Key: SOLR-3273
> URL: https://issues.apache.org/jira/browse/SOLR-3273
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
>Affects Versions: 4.0
> Environment: Any
>Reporter: Per Steffensen
>Assignee: Mark Miller
>Priority: Minor
>
> We have an application based on a recent copy of 4.0-SNAPSHOT. We have a
> preformance test setup where we performance test our application (and
> therefore indirectly Solr(Cloud)). When we run the performance test against a
> setup using SolrCloud without replication, everything seems to run very
> nicely for days. When we add replication to the setup the same performance
> test shows some problems - which we will report (and maybe help fix) in
> distinct issues here in jira.
> About the setup - the setup is a little more complex than described below,
> but I believe the description will tell "enough":
> We have two solr servers which we start from /example using
> this command (ZooKeepers have been started before) - we first start solr on
> server1, and then starts solr on server2 after solr on server1 finished
> starting up:
> {code}
> nohup java -Xmx4096m -Dcom.sun.management.jmxremote
> -DzkHost=server1:2181,server2:2181,server3:2181
> -Dbootstrap_confdir=./myapp/conf -Dcollection.configName=myapp_conf
> -Dsolr.solr.home=./myapp -Djava.util.logging.config.file=logging.properties
> -jar start.jar >./myapp/logs/stdout.log 2>./myapp/logs/stderr.log &
> {code}
> The ./myapp/solr.xml looks like this on server1:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The ./myapp/solr.xml looks like this on server2:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The first thing we observe is that Solr server1 (running collA_slice1_shard1)
> seems to start up nicely, but when Solr server2 (running collA_slice1_shard2)
> is started up later it quickly reports the following in its solr.log an keeps
> doing that for a long time:
> {code}
> SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
> Not Found
> request:
> http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2
> at
> org.apache.solr.common.SolrExceptionPropagationHelper.decodeFromMsg(SolrExceptionPropagationHelper.java:40)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:445)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:264)
> at
> org.apache.solr.cloud.RecoveryStrategy.sendPrepRecoveryCmd(RecoveryStrategy.java:188)
> at
> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:285)
> at
> org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:206)
> {code}
> Please note that we have changed a little bit in the way errors are logged,
> but basically this means that Solr server2 gets an "404 Not Found" on its
> request
> "http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2";
> to Solr server1.
> Seems like there is not a common agreement among the Solr servers on
> how/where to send those requests and how/where to listen for them.
> Regards, Per Steffensen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...
[jira] [Commented] (SOLR-3273) 404 Not Found on action=PREPRECOVERY
[
https://issues.apache.org/jira/browse/SOLR-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238377#comment-13238377
]
Mark Miller commented on SOLR-3273:
---
bq. adminPath="/admin/myapp"
Thats probably the issue - I think we assume /admin/cores or whatever the
default is.
> 404 Not Found on action=PREPRECOVERY
>
>
> Key: SOLR-3273
> URL: https://issues.apache.org/jira/browse/SOLR-3273
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
>Affects Versions: 4.0
> Environment: Any
>Reporter: Per Steffensen
>
> We have an application based on a recent copy of 4.0-SNAPSHOT. We have a
> preformance test setup where we performance test our application (and
> therefore indirectly Solr(Cloud)). When we run the performance test against a
> setup using SolrCloud without replication, everything seems to run very
> nicely for days. When we add replication to the setup the same performance
> test shows some problems - which we will report (and maybe help fix) in
> distinct issues here in jira.
> About the setup - the setup is a little more complex than described below,
> but I believe the description will tell "enough":
> We have two solr servers which we start from /example using
> this command (ZooKeepers have been started before) - we first start solr on
> server1, and then starts solr on server2 after solr on server1 finished
> starting up:
> {code}
> nohup java -Xmx4096m -Dcom.sun.management.jmxremote
> -DzkHost=server1:2181,server2:2181,server3:2181
> -Dbootstrap_confdir=./myapp/conf -Dcollection.configName=myapp_conf
> -Dsolr.solr.home=./myapp -Djava.util.logging.config.file=logging.properties
> -jar start.jar >./myapp/logs/stdout.log 2>./myapp/logs/stderr.log &
> {code}
> The ./myapp/solr.xml looks like this on server1:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The ./myapp/solr.xml looks like this on server2:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The first thing we observe is that Solr server1 (running collA_slice1_shard1)
> seems to start up nicely, but when Solr server2 (running collA_slice1_shard2)
> is started up later it quickly reports the following in its solr.log an keeps
> doing that for a long time:
> {code}
> SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
> Not Found
> request:
> http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2
> at
> org.apache.solr.common.SolrExceptionPropagationHelper.decodeFromMsg(SolrExceptionPropagationHelper.java:40)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:445)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:264)
> at
> org.apache.solr.cloud.RecoveryStrategy.sendPrepRecoveryCmd(RecoveryStrategy.java:188)
> at
> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:285)
> at
> org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:206)
> {code}
> Please note that we have changed a little bit in the way errors are logged,
> but basically this means that Solr server2 gets an "404 Not Found" on its
> request
> "http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2";
> to Solr server1.
> Seems like there is not a common agreement among the Solr servers on
> how/where to send those requests and how/where to listen for them.
> Regards, Per Steffensen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3273) 404 Not Found on action=PREPRECOVERY
[
https://issues.apache.org/jira/browse/SOLR-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238311#comment-13238311
]
Per Steffensen commented on SOLR-3273:
--
Hi
Thanks for your reply. Correct me (too) if Im wrong, but I believe SolrCloud
does not do replication unless it is asked to. I believe you can turn
replication on by setting "numShards > 1" somewhere, or you can set it up more
manually by making sure you have more cores defined with the same shard value
("slice1" in my case) in solr.xml's distributed on different solr instances -
like we try to do.
But I would really like to be corrected if anyone knows that I am doing
something wrong.
Regards, Per Steffensen
> 404 Not Found on action=PREPRECOVERY
>
>
> Key: SOLR-3273
> URL: https://issues.apache.org/jira/browse/SOLR-3273
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
>Affects Versions: 4.0
> Environment: Any
>Reporter: Per Steffensen
>
> We have an application based on a recent copy of 4.0-SNAPSHOT. We have a
> preformance test setup where we performance test our application (and
> therefore indirectly Solr(Cloud)). When we run the performance test against a
> setup using SolrCloud without replication, everything seems to run very
> nicely for days. When we add replication to the setup the same performance
> test shows some problems - which we will report (and maybe help fix) in
> distinct issues here in jira.
> About the setup - the setup is a little more complex than described below,
> but I believe the description will tell "enough":
> We have two solr servers which we start from /example using
> this command (ZooKeepers have been started before) - we first start solr on
> server1, and then starts solr on server2 after solr on server1 finished
> starting up:
> {code}
> nohup java -Xmx4096m -Dcom.sun.management.jmxremote
> -DzkHost=server1:2181,server2:2181,server3:2181
> -Dbootstrap_confdir=./myapp/conf -Dcollection.configName=myapp_conf
> -Dsolr.solr.home=./myapp -Djava.util.logging.config.file=logging.properties
> -jar start.jar >./myapp/logs/stdout.log 2>./myapp/logs/stderr.log &
> {code}
> The ./myapp/solr.xml looks like this on server1:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The ./myapp/solr.xml looks like this on server2:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The first thing we observe is that Solr server1 (running collA_slice1_shard1)
> seems to start up nicely, but when Solr server2 (running collA_slice1_shard2)
> is started up later it quickly reports the following in its solr.log an keeps
> doing that for a long time:
> {code}
> SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
> Not Found
> request:
> http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2
> at
> org.apache.solr.common.SolrExceptionPropagationHelper.decodeFromMsg(SolrExceptionPropagationHelper.java:40)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:445)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:264)
> at
> org.apache.solr.cloud.RecoveryStrategy.sendPrepRecoveryCmd(RecoveryStrategy.java:188)
> at
> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:285)
> at
> org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:206)
> {code}
> Please note that we have changed a little bit in the way errors are logged,
> but basically this means that Solr server2 gets an "404 Not Found" on its
> request
> "http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2";
> to Solr server1.
> Seems like there is not a common agreement among the Solr servers on
> how/where to send those requests and how/where to listen for them.
> Regards, Per Steffensen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For add
[jira] [Commented] (SOLR-3273) 404 Not Found on action=PREPRECOVERY
[
https://issues.apache.org/jira/browse/SOLR-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238292#comment-13238292
]
Erick Erickson commented on SOLR-3273:
--
Of course the people who actually know the code may make me look foolish, but
why are you even turning on replication in a SolrCloud environment? As I
understand it, all the replication & etc is done for you by virtue of the
leaders automatically distributing the incoming updates to all replicas so
nothing useful is accomplished by turning on replication.
If I'm on track, maybe the right solution is for the replication code to "do
the right thing" when running in a SolrCloud configuration, which is to do
nothing.
> 404 Not Found on action=PREPRECOVERY
>
>
> Key: SOLR-3273
> URL: https://issues.apache.org/jira/browse/SOLR-3273
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
>Affects Versions: 4.0
> Environment: Any
>Reporter: Per Steffensen
>
> We have an application based on a recent copy of 4.0-SNAPSHOT. We have a
> preformance test setup where we performance test our application (and
> therefore indirectly Solr(Cloud)). When we run the performance test against a
> setup using SolrCloud without replication, everything seems to run very
> nicely for days. When we add replication to the setup the same performance
> test shows some problems - which we will report (and maybe help fix) in
> distinct issues here in jira.
> About the setup - the setup is a little more complex than described below,
> but I believe the description will tell "enough":
> We have two solr servers which we start from /example using
> this command (ZooKeepers have been started before) - we first start solr on
> server1, and then starts solr on server2 after solr on server1 finished
> starting up:
> {code}
> nohup java -Xmx4096m -Dcom.sun.management.jmxremote
> -DzkHost=server1:2181,server2:2181,server3:2181
> -Dbootstrap_confdir=./myapp/conf -Dcollection.configName=myapp_conf
> -Dsolr.solr.home=./myapp -Djava.util.logging.config.file=logging.properties
> -jar start.jar >./myapp/logs/stdout.log 2>./myapp/logs/stderr.log &
> {code}
> The ./myapp/solr.xml looks like this on server1:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The ./myapp/solr.xml looks like this on server2:
> {code:xml}
>
>
>hostContext="solr">
> dataDir="collA_slice1_data" collection="collA" shard="slice1" />
>
>
> {code}
> The first thing we observe is that Solr server1 (running collA_slice1_shard1)
> seems to start up nicely, but when Solr server2 (running collA_slice1_shard2)
> is started up later it quickly reports the following in its solr.log an keeps
> doing that for a long time:
> {code}
> SEVERE: Error while trying to recover:org.apache.solr.common.SolrException:
> Not Found
> request:
> http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2
> at
> org.apache.solr.common.SolrExceptionPropagationHelper.decodeFromMsg(SolrExceptionPropagationHelper.java:40)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:445)
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:264)
> at
> org.apache.solr.cloud.RecoveryStrategy.sendPrepRecoveryCmd(RecoveryStrategy.java:188)
> at
> org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:285)
> at
> org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:206)
> {code}
> Please note that we have changed a little bit in the way errors are logged,
> but basically this means that Solr server2 gets an "404 Not Found" on its
> request
> "http://server1:8983/solr/admin/cores?action=PREPRECOVERY&core=collA_slice1_shard1&nodeName=server2%3A8983_solr&coreNodeName=server2%3A8983_solr_collA_slice1_shard2&state=recovering&checkLive=true&pauseFor=6000&wt=javabin&version=2";
> to Solr server1.
> Seems like there is not a common agreement among the Solr servers on
> how/where to send those requests and how/where to listen for them.
> Regards, Per Steffensen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For
