incubator-blur-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ravikumar Govindarajan <>
Subject Re: All Connections Are Bad...
Date Sat, 10 Dec 2016 10:56:08 GMT
Just now tried to understand the logic...

Whenever an IOException/TTransportException is thrown, we mark a Connection
as bad. Slowly when all Connections are greeted by this, we get "All
Connections Bad..."

Is it a good idea to write a reaper thread to proactively try & replenish
the bad Connection, instead of waiting for search to hit it at the wrong

Also, I just found that "staleness" check is eagerly performed. It should
be possible to return a live connection & refresh stale ones in background?
[*ClientPool.getConnection(Connection conn)*]


On Sat, Dec 10, 2016 at 3:44 PM, Ravikumar Govindarajan <> wrote:

> Often, I find myself bang in the middle of a query, when BlurClientManager
> comes up with this error. Happens both ways. When my app-server talks to
> controller-server as well as controller-server talks to shard-server. This
> is affecting search experience quite a bit nowadays in production!!
> BlurException(message:Unknown error during remote call to node
> [AAA.BB.CCC.DD:40020], stackTraceStr:org.apache.blur.thrift.BadConnectionException:
> Could not connect to controller/shard server. All connections are bad. at
> org.apache.blur.thrift.BlurClientManager.execute(
> at org.apache.blur.thrift.BlurClientManager.execute(
> at org.apache.blur.thrift.BlurControllerServer$BlurClientRemote$
> at org.apache.blur.thrift.BlurControllerServer$BlurClientRemote.execute(
> When do we get such an Exception? In-correct timeout settings or
> shard-server restarts etc...
> Any help is much appreciated
> --
> Ravi

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