[
https://issues.apache.org/jira/browse/SOLR-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925794#action_12925794
]
Shawn Heisey commented on SOLR-2204:
------------------------------------
All of the Solr documentation I've read says that you're supposed to upgrade
your slaves first, test it completely, then upgrade your masters. This is a
sensible approach, but it's impossible currently.
We can't do complete tests of our application against a single test server, we
need to test against the entire distributed index. The amount of hardware
required for an entire copy of the index costs too much to have in a lab
environment.
> Cross-version replication broken by new javabin format
> ------------------------------------------------------
>
> Key: SOLR-2204
> URL: https://issues.apache.org/jira/browse/SOLR-2204
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 3.1
> Environment: Linux idxst0-a 2.6.18-194.3.1.el5.centos.plusxen #1 SMP
> Wed May 19 09:59:34 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
> Reporter: Shawn Heisey
> Fix For: Next
>
>
> Slave server is branch_3x, revision 1027974. Master server is 1.4.1.
> Replication fails because of the new javabin format.
> SEVERE: Master at: http://HOST:8983/solr/live/replication is not available.
> Index fetch failed. Exception: Invalid version or the data in not in
> 'javabin' format
> Switching Solr's internally generated requests to XML, or adding support for
> both javabin versions would get rid of this problem. I do not know how to do
> either of these things.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
