On 5/10/2013 7:42 PM, Michael Sokolov wrote:
> My question is: is this intentional? It's unfortunate that we don't
> seem to be able to update the client and have it continue to work with
> (ie send updates to) the old servers. We have a centralized client
> library that we share across a large number of different installations,
> and getting all the servers upgraded is going to take some time. It
> would be really nice if we could decouple the upgrade efforts.
I have a SolrJ 4.2.1 client that keeps both copies of my index up to
date. A single program runs and updates both, it's not multiple copies.
One of those copies is running 3.5.0 and the other has been upgraded to
4.2.1. I haven't had any trouble with javabin.
Here's a rundown of how I set up my server object. It's more complex
than I remembered making it:
// class fields
private static boolean firstInstance = true;
private static final PoolingClientConnectionManager mgr =
new PoolingClientConnectionManager();
private static final DefaultHttpClient httpClient =
new DefaultHttpClient(mgr);
private HttpSolrServer _querySolr;
// in the constructor
if (firstInstance)
{
firstInstance = false;
mgr.setDefaultMaxPerRoute(25);
mgr.setMaxTotal(1000);
}
serverBaseUrl = "http://"; + serverHost + ":" +
serverPort + "/solr/";
coreBaseUrl = serverBaseUrl + name + "/";
_querySolr = new HttpSolrServer(coreBaseUrl, httpClient);
_querySolr.setMaxRetries(1);
_querySolr.setConnectionTimeout(15000);
I don't know why I'm not having any trouble. I'm certainly glad that
I'm not, though!
Thanks,
Shawn
