This is still occurring for us. In addition, it has started occurring on
one of the six nodes in the "healthy" cluster, for no reason we have been
able to determine.
We're willing to put in some serious time to help debug/solve this, but we
need *some* hint as to where to start. I understand that
On Tue, Apr 14, 2015 at 8:31 PM, Jiangjie Qin
wrote:
> Hey Evan,
>
> Is this issue only observed when mirror maker is consuming? It looks that
> for Cluster A you have some other consumers.
> Do you mean if you stop mirror maker the problem goes away?
>
Yes, exactly. The setup is A -> Mirrormake
Hey Evan,
Is this issue only observed when mirror maker is consuming? It looks that
for Cluster A you have some other consumers.
Do you mean if you stop mirror maker the problem goes away?
Jiangjie (Becket) Qin
On 4/14/15, 6:55 AM, "Evan Huus" wrote:
>Any ideas on this? It's still occurring...
Any ideas on this? It's still occurring...
Is there a separate mailing list or project for mirrormaker that I could
ask?
Thanks,
Evan
On Thu, Apr 9, 2015 at 4:36 PM, Evan Huus wrote:
> Hey Folks, we're running into an odd issue with mirrormaker and the fetch
> request purgatory on the brokers.
Hey Folks, we're running into an odd issue with mirrormaker and the fetch
request purgatory on the brokers. Our setup consists of two six-node
clusters (all running 0.8.2.1 on identical hw with the same config). All
"normal" producing and consuming happens on cluster A. Mirrormaker has been
set up
