Sathya,
We're still missing a fair amount of information here though it looks like your
cluster is healthy. How are you indexing and what's the request you're sending
that results in the error you're seeing? Have you checked your nodes' logs for
errors that correspond with the one you're seeing
Hi Greg,
This is my Clusterstate.json.
WatchedEvent state:SyncConnected type:None path:null
[zk: 10.10.1.72:2185(CONNECTED) 0] get /clusterstate.json
{"set_recent":{
"shards":{
"shard1":{
"range":"8000-d554",
"state":"active",
"replicas":{
"10.1
Hi Greg,
This is my Clusterstate.json.
WatchedEvent state:SyncConnected type:None path:null
[zk: 10.10.1.72:2185(CONNECTED) 0] get /clusterstate.json
{"set_recent":{
"shards":{
"shard1":{
"range":"8000-d554",
"state":"active",
"replicas":{
"10.1
Hi Greg,
Where i can find the clusterstate.json.? i have ensemble zookeeper. Can you
please tell me that where i can find it.
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr4-7-No-live-SolrServers-available-to-handle-this-request-tp4125679p4126452.html
Sent f
Excellent, thanks Shalin!
On 3/22/2014 3:32 PM, Shalin Shekhar Mangar wrote:
Thanks Michael! I just committed your fix. It will be released with 4.7.1
On Fri, Mar 21, 2014 at 8:30 PM, Michael Sokolov
wrote:
I just managed to track this down -- as you said the disconnect was a red
herring.
Ul
Thanks Michael! I just committed your fix. It will be released with 4.7.1
On Fri, Mar 21, 2014 at 8:30 PM, Michael Sokolov
wrote:
> I just managed to track this down -- as you said the disconnect was a red
> herring.
>
> Ultimately the problem was caused by a custom analysis component we wrote
>
I just managed to track this down -- as you said the disconnect was a
red herring.
Ultimately the problem was caused by a custom analysis component we
wrote that was raising an IOException -- it was missing some
configuration files it relies on.
What might be interesting for solr devs to hav
Broken pipe errors are generally caused by unexpected disconnections and are
some times hard to track down. Given the stack traces you've provided it's hard
to point to any one thing and I suspect the relevant information was snipped
out in the "long dump of document fields". You might grab the
I'm getting a similar exception when writing documents (on the client
side). I can write one document fine, but the second (which is being
routed to a different shard) generates the error. It happens every time
- definitely not a resource issue or timing problem since this database
is complet
Sathya,
I assume you're using Solr Cloud. Please provide your clusterstate.json while
you're seeing this issue and check your logs for any exceptions. With no
information from you it's hard to troubleshoot any issues!
Thanks,
Greg
On Mar 20, 2014, at 12:44 AM, Sathya wrote:
> Hi Friends,
>
Hi Friends,
I am new to Solr. I have 5 solr node in 5 different machine. When i index
the data, sometimes "*No live SolrServers available to handle this request*"
exception occur in 1 or 2 machines.
I dont know why its happen and how to solve this. Kindly help me to solve
this issue.
--
View
11 matches
Mail list logo
