lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suma Shivaprasad <sumasai.shivapra...@gmail.com>
Subject Re: SolrCloud on 5.2.1 cluster state
Date Thu, 06 Aug 2015 14:00:48 GMT
Thanks for clarifying

On Thu, Aug 6, 2015 at 6:43 PM, Shawn Heisey <apache@elyograg.org> wrote:

> On 8/6/2015 6:50 AM, Suma Shivaprasad wrote:
> > I was having issues since I am using a solr 4.8.1 client to talk to a
> 5.2.1
> > server. There is no API in ZKStateReader as well to add a collection to
> > watch in the 4.8.1 API . I assume that would have caused the
> > clusterstate.json to be updated?
> >
> > Since I am using a third party library (which in turn depends on 4.8.1 )
> >  which I cant upgrade due to some reasons, I was trying to get the older
> > version client to talk to 5.2.1 server.
> >
> > Is there any other way I can get the clusterstate.json to be updated with
> > the collections I am interested in?
>
> Cross-version compatibility is a strong goal with SolrJ, but that is
> mostly applicable to the client objects that have been around since the
> beginning (before SolrCloud entered the picture), like HttpSolrClient.
>
> CloudSolrClient/CloudSolrServer is especially sensitive to version
> differences.  SolrCloud internals are in constant flux currently,
> because devs are frequently thinking of better ways to do things and
> fixing bugs.
>
> If you are able to get any part of a 4.8.1 CloudSolrServer client to
> work with a 5.2.1 SolrCloud install, then I'm impressed, in particular
> because the client is older than the server and the MAJOR version number
> is different.  The older client expects all collections to be in the
> main clusterstate.json, but on a 5.x server, they are not -- each
> collection has its own state.json.
>
> Using a *newer* SolrJ version than your Solr version is much more likely
> to work.
>
> Thanks,
> Shawn
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message