lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Loudon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1282) Replication handler's fetchindex command randomly ignores masterUrl parameter
Date Wed, 15 Jul 2009 15:16:14 GMT

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

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

    Attachment: repl-clone-params.patch

Attached patch which clones the SolrParams instance prior to giving it to doSnapPull.

Note that my knowledge of Java programming is about a week old and was mostly prompted by
this issue, so I'm sure this change is going about things in entirely the wrong way. It does,
however, result in the masterUrl parameter being consistently used on every call to fetchindex.

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


Mime
View raw message