Hi
We have 3 brokers connected to Zookeeper using replicated leveldb. Some
times we get the following INFO message on Master
*Client session timed out, have not heard from server in 2xxxms for
sessionid x*
we do have zkSessionTimeout="3s"
and the broker recycles and starts as slave, most of
Thanks for clarifying.
On Feb 2, 2017 6:33 AM, "Christopher Shannon" <
christopher.l.shan...@gmail.com> wrote:
> The broker will continue to work just fine and the index deletion is not
> required. You only need to delete the index file if you want to reclaim
> the wasted space otherwise the fix
Those client logs look like neither broker is accepting a connection (I see
"connection refused" and EOFException). Can you share the broker logs from
the same time period?
Also, your description didn't say anything about multiple brokers; can you
describe what state each is in at the time, how t
The broker will continue to work just fine and the index deletion is not
required. You only need to delete the index file if you want to reclaim
the wasted space otherwise the fix will at least prevent the issue from
getting worse.
On Thu, Feb 2, 2017 at 8:27 AM, Tim Bain wrote:
> Chris,
>
> Wh
Chris,
What will be the behavior for anyone who doesn't delete their index after
upgrading? Will the broker continue to function as-is in that scenario, or
is this a required procedure during an upgrade beyond 5.14.3?
Tim
On Feb 2, 2017 5:02 AM, "Christopher Shannon" <
christopher.l.shan...@gmai
Sorry for taking a while to get back to you.
Based on your originally message and after analyzing some index files I
have actually discovered a bug with KahaDB that causes the index file to
grow too large when things like out of memory errors occur or any unclean
shutdown. On recovery the free pa
Hi Team,
I am using a application where in producer , consumer both uses ActiveMQ
broker..
Problem is after a while either producer or consumer is hanging not
processing any messages,... SO i had to restart broker, producer program and
consumer program as well , then only it is working...
Because