kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jun Rao <...@confluent.io>
Subject Re: fetchrequest and assigned replica issue
Date Thu, 05 Feb 2015 05:35:24 GMT
Which version of Kafka are you using?

Thanks,

Jun

On Wed, Feb 4, 2015 at 11:45 AM, Karts <kartadmin@gmail.com> wrote:

> Hey guys
>
> Seeing the following set of errors when sending messages to the client via
> the API. Thing is 4 out of 5 messages get in, and only one message is being
> lost, and I haven’t been able to pinpoint the culprit. Listed below are the
> only set of errors I see on my kafka out logs. Any advice is greatly
> appreciated . Thanks guys.
>
> BEFORE RESTART:
> Error in fetch Name: FetchRequest; Version: 0; CorrelationId: 3920;
> ClientId: ReplicaFetcherThread-3-2; ReplicaId: 3; MaxWait: 500 ms;
> MinBytes: 1 bytes; RequestInfo: [site.****,7] ->
> PartitionFetchInfo(2341,1048576),[site.****,4] ->
> PartitionFetchInfo(0,1048576),[site.****,5] ->
> PartitionFetchInfo(0,1048576),[site.****,3] ->
> PartitionFetchInfo(2187,1048576),[ERROR.****.consumer.publication,2] ->
> PartitionFetchInfo(0,1048576),[site.****,7] ->
> PartitionFetchInfo(0,1048576),[site.****,0] ->
> PartitionFetchInfo(0,1048576),[site.****,1] ->
> PartitionFetchInfo(0,1048576),[site.****,3] ->
> PartitionFetchInfo(12,1048576) (kafka.server.ReplicaFetcherThread)
>
>
> AFTER RESTART:
> kafka.common.NotAssignedReplicaException: Leader 2 failed to record
> follower 3's position 0 for partition [site.****,7] since the replica 3 is
> not recognized to be one of the assigned replicas  for partition
> [site.****,7]
> [2015-02-04 10:24:50,296] ERROR [ReplicaFetcherThread-2-2], Error in fetch
> Name: FetchRequest; Version: 0; CorrelationId: 4081; ClientId:
> ReplicaFetcherThread-2-2; ReplicaId: 3; MaxWait: 500 ms; MinBytes: 1 bytes;
> RequestInfo: [site.****,6] -> PartitionFetchInfo(0,1048576),[site.****,4]
> -> PartitionFetchInfo(0,1048576),[site.****,7] ->
> PartitionFetchInfo(0,1048576),[EXHAUSTED.site.****.publication,0] ->
> PartitionFetchInfo(0,1048576),[site.****,2] ->
> PartitionFetchInfo(0,1048576),[site.****,3] ->
> PartitionFetchInfo(0,1048576),[site.****,0] ->
> PartitionFetchInfo(0,1048576),[site.****,2] ->
> PartitionFetchInfo(2231,1048576),[site.****,6] ->
> PartitionFetchInfo(2202,1048576) (kafka.server.ReplicaFetcherThread)
>
> [2015-02-04 10:24:50,296] ERROR [ReplicaFetcherThread-3-2], Error in fetch
> Name: FetchRequest; Version: 0; CorrelationId: 3920; ClientId:
> ReplicaFetcherThread-3-2; ReplicaId: 3; MaxWait: 500 ms; MinBytes: 1 bytes;
> RequestInfo: [site.*****,7] ->
> PartitionFetchInfo(2341,1048576),[site.****,4] ->
> PartitionFetchInfo(0,1048576),[site.****,5] ->
> PartitionFetchInfo(0,1048576),[site.****,3] ->
> PartitionFetchInfo(2187,1048576),[ERROR.site.****.publication,2] ->
> PartitionFetchInfo(0,1048576),[site.****,7] ->
> PartitionFetchInfo(0,1048576),[site.****,0] ->
> PartitionFetchInfo(0,1048576),[site.****,1] ->
> PartitionFetchInfo(0,1048576),[site.****,3] ->
> PartitionFetchInfo(12,1048576) (kafka.server.ReplicaFetcherThread)
> java.net.ConnectException: Connection refused
>
> [2015-02-04 10:24:50,357] INFO [Replica Manager on Broker 3]: Shutted down
> completely (kafka.server.ReplicaManager)
> [2015-02-04 10:24:50,918] WARN sleep interrupted (kafka.utils.Utils$)
> java.lang.InterruptedException: sleep interrupted
>         at java.lang.Thread.sleep(Native Method)
>         at
>
> kafka.controller.RequestSendThread$$anonfun$liftedTree1$1$1.apply$mcV$sp(ControllerChannelManager.scala:143)
>         at kafka.utils.Utils$.swallow(Utils.scala:167)
>         at kafka.utils.Logging$class.swallowWarn(Logging.scala:92)
>         at kafka.utils.Utils$.swallowWarn(Utils.scala:46)[2015-02-04
> 10:24:50,296] ERROR [ReplicaFetcherThread-3-2],
>

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