[
https://issues.apache.org/jira/browse/SOLR-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196998#comment-13196998
]
Shawn Heisey commented on SOLR-2204:
------------------------------------
bq. I think there's an acceptable workaround for that too. You disable
replication, then upgrade master, then upgrade slave(s) and then enable
replication again. Disabling/enabling polling can be done over HTTP so it's
easily scriptable.
Yes, there are workarounds, but they force you into a rushed upgrade. While
upgrading the master, the index is not being updated. While upgrading the
slaves, it's running single-stranded. Ideally you'd want hours or days for
semi-production testing, a luxury you don't get if you can't upgrade one slave
first and replicate from the older version on the master.
If the application has enough volume to require the services of multiple
slaves, there will be application downtime. Of course any sane company has
built-in maintenance outage times, but how many non-technical management people
are actually sane when it comes to this? Mine are extremely intolerant of
downtime, even if it's planned.
When I upgraded one of my distributed indexes, it was about two weeks before I
was ready to declare it a success and upgrade the other one. I had already
been testing on a dev box with a limited shard collection for several weeks
before that. I did find a few problems, and I was able to simply disable the
index and fall back to the 1.4.1 version that I was keeping updated separately.
> 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: 3.6, 4.0
>
> Attachments: SOLR-2204.patch, SOLR-2204.patch
>
>
> 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.
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
