You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Brian Loudon (JIRA)" <ji...@apache.org> on 2009/07/15 17:02:14 UTC

[jira] Updated: (SOLR-1282) Replication handler's fetchindex command randomly ignores masterUrl parameter

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

Brian Loudon updated SOLR-1282:
-------------------------------

    Attachment: repl-debug.patch

Logging added to examine the contents of solrParams on each doSnapPull call.

> 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-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.