lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Commented) (JIRA) <>
Subject [jira] [Commented] (SOLR-2204) Cross-version replication broken by new javabin format
Date Mon, 31 Oct 2011 10:08:32 GMT


Jan Høydahl commented on SOLR-2204:

I like how luceneMatchVersion works - clients shouldn't need to worry about JavaBin version
X or XML protocol version Y, they specify the Lucene/Solr version and our code knows what
that means in terms of feature support.

Say we introduced Avro as default streaming format in Solr4.9, but some of our servers are
still at 4.8. We could then upgrade all clients to 4.9 but initialize with version=4.8 when
talking to the old servers, doing fallback to JavaBinV2. For a 1.4.1 server we'd fallback
to v1.
> Cross-version replication broken by new javabin format
> ------------------------------------------------------
>                 Key: SOLR-2204
>                 URL:
>             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.5, 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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message