yes, Kafka provides those metrics for monitoring the pending requests and
idle request handler, check their documents, you should get it, otherwise,
let me know.
from the operations you did:
1. Restarting service is not help should be expected, since that broker
is already being a bottlenec
Thanks Tony.
How can I check the number of pending requests and the idle percentage
of the requests handler on node 6? Are there any metrics for those?
Controller logs confirm that the controller is not able to send
updateMetadataRequest() to that particular node acting as the follower.
Whereas t
you mentioned:
1. broker disconnection error, normally the case I have ever seen is
when some broker is busy and can not response connection quickly to other
replicas.
2. partitions under-replicated, normally pint to some broker may have a
performance issue.
3. 90% under-replicat
Still hoping for some help here.
On Fri, Dec 7, 2018 at 12:24 AM Suman B N wrote:
> Guys,
> Another observation is 90% of under-replicated partitions have the same
> node as the follower.
>
> *Any help in here is very much appreciated. We have very less time to
> stabilize kafka. Thanks a lot in
Guys,
Another observation is 90% of under-replicated partitions have the same
node as the follower.
*Any help in here is very much appreciated. We have very less time to
stabilize kafka. Thanks a lot in advance.*
-Suman
On Thu, Dec 6, 2018 at 9:08 PM Suman B N wrote:
> +users
>
> On Thu, Dec 6
+users
On Thu, Dec 6, 2018 at 9:01 PM Suman B N wrote:
> Team,
>
> We are observing ISR shrink and expand very frequently. In the logs of the
> follower, below errors are observed:
>
> [2018-12-06 20:00:42,709] WARN [ReplicaFetcherThread-2-15], Error in fetch
> kafka.server.ReplicaFetcherThread$
