I am getting the Co ordinator not available error when trace is enabled
on kafka servers.
2018-01-08 19:57:22,088] TRACE [KafkaApi-0] Handling
request:RequestHeader(apiKey=FIND_COORDINATOR, apiVersion=1,
clientId=producer-2, correlationId=563) --
{coordinator_key=NBDEV1$Q4LG13020AVRO2018-01-08 1
2:55:41,coordinator_type=1} from connection 10.211.133.198:9092
-10.55.94.140:57334-380;securityProtocol:PLAINTEXT,principal:User:ANONYMOUS
(kafka.server.KafkaApis)
[2018-01-08 19:57:22,089] TRACE [KafkaApi-0] Sending FindCoordinator
response FindCoordinatorResponse(throttleTimeMs=0, errorMessage='null',
error=COORDINATOR_NOT_AVAILABLE, node=:-1 (id: -1 rack: null)) for
correlation id 563 to client producer-2. (kafka.server.KafkaApis)
[2018-01-08 19:57:22,089] TRACE Socket server received response to send to
10.211.133.198:9092-10.55.94.140:57334-380, registering for write and
sending data: Response(request=Request(processor=2, connection
Id=10.211.133.198:9092-10.55.94.140:57334-380,
session=Session(User:ANONYMOUS,/10.55.94.140),
listenerName=ListenerName(PLAINTEXT), securityProtocol=PLAINTEXT,
buffer=null), responseSend=Some(org.apache.kafk
a.common.network.NetworkSend@67872478), responseAction=SendAction),
responseAsString=Some({throttle_time_ms=0,error_code=15,error_message=null,coordinator={node_id=-1,host=,port=-1}})
(kafka.network.Processo
r)
[2018-01-08 19:57:22,091] TRACE [KafkaApi-0] Handling
request:RequestHeader(apiKey=HEARTBEAT, apiVersion=1,
clientId=_confluent-controlcenter-4-0-0-5-b15126ae-d09a-4b83-9387-e297d871f326-StreamThread-7-consu
mer, correlationId=1330306) --
{group_id=_confluent-controlcenter-4-0-0-5,generation_id=8,member_id=_confluent-controlcenter-4-0-0-5-b15126ae-d09a-4b83-9387-e297d871f326-StreamThread-7-consumer-bb18d5a5-7b3a
-4044-a745-815640103e70} from connection 10.211.133.198:9092
-10.211.133.198:55182-1;securityProtocol:PLAINTEXT,principal:User:ANONYMOUS
(kafka.server.KafkaApis)
[2018-01-08 19:57:22,092] TRACE [KafkaApi-0] Sending heartbeat response
org.apache.kafka.common.requests.HeartbeatResponse@3210e01f for correlation
id 1330306 to client _confluent-controlcenter-4-0-0-5-b1512
6ae-d09a-4b83-9387-e297d871f326-StreamThread-7-consumer.
(kafka.server.KafkaApis)
[2018-01-08 19:57:22,092] TRACE Socket server received response to send to
10.211.133.198:9092-10.211.133.198:55182-1, registering for write and
sending data: Response(request=Request(processor=2, connection
Id=10.211.133.198:9092-10.211.133.198:55182-1,
session=Session(User:ANONYMOUS,/10.211.133.198),
listenerName=ListenerName(PLAINTEXT), securityProtocol=PLAINTEXT,
buffer=null), responseSend=Some(org.apache.ka
fka.common.network.NetworkSend@21e8f193), responseAction=SendAction),
responseAsString=Some({throttle_time_ms=0,error_code=0})
(kafka.network.Processor)
On Mon, Jan 8, 2018 at 12:08 PM, Nishanth S <nishanth.2...@gmail.com> wrote:
> Hi EveryOne,
> We are running into an issue where kafka producer hangs after
> inittransactions api. I have created a new topic and the same issue
> happens intermittently . It is not consistent but occurs more often than
> not . We are running confluent 4.0 and using the below dependencies on
> client side.
>
> Is this an issue with client side dependencies ? Does confluent maintain
> its own version for kafka-clients?
>
> <dependency>
> <!-- https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11 -->
> <groupId>org.apache.kafka</groupId>
> <artifactId>kafka_2.12</artifactId>
> <version>0.11.0.0</version>
> </dependency>
> <dependency>
> <!-- https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11 -->
> <groupId>org.apache.kafka</groupId>
> <artifactId>kafka-clients</artifactId>
> <version>0.11.0.0</version>
> </dependency>
> <dependency>
> <groupId>io.confluent</groupId>
> <artifactId>kafka-avro-serializer</artifactId>
> <!-- For CP 3.0.0 -->
> <version>3.0.0</version>
> </dependency>
>
