[
https://issues.apache.org/jira/browse/SOLR-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731793#action_12731793
]
Noble Paul commented on SOLR-1282:
----------------------------------
hi Brian. I made those changes to the code (copying the object before spawning
a new threda) . SO the last nightly should have the fix
> Replication handler's fetchindex command randomly ignores masterUrl parameter
> -----------------------------------------------------------------------------
>
> Key: SOLR-1282
> URL: https://issues.apache.org/jira/browse/SOLR-1282
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 1.4
> Reporter: Brian Loudon
> Assignee: Noble Paul
> Attachments: repl-clone-params.patch, repl-debug.patch
>
>
> The fetchindex command of the replication handler is randomly ignoring the
> value of a specified masterUrl parameter, instead using the masterUrl
> configured in solrconfig.xml.
> Injecting some debugging code shows that the contents of solrParams disappear
> sometime after the thread running doSnapPull() starts in ReplicationHandler's
> handleRequestBody() method.
> This behavior is observed in the most recent nightly build (2009-07-14).
> How to replicate:
> Configure a core as a slave with a masterUrl:
> <requestHandler name="/replication" class="solr.ReplicationHandler">
> <lst name="slave">
> <str name="masterUrl">http://dummy1</str>
> </lst>
> </requestHandler>
> Run the core's fetchindex replication command several times, passing a
> different masterUrl:
> /replication?command=fetchindex&masterUrl=http://dummy2
> Logs show that the configured masterUrl (dummy1) is being used for at
> least half the requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
