Hi,
By saying "client jars" I mean standalone java program that send documents to
sold server.
I assume that you use SolrJ for indexing, like described here :
https://cwiki.apache.org/confluence/display/solr/Using+SolrJ
Updating solr server is one thing, if you are using solr java client, updat
Hello Ahmet,
Thank you for the quick reply.
I'm not sure about the 'client jars' you specified in the mail. JAR files
used in my case are from the tar ball available from the location
http://apache.cs.utah.edu/lucene/solr/4.10.2/solr-4.10.2.tgz
~Regards
Joe
On Tue, Nov 25, 2014 at 1:45 PM, Ahmet
Hi Joe,
StreamingSolrServer is renamed to ConcurrentSolrServer.
I am surprised you see
'StreamingSolrServers' in your logs. May be you need to upgrade your client
jars too?
Ahmet
On Tuesday, November 25, 2014 4:42 AM, Joseph V J
wrote:
Hi Team,
Does this mean that the updates on the other
Hi Team,
Does this mean that the updates on the other server is not getting
forwarded to leader?
Or can this error be safely ignored?
~Regards
Joe
On Mon, Nov 24, 2014 at 12:24 PM, Joseph V J
wrote:
> Hi,
>
> I have a production Solr Cloud setup which has been migrated from 4.2 to
> 4.10.2. U
Hi,
I have a production Solr Cloud setup which has been migrated from 4.2 to
4.10.2. Upon then at times I'm getting this ERROR.
ERROR StreamingSolrServers
org.apache.solr.common.SolrException: Bad Request
request:
http://10.0.0.160:8080/solr/profiles/update?update.distrib=TOLEADER&distrib.from=h
