[jira] [Resolved] (KAFKA-13685) Seems to get empty event time in some messages.
[ https://issues.apache.org/jira/browse/KAFKA-13685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex resolved KAFKA-13685. -- Resolution: Auto Closed > Seems to get empty event time in some messages. > --- > > Key: KAFKA-13685 > URL: https://issues.apache.org/jira/browse/KAFKA-13685 > Project: Kafka > Issue Type: Bug > Components: consumer, producer >Reporter: Alex >Priority: Critical > > I get these errors in different services occasionally: > Failed to commit stream task 0_7 due to the following error:: > org.apache.kafka.streams.errors.StreamsException: task [0_7] Abort sending > since an error caught with a previous record (key > \x00\x00\x00\x00\x00\x00\x031\x00\x00\x01\x7F\x0FG8\x00 value [B@6b718659 > timestamp null) to topic > snapshot-server-KTABLE-SUPPRESS-STATE-STORE-03-changelog due to > org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for > snapshot-server-KTABLE-SUPPRESS-STATE-STORE-03-changelog-7:120001 ms > has passed since batch creation > > It's only info i get. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (KAFKA-13685) Seems to get empty event time in some messages.
Alex created KAFKA-13685: Summary: Seems to get empty event time in some messages. Key: KAFKA-13685 URL: https://issues.apache.org/jira/browse/KAFKA-13685 Project: Kafka Issue Type: Bug Components: consumer, producer Reporter: Alex I get these errors in different services occasionally: Failed to commit stream task 0_7 due to the following error:: org.apache.kafka.streams.errors.StreamsException: task [0_7] Abort sending since an error caught with a previous record (key \x00\x00\x00\x00\x00\x00\x031\x00\x00\x01\x7F\x0FG8\x00 value [B@6b718659 timestamp null) to topic snapshot-server-KTABLE-SUPPRESS-STATE-STORE-03-changelog due to org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for snapshot-server-KTABLE-SUPPRESS-STATE-STORE-03-changelog-7:120001 ms has passed since batch creation It's only info i get. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (KAFKA-6221) ReplicaFetcherThread throws UnknownTopicOrPartitionExeption on topic creation
Alex created KAFKA-6221:
---
Summary: ReplicaFetcherThread throws
UnknownTopicOrPartitionExeption on topic creation
Key: KAFKA-6221
URL: https://issues.apache.org/jira/browse/KAFKA-6221
Project: Kafka
Issue Type: Bug
Components: core
Affects Versions: 0.10.2.1, 0.10.2.0
Environment: RHEL 7
Reporter: Alex
This issue appeared to happen frequently on 0.10.2.0. On 0.10.2.1 it's a way
harder to reproduce. We'll focus on reproducing it on 0.10.2.1.
*Topology:* 3 brokers, 1 zk.
*Reproducing strategy:* create a few dozens topics (say, 40) one by one, each
with replication factor 2. Number of partitions, generally, does not matter
but, for easier reproduction, should not be very small (around 30 or so).
*CREATE 40 TOPICS:*
for i in {1..40}; do bin/kafka-topics.sh --create --topic "topic${i}_p28_r2"
--partitions 28 --replication-factor 2 --zookeeper :2165; done
{code:java}
*BROKER 1*
[2017-11-15 16:46:00,853] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,27] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,853] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,27] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,9] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,9] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,3] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,3] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,15] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,15] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,21] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,21] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
*BROKER 2*
[2017-11-15 16:46:36,408] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,12] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:36,408] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,12] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:36,410] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,0] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:36,410] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,0] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:36,410] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,6] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16
[jira] [Created] (KAFKA-6220) ReplicaFetcherThread throws UnknownTopicOrPartitionExeption on topic creation
Alex created KAFKA-6220:
---
Summary: ReplicaFetcherThread throws
UnknownTopicOrPartitionExeption on topic creation
Key: KAFKA-6220
URL: https://issues.apache.org/jira/browse/KAFKA-6220
Project: Kafka
Issue Type: Bug
Components: core
Affects Versions: 0.10.2.1, 0.10.2.0
Environment: RHEL 7
Reporter: Alex
This issue appeared to happen frequently on 0.10.2.0. On 0.10.2.1 it's a way
harder to reproduce. We'll focus on reproducing it on 0.10.2.1.
*Topology:* 3 brokers, 1 zk.
*Reproducing strategy:* create a few dozens topics (say, 40) one by one, each
with replication factor 2. Number of partitions, generally, does not matter
but, for easier reproduction, should not be very small (around 30 or so).
*CREATE 40 TOPICS:*
for i in {1..40}; do bin/kafka-topics.sh --create --topic "topic${i}_p28_r2"
--partitions 28 --replication-factor 2 --zookeeper :2165; done
{code:java}
*BROKER 1*
[2017-11-15 16:46:00,853] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,27] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,853] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,27] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,9] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,9] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,3] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,3] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,15] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,15] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,21] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:00,854] ERROR [ReplicaFetcherThread-0-2], Error for partition
[topic1_p28_r2,21] to broker
2:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
*BROKER 2*
[2017-11-15 16:46:36,408] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,12] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:36,408] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,12] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:36,410] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,0] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:36,410] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,0] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16:46:36,410] ERROR [ReplicaFetcherThread-0-3], Error for partition
[topic20_p28_r2,6] to broker
3:org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server
does not host this topic-partition. (kafka.server.ReplicaFetcherThread)
[2017-11-15 16
[jira] [Resolved] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped
[
https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex resolved KAFKA-4367.
-
Resolution: Not A Problem
Not a bug. We had to run kafka-mirror-maker.sh with nohup to completely detach
the process from terminal.
> MirrorMaker shuts down gracefully without actually being stopped
>
>
> Key: KAFKA-4367
> URL: https://issues.apache.org/jira/browse/KAFKA-4367
> Project: Kafka
> Issue Type: Bug
> Components: clients
>Affects Versions: 0.9.0.1
> Environment: RHEL 7
>Reporter: Alex
>
> MirrorMaker stops working without being stopped. From 30 minutes to 20 hours.
> No clue why this problem occurs.
> Start:
> bin/kafka-mirror-maker.sh --new.consumer --consumer.config
> config/ssl_mirroring_consumer.properties --producer.config
> config/ssl_mirroring_producer.properties --whitelist
> "TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null &
>
> kafka-mirror-maker.log
>
> [2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
> CEP.FS.IN-175 with base offset offset 15015 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
> CEP.FS.IN-151 with base offset offset 15066 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,003] TRACE Nodes with data ready to send: [Node(8,
> 10.126.0.2, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,003] TRACE Created 1 produce requests:
> [ClientRequest(expectResponse=true,
> callback=org.apache.kafka.clients.producer.internals.Sender$1@483c4c7a,
> request=RequestSend(header={api_key=0,api_version=1,correlation_id=219685,client_id=producer-1},
>
> body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=133,record_set=java.nio.HeapByteBuffer[pos=0
> lim=9085 cap=16384]}]}]}), createdTimeMs=1478017412003, sendTimeMs=0)]
> (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,008] TRACE Returning fetched records for assigned
> partition CEP.FS.IN-172 and update consumed position to 3869316
> (org.apache.kafka.clients.consumer.internals.Fetcher)
> [2016-11-01 19:23:32,008] TRACE [mirrormaker-thread-7] Sending message with
> value size 485 and offset 3869315 (kafka.tools.MirrorMaker$MirrorMakerThread)
> [2016-11-01 19:23:32,008] TRACE Sending record
> ProducerRecord(topic=CEP.FS.IN, partition=null, key=null, value=[B@12a54f5a
> with callback kafka.tools.MirrorMaker$MirrorMakerProducerCallback@5ea65b8f to
> topic CEP.FS.IN partition 160
> (org.apache.kafka.clients.producer.KafkaProducer)
> [2016-11-01 19:23:32,008] TRACE Allocating a new 16384 byte message buffer
> for topic CEP.FS.IN partition 160
> (org.apache.kafka.clients.producer.internals.RecordAccumulator)
> [2016-11-01 19:23:32,008] TRACE Waking up the sender since topic CEP.FS.IN
> partition 160 is either full or getting a new batch
> (org.apache.kafka.clients.producer.KafkaProducer)
> [2016-11-01 19:23:32,010] TRACE Received produce response from node 7 with
> correlation id 219684 (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
> CEP.FS.IN-106 with base offset offset 15086 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
> CEP.FS.IN-124 with base offset offset 15095 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,010] TRACE Nodes with data ready to send: [Node(7,
> 10.126.0.1, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] INFO Start clean shutdown.
> (kafka.tools.MirrorMaker$)
> [2016-11-01 19:23:32,010] TRACE Created 1 produce requests:
> [ClientRequest(expectResponse=true,
> callback=org.apache.kafka.clients.producer.internals.Sender$1@44b788c7,
> request=RequestSend(header={api_key=0,api_version=1,correlation_id=219686,client_id=producer-1},
>
> body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=160,record_set=java.nio.HeapByteBuffer[pos=0
> lim=511 cap=16384]}]}]}), createdTimeMs=1478017412010, sendTimeMs=0)]
> (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] INFO Shutting down consumer threads.
> (kafka.tools.MirrorMaker$)
> [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0
> shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
> [2016-11-01 19:23:32,011] INFO [mirrormaker-thread
[jira] [Commented] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped
[
https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650572#comment-15650572
]
Alex commented on KAFKA-4367:
-
No, we didn't! That was the issue! Thanks for mentioning. We had to use nohup.
> MirrorMaker shuts down gracefully without actually being stopped
>
>
> Key: KAFKA-4367
> URL: https://issues.apache.org/jira/browse/KAFKA-4367
> Project: Kafka
> Issue Type: Bug
> Components: clients
>Affects Versions: 0.9.0.1
> Environment: RHEL 7
>Reporter: Alex
>
> MirrorMaker stops working without being stopped. From 30 minutes to 20 hours.
> No clue why this problem occurs.
> Start:
> bin/kafka-mirror-maker.sh --new.consumer --consumer.config
> config/ssl_mirroring_consumer.properties --producer.config
> config/ssl_mirroring_producer.properties --whitelist
> "TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null &
>
> kafka-mirror-maker.log
>
> [2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
> CEP.FS.IN-175 with base offset offset 15015 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
> CEP.FS.IN-151 with base offset offset 15066 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,003] TRACE Nodes with data ready to send: [Node(8,
> 10.126.0.2, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,003] TRACE Created 1 produce requests:
> [ClientRequest(expectResponse=true,
> callback=org.apache.kafka.clients.producer.internals.Sender$1@483c4c7a,
> request=RequestSend(header={api_key=0,api_version=1,correlation_id=219685,client_id=producer-1},
>
> body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=133,record_set=java.nio.HeapByteBuffer[pos=0
> lim=9085 cap=16384]}]}]}), createdTimeMs=1478017412003, sendTimeMs=0)]
> (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,008] TRACE Returning fetched records for assigned
> partition CEP.FS.IN-172 and update consumed position to 3869316
> (org.apache.kafka.clients.consumer.internals.Fetcher)
> [2016-11-01 19:23:32,008] TRACE [mirrormaker-thread-7] Sending message with
> value size 485 and offset 3869315 (kafka.tools.MirrorMaker$MirrorMakerThread)
> [2016-11-01 19:23:32,008] TRACE Sending record
> ProducerRecord(topic=CEP.FS.IN, partition=null, key=null, value=[B@12a54f5a
> with callback kafka.tools.MirrorMaker$MirrorMakerProducerCallback@5ea65b8f to
> topic CEP.FS.IN partition 160
> (org.apache.kafka.clients.producer.KafkaProducer)
> [2016-11-01 19:23:32,008] TRACE Allocating a new 16384 byte message buffer
> for topic CEP.FS.IN partition 160
> (org.apache.kafka.clients.producer.internals.RecordAccumulator)
> [2016-11-01 19:23:32,008] TRACE Waking up the sender since topic CEP.FS.IN
> partition 160 is either full or getting a new batch
> (org.apache.kafka.clients.producer.KafkaProducer)
> [2016-11-01 19:23:32,010] TRACE Received produce response from node 7 with
> correlation id 219684 (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
> CEP.FS.IN-106 with base offset offset 15086 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
> CEP.FS.IN-124 with base offset offset 15095 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,010] TRACE Nodes with data ready to send: [Node(7,
> 10.126.0.1, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] INFO Start clean shutdown.
> (kafka.tools.MirrorMaker$)
> [2016-11-01 19:23:32,010] TRACE Created 1 produce requests:
> [ClientRequest(expectResponse=true,
> callback=org.apache.kafka.clients.producer.internals.Sender$1@44b788c7,
> request=RequestSend(header={api_key=0,api_version=1,correlation_id=219686,client_id=producer-1},
>
> body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=160,record_set=java.nio.HeapByteBuffer[pos=0
> lim=511 cap=16384]}]}]}), createdTimeMs=1478017412010, sendTimeMs=0)]
> (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] INFO Shutting down consumer threads.
> (kafka.tools.MirrorMaker$)
> [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0
> shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
> [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-1] mir
[jira] [Commented] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped
[
https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632077#comment-15632077
]
Alex commented on KAFKA-4367:
-
This shouldn't be an issue since we run MirrorMaker detached from terminal: &>
/dev/null &
Yes, it does look like a clean shutdown and that's wierd.
> MirrorMaker shuts down gracefully without actually being stopped
>
>
> Key: KAFKA-4367
> URL: https://issues.apache.org/jira/browse/KAFKA-4367
> Project: Kafka
> Issue Type: Bug
> Components: clients
>Affects Versions: 0.9.0.1
> Environment: RHEL 7
>Reporter: Alex
>
> MirrorMaker stops working without being stopped. From 30 minutes to 20 hours.
> No clue why this problem occurs.
> Start:
> bin/kafka-mirror-maker.sh --new.consumer --consumer.config
> config/ssl_mirroring_consumer.properties --producer.config
> config/ssl_mirroring_producer.properties --whitelist
> "TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null &
>
> kafka-mirror-maker.log
>
> [2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
> CEP.FS.IN-175 with base offset offset 15015 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
> CEP.FS.IN-151 with base offset offset 15066 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,003] TRACE Nodes with data ready to send: [Node(8,
> 10.126.0.2, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,003] TRACE Created 1 produce requests:
> [ClientRequest(expectResponse=true,
> callback=org.apache.kafka.clients.producer.internals.Sender$1@483c4c7a,
> request=RequestSend(header={api_key=0,api_version=1,correlation_id=219685,client_id=producer-1},
>
> body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=133,record_set=java.nio.HeapByteBuffer[pos=0
> lim=9085 cap=16384]}]}]}), createdTimeMs=1478017412003, sendTimeMs=0)]
> (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,008] TRACE Returning fetched records for assigned
> partition CEP.FS.IN-172 and update consumed position to 3869316
> (org.apache.kafka.clients.consumer.internals.Fetcher)
> [2016-11-01 19:23:32,008] TRACE [mirrormaker-thread-7] Sending message with
> value size 485 and offset 3869315 (kafka.tools.MirrorMaker$MirrorMakerThread)
> [2016-11-01 19:23:32,008] TRACE Sending record
> ProducerRecord(topic=CEP.FS.IN, partition=null, key=null, value=[B@12a54f5a
> with callback kafka.tools.MirrorMaker$MirrorMakerProducerCallback@5ea65b8f to
> topic CEP.FS.IN partition 160
> (org.apache.kafka.clients.producer.KafkaProducer)
> [2016-11-01 19:23:32,008] TRACE Allocating a new 16384 byte message buffer
> for topic CEP.FS.IN partition 160
> (org.apache.kafka.clients.producer.internals.RecordAccumulator)
> [2016-11-01 19:23:32,008] TRACE Waking up the sender since topic CEP.FS.IN
> partition 160 is either full or getting a new batch
> (org.apache.kafka.clients.producer.KafkaProducer)
> [2016-11-01 19:23:32,010] TRACE Received produce response from node 7 with
> correlation id 219684 (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
> CEP.FS.IN-106 with base offset offset 15086 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
> CEP.FS.IN-124 with base offset offset 15095 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,010] TRACE Nodes with data ready to send: [Node(7,
> 10.126.0.1, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] INFO Start clean shutdown.
> (kafka.tools.MirrorMaker$)
> [2016-11-01 19:23:32,010] TRACE Created 1 produce requests:
> [ClientRequest(expectResponse=true,
> callback=org.apache.kafka.clients.producer.internals.Sender$1@44b788c7,
> request=RequestSend(header={api_key=0,api_version=1,correlation_id=219686,client_id=producer-1},
>
> body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=160,record_set=java.nio.HeapByteBuffer[pos=0
> lim=511 cap=16384]}]}]}), createdTimeMs=1478017412010, sendTimeMs=0)]
> (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] INFO Shutting down consumer threads.
> (kafka.tools.MirrorMaker$)
> [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0
> shutting down (kafka.tools.MirrorMaker$Mirror
[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped
[
https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex updated KAFKA-4367:
Description:
MirrorMaker stops working without being stopped. From 30 minutes to 20 hours.
No clue why this problem occurs.
Start:
bin/kafka-mirror-maker.sh --new.consumer --consumer.config
config/ssl_mirroring_consumer.properties --producer.config
config/ssl_mirroring_producer.properties --whitelist
"TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null &
kafka-mirror-maker.log
[2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
CEP.FS.IN-175 with base offset offset 15015 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
CEP.FS.IN-151 with base offset offset 15066 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,003] TRACE Nodes with data ready to send: [Node(8,
10.126.0.2, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,003] TRACE Created 1 produce requests:
[ClientRequest(expectResponse=true,
callback=org.apache.kafka.clients.producer.internals.Sender$1@483c4c7a,
request=RequestSend(header={api_key=0,api_version=1,correlation_id=219685,client_id=producer-1},
body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=133,record_set=java.nio.HeapByteBuffer[pos=0
lim=9085 cap=16384]}]}]}), createdTimeMs=1478017412003, sendTimeMs=0)]
(org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,008] TRACE Returning fetched records for assigned
partition CEP.FS.IN-172 and update consumed position to 3869316
(org.apache.kafka.clients.consumer.internals.Fetcher)
[2016-11-01 19:23:32,008] TRACE [mirrormaker-thread-7] Sending message with
value size 485 and offset 3869315 (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,008] TRACE Sending record ProducerRecord(topic=CEP.FS.IN,
partition=null, key=null, value=[B@12a54f5a with callback
kafka.tools.MirrorMaker$MirrorMakerProducerCallback@5ea65b8f to topic CEP.FS.IN
partition 160 (org.apache.kafka.clients.producer.KafkaProducer)
[2016-11-01 19:23:32,008] TRACE Allocating a new 16384 byte message buffer for
topic CEP.FS.IN partition 160
(org.apache.kafka.clients.producer.internals.RecordAccumulator)
[2016-11-01 19:23:32,008] TRACE Waking up the sender since topic CEP.FS.IN
partition 160 is either full or getting a new batch
(org.apache.kafka.clients.producer.KafkaProducer)
[2016-11-01 19:23:32,010] TRACE Received produce response from node 7 with
correlation id 219684 (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
CEP.FS.IN-106 with base offset offset 15086 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
CEP.FS.IN-124 with base offset offset 15095 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,010] TRACE Nodes with data ready to send: [Node(7,
10.126.0.1, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] INFO Start clean shutdown. (kafka.tools.MirrorMaker$)
[2016-11-01 19:23:32,010] TRACE Created 1 produce requests:
[ClientRequest(expectResponse=true,
callback=org.apache.kafka.clients.producer.internals.Sender$1@44b788c7,
request=RequestSend(header={api_key=0,api_version=1,correlation_id=219686,client_id=producer-1},
body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=160,record_set=java.nio.HeapByteBuffer[pos=0
lim=511 cap=16384]}]}]}), createdTimeMs=1478017412010, sendTimeMs=0)]
(org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] INFO Shutting down consumer threads.
(kafka.tools.MirrorMaker$)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-1] mirrormaker-thread-1
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-2] mirrormaker-thread-2
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-3] mirrormaker-thread-3
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-4] mirrormaker-thread-4
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-5] mirrormaker-thread-5
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,012] INFO [mirrormaker-thread-6] mirrorma
[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped
[
https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex updated KAFKA-4367:
Description:
MirrorMaker stops working without being stopped, 30 minutes after start. No
clue why this problem occurs.
Start:
bin/kafka-mirror-maker.sh --new.consumer --consumer.config
config/ssl_mirroring_consumer.properties --producer.config
config/ssl_mirroring_producer.properties --whitelist
"TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null &
kafka-mirror-maker.log
[2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
CEP.FS.IN-175 with base offset offset 15015 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
CEP.FS.IN-151 with base offset offset 15066 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,003] TRACE Nodes with data ready to send: [Node(8,
10.126.0.2, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,003] TRACE Created 1 produce requests:
[ClientRequest(expectResponse=true,
callback=org.apache.kafka.clients.producer.internals.Sender$1@483c4c7a,
request=RequestSend(header={api_key=0,api_version=1,correlation_id=219685,client_id=producer-1},
body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=133,record_set=java.nio.HeapByteBuffer[pos=0
lim=9085 cap=16384]}]}]}), createdTimeMs=1478017412003, sendTimeMs=0)]
(org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,008] TRACE Returning fetched records for assigned
partition CEP.FS.IN-172 and update consumed position to 3869316
(org.apache.kafka.clients.consumer.internals.Fetcher)
[2016-11-01 19:23:32,008] TRACE [mirrormaker-thread-7] Sending message with
value size 485 and offset 3869315 (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,008] TRACE Sending record ProducerRecord(topic=CEP.FS.IN,
partition=null, key=null, value=[B@12a54f5a with callback
kafka.tools.MirrorMaker$MirrorMakerProducerCallback@5ea65b8f to topic CEP.FS.IN
partition 160 (org.apache.kafka.clients.producer.KafkaProducer)
[2016-11-01 19:23:32,008] TRACE Allocating a new 16384 byte message buffer for
topic CEP.FS.IN partition 160
(org.apache.kafka.clients.producer.internals.RecordAccumulator)
[2016-11-01 19:23:32,008] TRACE Waking up the sender since topic CEP.FS.IN
partition 160 is either full or getting a new batch
(org.apache.kafka.clients.producer.KafkaProducer)
[2016-11-01 19:23:32,010] TRACE Received produce response from node 7 with
correlation id 219684 (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
CEP.FS.IN-106 with base offset offset 15086 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
CEP.FS.IN-124 with base offset offset 15095 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,010] TRACE Nodes with data ready to send: [Node(7,
10.126.0.1, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] INFO Start clean shutdown. (kafka.tools.MirrorMaker$)
[2016-11-01 19:23:32,010] TRACE Created 1 produce requests:
[ClientRequest(expectResponse=true,
callback=org.apache.kafka.clients.producer.internals.Sender$1@44b788c7,
request=RequestSend(header={api_key=0,api_version=1,correlation_id=219686,client_id=producer-1},
body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=160,record_set=java.nio.HeapByteBuffer[pos=0
lim=511 cap=16384]}]}]}), createdTimeMs=1478017412010, sendTimeMs=0)]
(org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] INFO Shutting down consumer threads.
(kafka.tools.MirrorMaker$)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-1] mirrormaker-thread-1
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-2] mirrormaker-thread-2
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-3] mirrormaker-thread-3
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-4] mirrormaker-thread-4
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-5] mirrormaker-thread-5
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,012] INFO [mirrormaker-thread-6] mirrormaker-t
[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without actually being stopped
[
https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex updated KAFKA-4367:
Summary: MirrorMaker shuts down gracefully without actually being stopped
(was: MirrorMaker shuts down gracefully without being stopped)
> MirrorMaker shuts down gracefully without actually being stopped
>
>
> Key: KAFKA-4367
> URL: https://issues.apache.org/jira/browse/KAFKA-4367
> Project: Kafka
> Issue Type: Bug
> Components: clients
>Affects Versions: 0.9.0.1
> Environment: RHEL 7
>Reporter: Alex
>
> Start:
> bin/kafka-mirror-maker.sh --new.consumer --consumer.config
> config/ssl_mirroring_consumer.properties --producer.config
> config/ssl_mirroring_producer.properties --whitelist
> "TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null &
> MirrorMaker stops working without being stopped, 30 minutes after start. No
> clue why this problem occurs.
>
> kafka-mirror-maker.log
>
> [2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
> CEP.FS.IN-175 with base offset offset 15015 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
> CEP.FS.IN-151 with base offset offset 15066 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,003] TRACE Nodes with data ready to send: [Node(8,
> 10.126.0.2, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,003] TRACE Created 1 produce requests:
> [ClientRequest(expectResponse=true,
> callback=org.apache.kafka.clients.producer.internals.Sender$1@483c4c7a,
> request=RequestSend(header={api_key=0,api_version=1,correlation_id=219685,client_id=producer-1},
>
> body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=133,record_set=java.nio.HeapByteBuffer[pos=0
> lim=9085 cap=16384]}]}]}), createdTimeMs=1478017412003, sendTimeMs=0)]
> (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,008] TRACE Returning fetched records for assigned
> partition CEP.FS.IN-172 and update consumed position to 3869316
> (org.apache.kafka.clients.consumer.internals.Fetcher)
> [2016-11-01 19:23:32,008] TRACE [mirrormaker-thread-7] Sending message with
> value size 485 and offset 3869315 (kafka.tools.MirrorMaker$MirrorMakerThread)
> [2016-11-01 19:23:32,008] TRACE Sending record
> ProducerRecord(topic=CEP.FS.IN, partition=null, key=null, value=[B@12a54f5a
> with callback kafka.tools.MirrorMaker$MirrorMakerProducerCallback@5ea65b8f to
> topic CEP.FS.IN partition 160
> (org.apache.kafka.clients.producer.KafkaProducer)
> [2016-11-01 19:23:32,008] TRACE Allocating a new 16384 byte message buffer
> for topic CEP.FS.IN partition 160
> (org.apache.kafka.clients.producer.internals.RecordAccumulator)
> [2016-11-01 19:23:32,008] TRACE Waking up the sender since topic CEP.FS.IN
> partition 160 is either full or getting a new batch
> (org.apache.kafka.clients.producer.KafkaProducer)
> [2016-11-01 19:23:32,010] TRACE Received produce response from node 7 with
> correlation id 219684 (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
> CEP.FS.IN-106 with base offset offset 15086 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
> CEP.FS.IN-124 with base offset offset 15095 and error: null.
> (org.apache.kafka.clients.producer.internals.RecordBatch)
> [2016-11-01 19:23:32,010] TRACE Nodes with data ready to send: [Node(7,
> 10.126.0.1, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] INFO Start clean shutdown.
> (kafka.tools.MirrorMaker$)
> [2016-11-01 19:23:32,010] TRACE Created 1 produce requests:
> [ClientRequest(expectResponse=true,
> callback=org.apache.kafka.clients.producer.internals.Sender$1@44b788c7,
> request=RequestSend(header={api_key=0,api_version=1,correlation_id=219686,client_id=producer-1},
>
> body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=160,record_set=java.nio.HeapByteBuffer[pos=0
> lim=511 cap=16384]}]}]}), createdTimeMs=1478017412010, sendTimeMs=0)]
> (org.apache.kafka.clients.producer.internals.Sender)
> [2016-11-01 19:23:32,010] INFO Shutting down consumer threads.
> (kafka.tools.MirrorMaker$)
> [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0
> shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
> [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-1] mir
[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without being stopped
[
https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex updated KAFKA-4367:
Description:
Start:
bin/kafka-mirror-maker.sh --new.consumer --consumer.config
config/ssl_mirroring_consumer.properties --producer.config
config/ssl_mirroring_producer.properties --whitelist
"TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null &
MirrorMaker stops working without being stopped, 30 minutes after start. No
clue why this problem occurs.
kafka-mirror-maker.log
[2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
CEP.FS.IN-175 with base offset offset 15015 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,003] TRACE Produced messages to topic-partition
CEP.FS.IN-151 with base offset offset 15066 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,003] TRACE Nodes with data ready to send: [Node(8,
10.126.0.2, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,003] TRACE Created 1 produce requests:
[ClientRequest(expectResponse=true,
callback=org.apache.kafka.clients.producer.internals.Sender$1@483c4c7a,
request=RequestSend(header={api_key=0,api_version=1,correlation_id=219685,client_id=producer-1},
body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=133,record_set=java.nio.HeapByteBuffer[pos=0
lim=9085 cap=16384]}]}]}), createdTimeMs=1478017412003, sendTimeMs=0)]
(org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,008] TRACE Returning fetched records for assigned
partition CEP.FS.IN-172 and update consumed position to 3869316
(org.apache.kafka.clients.consumer.internals.Fetcher)
[2016-11-01 19:23:32,008] TRACE [mirrormaker-thread-7] Sending message with
value size 485 and offset 3869315 (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,008] TRACE Sending record ProducerRecord(topic=CEP.FS.IN,
partition=null, key=null, value=[B@12a54f5a with callback
kafka.tools.MirrorMaker$MirrorMakerProducerCallback@5ea65b8f to topic CEP.FS.IN
partition 160 (org.apache.kafka.clients.producer.KafkaProducer)
[2016-11-01 19:23:32,008] TRACE Allocating a new 16384 byte message buffer for
topic CEP.FS.IN partition 160
(org.apache.kafka.clients.producer.internals.RecordAccumulator)
[2016-11-01 19:23:32,008] TRACE Waking up the sender since topic CEP.FS.IN
partition 160 is either full or getting a new batch
(org.apache.kafka.clients.producer.KafkaProducer)
[2016-11-01 19:23:32,010] TRACE Received produce response from node 7 with
correlation id 219684 (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
CEP.FS.IN-106 with base offset offset 15086 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,010] TRACE Produced messages to topic-partition
CEP.FS.IN-124 with base offset offset 15095 and error: null.
(org.apache.kafka.clients.producer.internals.RecordBatch)
[2016-11-01 19:23:32,010] TRACE Nodes with data ready to send: [Node(7,
10.126.0.1, 9092)] (org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] INFO Start clean shutdown. (kafka.tools.MirrorMaker$)
[2016-11-01 19:23:32,010] TRACE Created 1 produce requests:
[ClientRequest(expectResponse=true,
callback=org.apache.kafka.clients.producer.internals.Sender$1@44b788c7,
request=RequestSend(header={api_key=0,api_version=1,correlation_id=219686,client_id=producer-1},
body={acks=-1,timeout=3,topic_data=[{topic=CEP.FS.IN,data=[{partition=160,record_set=java.nio.HeapByteBuffer[pos=0
lim=511 cap=16384]}]}]}), createdTimeMs=1478017412010, sendTimeMs=0)]
(org.apache.kafka.clients.producer.internals.Sender)
[2016-11-01 19:23:32,010] INFO Shutting down consumer threads.
(kafka.tools.MirrorMaker$)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-1] mirrormaker-thread-1
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-2] mirrormaker-thread-2
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-3] mirrormaker-thread-3
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-4] mirrormaker-thread-4
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,011] INFO [mirrormaker-thread-5] mirrormaker-thread-5
shutting down (kafka.tools.MirrorMaker$MirrorMakerThread)
[2016-11-01 19:23:32,012] INFO [mirrormaker-thread-6] mirrormaker-t
[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without being stopped
[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex updated KAFKA-4367: Description: Start: bin/kafka-mirror-maker.sh --new.consumer --consumer.config config/ssl_mirroring_consumer.properties --producer.config config/ssl_mirroring_producer.properties --whitelist "TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null & MirrorMaker stops working without being stopped. No clue why this problem occurs. kafka-mirror-maker.log [2016-11-01 19:23:32,010] INFO Shutting down consumer threads. (kafka.tools.MirrorMaker$) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-1] mirrormaker-thread-1 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-2] mirrormaker-thread-2 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-3] mirrormaker-thread-3 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-4] mirrormaker-thread-4 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-5] mirrormaker-thread-5 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-6] mirrormaker-thread-6 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-7] mirrormaker-thread-7 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-8] mirrormaker-thread-8 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-9] mirrormaker-thread-9 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-10] mirrormaker-thread-10 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-11] mirrormaker-thread-11 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-12] mirrormaker-thread-12 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-13] mirrormaker-thread-13 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-14] mirrormaker-thread-14 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-15] mirrormaker-thread-15 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-16] mirrormaker-thread-16 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-17] mirrormaker-thread-17 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-18] mirrormaker-thread-18 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-9] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-11] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-12] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-6] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE [mirrormaker-thread-1] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] INFO [mirrormaker-thread-19] mirrormaker-thread-19 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-13] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] INFO [mirrormaker-thread-13] Flushing producer. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE Flushing accumulated records in producer. (org.apache.kafka.clients.producer.KafkaProducer) [2016-11-01 19:23:32,012] TRACE [mirrormaker-thread-4] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE [mirrormaker-thread-19] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23
[jira] [Updated] (KAFKA-4367) MirrorMaker shuts down gracefully without being stopped
[ https://issues.apache.org/jira/browse/KAFKA-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex updated KAFKA-4367: Description: Start: bin/kafka-mirror-maker.sh --new.consumer --consumer.config config/ssl_mirroring_consumer.properties --producer.config config/ssl_mirroring_producer.properties --whitelist "TOPIC1|TOPIC2|TOPIC3|TOPIC4" --num.streams 20 &> /dev/null & MirrorMaker stops working without being stopped, 30 minutes after start. No clue why this problem occurs. kafka-mirror-maker.log [2016-11-01 19:23:32,010] INFO Shutting down consumer threads. (kafka.tools.MirrorMaker$) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-1] mirrormaker-thread-1 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-2] mirrormaker-thread-2 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-3] mirrormaker-thread-3 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-4] mirrormaker-thread-4 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-5] mirrormaker-thread-5 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-6] mirrormaker-thread-6 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-7] mirrormaker-thread-7 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-8] mirrormaker-thread-8 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-9] mirrormaker-thread-9 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-10] mirrormaker-thread-10 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-11] mirrormaker-thread-11 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-12] mirrormaker-thread-12 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-13] mirrormaker-thread-13 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-14] mirrormaker-thread-14 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-15] mirrormaker-thread-15 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-16] mirrormaker-thread-16 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-17] mirrormaker-thread-17 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-18] mirrormaker-thread-18 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-9] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-11] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-12] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-6] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE [mirrormaker-thread-1] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] INFO [mirrormaker-thread-19] mirrormaker-thread-19 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-13] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] INFO [mirrormaker-thread-13] Flushing producer. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE Flushing accumulated records in producer. (org.apache.kafka.clients.producer.KafkaProducer) [2016-11-01 19:23:32,012] TRACE [mirrormaker-thread-4] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE [mirrormaker-thread-19] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerT
[jira] [Created] (KAFKA-4367) MirrorMaker shuts down gracefully without being stopped
Alex created KAFKA-4367: --- Summary: MirrorMaker shuts down gracefully without being stopped Key: KAFKA-4367 URL: https://issues.apache.org/jira/browse/KAFKA-4367 Project: Kafka Issue Type: Bug Components: clients Affects Versions: 0.9.0.1 Environment: RHEL 7 Reporter: Alex MirrorMaker stops working without being stopped. No clue why this problem occurs. kafka-mirror-maker.log [2016-11-01 19:23:32,010] INFO Shutting down consumer threads. (kafka.tools.MirrorMaker$) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-0] mirrormaker-thread-0 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-1] mirrormaker-thread-1 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-2] mirrormaker-thread-2 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-3] mirrormaker-thread-3 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-4] mirrormaker-thread-4 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,011] INFO [mirrormaker-thread-5] mirrormaker-thread-5 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-6] mirrormaker-thread-6 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-7] mirrormaker-thread-7 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-8] mirrormaker-thread-8 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-9] mirrormaker-thread-9 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-10] mirrormaker-thread-10 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-11] mirrormaker-thread-11 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-12] mirrormaker-thread-12 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-13] mirrormaker-thread-13 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-14] mirrormaker-thread-14 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-15] mirrormaker-thread-15 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-16] mirrormaker-thread-16 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-17] mirrormaker-thread-17 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,012] INFO [mirrormaker-thread-18] mirrormaker-thread-18 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-9] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-11] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-12] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-6] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE [mirrormaker-thread-1] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] INFO [mirrormaker-thread-19] mirrormaker-thread-19 shutting down (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,013] TRACE [mirrormaker-thread-13] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] INFO [mirrormaker-thread-13] Flushing producer. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE Flushing accumulated records in producer. (org.apache.kafka.clients.producer.KafkaProducer) [2016-11-01 19:23:32,012] TRACE [mirrormaker-thread-4] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] TRACE [mirrormaker-thread-19] Caught ConsumerWakeupException, continue iteration. (kafka.tools.MirrorMaker$MirrorMakerThread) [2016-11-01 19:23:32,014] INFO [mirrormaker-threa
[jira] [Created] (KAFKA-4255) Scheme not compatible with
Alex created KAFKA-4255: --- Summary: Scheme not compatible with Key: KAFKA-4255 URL: https://issues.apache.org/jira/browse/KAFKA-4255 Project: Kafka Issue Type: Bug Reporter: Alex Schemes for protocols SASL_PLAINTEXT and SASL_SSL are incorrect since they do not correspond to RFC 3986 (3.1. Scheme, p. 17, https://tools.ietf.org/html/rfc3986#page-17) and are incompatible with java.net.Uri. Correct scheme is: scheme = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." ) That is, underscores should not be used. Possible solution: SASL_SSL -> SASL-SSL SASL_PLAINTEXT -> SASL-PLAINTEXT -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KAFKA-3668) Unable to authenticate Kafka broker to secured Zookeeper
[
https://issues.apache.org/jira/browse/KAFKA-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex closed KAFKA-3668.
---
> Unable to authenticate Kafka broker to secured Zookeeper
>
>
> Key: KAFKA-3668
> URL: https://issues.apache.org/jira/browse/KAFKA-3668
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.9.0.0, 0.9.0.1
> Environment: Red Hat Enterprise Linux Server release 7.0 (Maipo)
> Java 1.8.0_66-b17
> Kafka 0.9.0.0 and 0.9.0.1
>Reporter: Alex
> Fix For: 0.9.0.0, 0.9.0.1
>
>
> Hello,
> we are running into trouble when trying to connect Kafka broker to secured
> Zookeeper, Kerberos protected.
> Configuration is as simple as possible: 1 Zookeeper, 1 Kafka broker and
> Kerberos. All running on local machine.
> Zookeeper successfully starts and receives TGT from Kerberos AS_REQ. Then
> Kafka broker obtains TGT from AS_REQ, but it is unable to get TGS from
> TGS_REQ because as krb5kdc.log shows:
> krb5kdc.log
> ...
> May 06 17:41:42 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545702, etypes
> {rep=18 tkt=18 ses=18}, zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
> krbtgt/ca.sbrf...@ca.sbrf.ru
> May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545864, etypes
> {rep=18 tkt=18 ses=18}, kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
> krbtgt/ca.sbrf...@ca.sbrf.ru
> May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): TGS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: LOOKING_UP_SERVER: authtime 0,
> kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for , Server not
> found in Kerberos database
> What is the possible reason of this problem?
> KAFKA CONFIG:
>
> zookeeper.properties
> dataDir=/tmp/zookeeper
> clientPort=2181
>
> authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider
> jaasLoginRenew=360
>
> server.properties
> broker.id=0
> log.dirs=/tmp/kafka-logs
> listeners=SASL_PLAINTEXT://10.116.93.88:9092
> security.inter.broker.protocol=SASL_PLAINTEXT
> zookeeper.connect=10.116.93.88:2181
> sasl.kerberos.service.name=kafka
> authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
> zookeeper.set.acl=true
> #allow.everyone.if.no.acl.found=true
> #sasl.enabled.mechanisms=GSSAPI
> #sasl.mechanism.inter.broker.protocol=GSSAPI
> JVM params:
> Kafka:
> -Djava.security.krb5.conf=/etc/krb5.conf
>
> -Djava.security.auth.login.config=config/kafka-broker-jaas.conf
> Zookeeper:
> -Djava.security.krb5.conf=/etc/krb5.conf
> -Djava.security.auth.login.config=config/zookeeper.conf
>
> JAAS files:
> kafka-broker-jaas.conf:
> KafkaServer {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> storeKey=true
> keyTab="/etc/security/keytabs/kafka.keytab"
> debug=true
> useTicketCache=false
>
> principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> Client {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> storeKey=true
> keyTab="/etc/security/keytabs/kafka.keytab"
> debug=true
> useTicketCache=false
>
> principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> zookeeper-jaas.conf
> Server {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> keyTab="/etc/security/keytabs/zookeeper.keytab"
> storeKey=true
> useTicketCache=false
> debug=true
>
> principal="zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> KERBEROS 5 CONFIG:
> krb5.conf
> [logging]
>default = FILE:/var/log/krb5libs.log
>kdc = FILE:/var/log/krb5k
[jira] [Resolved] (KAFKA-3668) Unable to authenticate Kafka broker to secured Zookeeper
[
https://issues.apache.org/jira/browse/KAFKA-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex resolved KAFKA-3668.
-
Resolution: Not A Bug
> Unable to authenticate Kafka broker to secured Zookeeper
>
>
> Key: KAFKA-3668
> URL: https://issues.apache.org/jira/browse/KAFKA-3668
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.9.0.0, 0.9.0.1
> Environment: Red Hat Enterprise Linux Server release 7.0 (Maipo)
> Java 1.8.0_66-b17
> Kafka 0.9.0.0 and 0.9.0.1
>Reporter: Alex
> Fix For: 0.9.0.1, 0.9.0.0
>
>
> Hello,
> we are running into trouble when trying to connect Kafka broker to secured
> Zookeeper, Kerberos protected.
> Configuration is as simple as possible: 1 Zookeeper, 1 Kafka broker and
> Kerberos. All running on local machine.
> Zookeeper successfully starts and receives TGT from Kerberos AS_REQ. Then
> Kafka broker obtains TGT from AS_REQ, but it is unable to get TGS from
> TGS_REQ because as krb5kdc.log shows:
> krb5kdc.log
> ...
> May 06 17:41:42 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545702, etypes
> {rep=18 tkt=18 ses=18}, zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
> krbtgt/ca.sbrf...@ca.sbrf.ru
> May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545864, etypes
> {rep=18 tkt=18 ses=18}, kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
> krbtgt/ca.sbrf...@ca.sbrf.ru
> May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): TGS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: LOOKING_UP_SERVER: authtime 0,
> kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for , Server not
> found in Kerberos database
> What is the possible reason of this problem?
> KAFKA CONFIG:
>
> zookeeper.properties
> dataDir=/tmp/zookeeper
> clientPort=2181
>
> authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider
> jaasLoginRenew=360
>
> server.properties
> broker.id=0
> log.dirs=/tmp/kafka-logs
> listeners=SASL_PLAINTEXT://10.116.93.88:9092
> security.inter.broker.protocol=SASL_PLAINTEXT
> zookeeper.connect=10.116.93.88:2181
> sasl.kerberos.service.name=kafka
> authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
> zookeeper.set.acl=true
> #allow.everyone.if.no.acl.found=true
> #sasl.enabled.mechanisms=GSSAPI
> #sasl.mechanism.inter.broker.protocol=GSSAPI
> JVM params:
> Kafka:
> -Djava.security.krb5.conf=/etc/krb5.conf
>
> -Djava.security.auth.login.config=config/kafka-broker-jaas.conf
> Zookeeper:
> -Djava.security.krb5.conf=/etc/krb5.conf
> -Djava.security.auth.login.config=config/zookeeper.conf
>
> JAAS files:
> kafka-broker-jaas.conf:
> KafkaServer {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> storeKey=true
> keyTab="/etc/security/keytabs/kafka.keytab"
> debug=true
> useTicketCache=false
>
> principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> Client {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> storeKey=true
> keyTab="/etc/security/keytabs/kafka.keytab"
> debug=true
> useTicketCache=false
>
> principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> zookeeper-jaas.conf
> Server {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> keyTab="/etc/security/keytabs/zookeeper.keytab"
> storeKey=true
> useTicketCache=false
> debug=true
>
> principal="zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> KERBEROS 5 CONFIG:
> krb5.conf
> [logging]
>default = FILE:/var/log/krb5libs.log
>
[jira] [Updated] (KAFKA-3668) Unable to authenticate Kafka broker to secured Zookeeper
[
https://issues.apache.org/jira/browse/KAFKA-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex updated KAFKA-3668:
Description:
Hello,
we are running into trouble when trying to connect Kafka broker to secured
Zookeeper, Kerberos protected.
Configuration is as simple as possible: 1 Zookeeper, 1 Kafka broker and
Kerberos. All running on local machine.
Zookeeper successfully starts and receives TGT from Kerberos AS_REQ. Then Kafka
broker obtains TGT from AS_REQ, but it is unable to get TGS from TGS_REQ
because as krb5kdc.log shows:
krb5kdc.log
...
May 06 17:41:42 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545702, etypes {rep=18
tkt=18 ses=18}, zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
krbtgt/ca.sbrf...@ca.sbrf.ru
May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545864, etypes {rep=18
tkt=18 ses=18}, kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
krbtgt/ca.sbrf...@ca.sbrf.ru
May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): TGS_REQ (4
etypes {18 17 16 23}) 10.116.93.88: LOOKING_UP_SERVER: authtime 0,
kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for , Server not found
in Kerberos database
What is the possible reason of this problem?
KAFKA CONFIG:
zookeeper.properties
dataDir=/tmp/zookeeper
clientPort=2181
authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider
jaasLoginRenew=360
server.properties
broker.id=0
log.dirs=/tmp/kafka-logs
listeners=SASL_PLAINTEXT://10.116.93.88:9092
security.inter.broker.protocol=SASL_PLAINTEXT
zookeeper.connect=10.116.93.88:2181
sasl.kerberos.service.name=kafka
authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
zookeeper.set.acl=true
#allow.everyone.if.no.acl.found=true
#sasl.enabled.mechanisms=GSSAPI
#sasl.mechanism.inter.broker.protocol=GSSAPI
JVM params:
Kafka:
-Djava.security.krb5.conf=/etc/krb5.conf
-Djava.security.auth.login.config=config/kafka-broker-jaas.conf
Zookeeper:
-Djava.security.krb5.conf=/etc/krb5.conf
-Djava.security.auth.login.config=config/zookeeper.conf
JAAS files:
kafka-broker-jaas.conf:
KafkaServer {
com.sun.security.auth.module.Krb5LoginModule
required
useKeyTab=true
storeKey=true
keyTab="/etc/security/keytabs/kafka.keytab"
debug=true
useTicketCache=false
principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
};
Client {
com.sun.security.auth.module.Krb5LoginModule
required
useKeyTab=true
storeKey=true
keyTab="/etc/security/keytabs/kafka.keytab"
debug=true
useTicketCache=false
principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
};
zookeeper-jaas.conf
Server {
com.sun.security.auth.module.Krb5LoginModule
required
useKeyTab=true
keyTab="/etc/security/keytabs/zookeeper.keytab"
storeKey=true
useTicketCache=false
debug=true
principal="zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
};
KERBEROS 5 CONFIG:
krb5.conf
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
dns_lookup_realm = false
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true
rdns = false
default_realm = CA.SBRF.RU
default_ccache_name = KEYRING:persistent:%{uid}
[realms]
CA.SBRF.RU = {
kdc = SBT-IPO-204.ca.sbrf.ru
admin_server = SBT-IPO-204.ca.
[jira] [Reopened] (KAFKA-3668) Unable to authenticate Kafka broker to secured Zookeeper
[
https://issues.apache.org/jira/browse/KAFKA-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex reopened KAFKA-3668:
-
> Unable to authenticate Kafka broker to secured Zookeeper
>
>
> Key: KAFKA-3668
> URL: https://issues.apache.org/jira/browse/KAFKA-3668
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.9.0.0, 0.9.0.1
> Environment: Red Hat Enterprise Linux Server release 7.0 (Maipo)
> Java 1.8.0_66-b17
> Kafka 0.9.0.0 and 0.9.0.1
>Reporter: Alex
> Fix For: 0.9.0.0, 0.9.0.1
>
>
> Hello,
> we are running into trouble when trying to connect Kafka broker to secured
> Zookeeper, Kerberos protected.
> Configuration is as simple as possible: 1 Zookeeper, 1 Kafka broker and
> Kerberos. All running on local machine.
> Zookeeper successfully starts and receives TGT from Kerberos AS_REQ. Then
> Kafka broker obtains TGT from AS_REQ, but it is unable to get TGS from
> TGS_REQ because as krb5kdc.log shows:
> krb5kdc.log
> ...
> May 06 17:41:42 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545702, etypes
> {rep=18 tkt=18 ses=18}, zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
> krbtgt/ca.sbrf...@ca.sbrf.ru
> May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545864, etypes
> {rep=18 tkt=18 ses=18}, kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
> krbtgt/ca.sbrf...@ca.sbrf.ru
> May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): TGS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: LOOKING_UP_SERVER: authtime 0,
> kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for , Server not
> found in Kerberos database
> What is the possible reason of this problem?
> KAFKA CONFIG:
>
> zookeeper.properties
> dataDir=/tmp/zookeeper
> clientPort=2181
>
> authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider
> jaasLoginRenew=360
>
> server.properties
> broker.id=0
> log.dirs=/tmp/kafka-logs
> listeners=SASL_PLAINTEXT://10.116.93.88:9092
> security.inter.broker.protocol=SASL_PLAINTEXT
> zookeeper.connect=10.116.93.88:2181
> sasl.kerberos.service.name=kafka
> authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
> zookeeper.set.acl=true
> #allow.everyone.if.no.acl.found=true
> #sasl.enabled.mechanisms=GSSAPI
> #sasl.mechanism.inter.broker.protocol=GSSAPI
> JVM params:
> Kafka:
> -Djava.security.krb5.conf=/etc/krb5.conf
>
> -Djava.security.auth.login.config=config/kafka-broker-jaas.conf
> Zookeeper:
> -Djava.security.krb5.conf=/etc/krb5.conf
> -Djava.security.auth.login.config=config/zookeeper.conf
>
> JAAS files:
> kafka-broker-jaas.conf:
> KafkaServer {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> storeKey=true
> keyTab="/etc/security/keytabs/kafka.keytab"
> debug=true
> useTicketCache=false
>
> principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> Client {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> storeKey=true
> keyTab="/etc/security/keytabs/kafka.keytab"
> debug=true
> useTicketCache=false
>
> principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> zookeeper-jaas.conf
> Server {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> keyTab="/etc/security/keytabs/zookeeper.keytab"
> storeKey=true
> useTicketCache=false
> debug=true
>
> principal="zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> KERBEROS 5 CONFIG:
> krb5.conf
> [logging]
>default = FILE:/var/log/krb5libs.log
>kdc = FILE:/var/log/k
[jira] [Resolved] (KAFKA-3668) Unable to authenticate Kafka broker to secured Zookeeper
[
https://issues.apache.org/jira/browse/KAFKA-3668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex resolved KAFKA-3668.
-
Resolution: Not A Bug
> Unable to authenticate Kafka broker to secured Zookeeper
>
>
> Key: KAFKA-3668
> URL: https://issues.apache.org/jira/browse/KAFKA-3668
> Project: Kafka
> Issue Type: Bug
>Affects Versions: 0.9.0.0, 0.9.0.1
> Environment: Red Hat Enterprise Linux Server release 7.0 (Maipo)
> Java 1.8.0_66-b17
> Kafka 0.9.0.0 and 0.9.0.1
>Reporter: Alex
> Fix For: 0.9.0.1, 0.9.0.0
>
>
> Hello,
> we are running into trouble when trying to connect Kafka broker to secured
> Zookeeper, Kerberos protected.
> Configuration is as simple as possible: 1 Zookeeper, 1 Kafka broker and
> Kerberos. All running on local machine.
> Zookeeper successfully starts and receives TGT from Kerberos AS_REQ. Then
> Kafka broker obtains TGT from AS_REQ, but it is unable to get TGS from
> TGS_REQ because as krb5kdc.log shows:
> krb5kdc.log
> ...
> May 06 17:41:42 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545702, etypes
> {rep=18 tkt=18 ses=18}, zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
> krbtgt/ca.sbrf...@ca.sbrf.ru
> May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545864, etypes
> {rep=18 tkt=18 ses=18}, kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
> krbtgt/ca.sbrf...@ca.sbrf.ru
> May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): TGS_REQ (4
> etypes {18 17 16 23}) 10.116.93.88: LOOKING_UP_SERVER: authtime 0,
> kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for , Server not
> found in Kerberos database
> What is the possible reason of this problem?
> KAFKA CONFIG:
>
> zookeeper.properties
> dataDir=/tmp/zookeeper
> clientPort=2181
>
> authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider
> jaasLoginRenew=360
>
> server.properties
> broker.id=0
> log.dirs=/tmp/kafka-logs
> listeners=SASL_PLAINTEXT://10.116.93.88:9092
> security.inter.broker.protocol=SASL_PLAINTEXT
> zookeeper.connect=10.116.93.88:2181
> sasl.kerberos.service.name=kafka
> authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
> zookeeper.set.acl=true
> #allow.everyone.if.no.acl.found=true
> #sasl.enabled.mechanisms=GSSAPI
> #sasl.mechanism.inter.broker.protocol=GSSAPI
> JVM params:
> Kafka:
> -Djava.security.krb5.conf=/etc/krb5.conf
>
> -Djava.security.auth.login.config=config/kafka-broker-jaas.conf
> Zookeeper:
> -Djava.security.krb5.conf=/etc/krb5.conf
> -Djava.security.auth.login.config=config/zookeeper.conf
>
> JAAS files:
> kafka-broker-jaas.conf:
> KafkaServer {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> storeKey=true
> keyTab="/etc/security/keytabs/kafka.keytab"
> debug=true
> useTicketCache=false
>
> principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> Client {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> storeKey=true
> keyTab="/etc/security/keytabs/kafka.keytab"
> debug=true
> useTicketCache=false
>
> principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> zookeeper-jaas.conf
> Server {
> com.sun.security.auth.module.Krb5LoginModule
> required
> useKeyTab=true
> keyTab="/etc/security/keytabs/zookeeper.keytab"
> storeKey=true
> useTicketCache=false
> debug=true
>
> principal="zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
> };
> KERBEROS 5 CONFIG:
> krb5.conf
> [logging]
>default = FILE:/var/log/krb5libs.log
>
[jira] [Created] (KAFKA-3668) Unable to authenticate Kafka broker to secured Zookeeper
Alex created KAFKA-3668:
---
Summary: Unable to authenticate Kafka broker to secured Zookeeper
Key: KAFKA-3668
URL: https://issues.apache.org/jira/browse/KAFKA-3668
Project: Kafka
Issue Type: Bug
Affects Versions: 0.9.0.1, 0.9.0.0
Environment: Red Hat Enterprise Linux Server release 7.0 (Maipo)
Java 1.8.0_66-b17
Kafka 0.9.0.0 and 0.9.0.1
Reporter: Alex
Fix For: 0.9.0.1, 0.9.0.0
Hello,
we are running into trouble when trying to connect Kafka broker to secured
Zookeeper, Kerberos protected.
Configuration is as simple as possible: 1 Zookeeper, 1 Kafka broker and
Kerberos. All running on local machine.
Zookeeper successfully starts and receives TGT from Kerberos AS_REQ. Then Kafka
broker obtains TGT from AS_REQ, but it is unable to get TGS from TGS_REQ
because as krb5kdc.log shows:
krb5kdc.log
...
May 06 17:41:42 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545702, etypes {rep=18
tkt=18 ses=18}, zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
krbtgt/ca.sbrf...@ca.sbrf.ru
May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): AS_REQ (4
etypes {18 17 16 23}) 10.116.93.88: ISSUE: authtime 1462545864, etypes {rep=18
tkt=18 ses=18}, kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for
krbtgt/ca.sbrf...@ca.sbrf.ru
May 06 17:44:24 SBT-IPO-204.ca.sbrf.ru krb5kdc[1580](info): TGS_REQ (4
etypes {18 17 16 23}) 10.116.93.88: LOOKING_UP_SERVER: authtime 0,
kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru for , Server not found
in Kerberos database
What is the possible reason of this problem?
KAFKA CONFIG:
zookeeper.properties
dataDir=/tmp/zookeeper
clientPort=2181
authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider
jaasLoginRenew=360
server.properties
broker.id=0
log.dirs=/tmp/kafka-logs
listeners=SASL_PLAINTEXT://10.116.93.88:9092
security.inter.broker.protocol=SASL_PLAINTEXT
zookeeper.connect=10.116.93.88:2181
sasl.kerberos.service.name=kafka
authorizer.class.name=kafka.security.auth.SimpleAclAuthorizer
zookeeper.set.acl=true
#allow.everyone.if.no.acl.found=true
#sasl.enabled.mechanisms=GSSAPI
#sasl.mechanism.inter.broker.protocol=GSSAPI
JVM params:
Kafka:
-Djava.security.krb5.conf=/etc/krb5.conf
-Djava.security.auth.login.config=config/kafka-broker-jaas.conf
Zookeeper:
-Djava.security.krb5.conf=/etc/krb5.conf
-Djava.security.auth.login.config=config/zookeeper.conf
JAAS files:
kafka-broker-jaas.conf:
KafkaServer {
com.sun.security.auth.module.Krb5LoginModule
required
useKeyTab=true
storeKey=true
keyTab="/etc/security/keytabs/kafka.keytab"
debug=true
useTicketCache=false
principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
};
Client {
com.sun.security.auth.module.Krb5LoginModule
required
useKeyTab=true
storeKey=true
keyTab="/etc/security/keytabs/kafka.keytab"
debug=true
useTicketCache=false
principal="kafka/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
};
zookeeper-jaas.conf
Server {
com.sun.security.auth.module.Krb5LoginModule
required
useKeyTab=true
keyTab="/etc/security/keytabs/zookeeper.keytab"
storeKey=true
useTicketCache=false
debug=true
principal="zookeeper/sbt-ipo-204.ca.sbrf...@ca.sbrf.ru";
};
KERBEROS 5 CONFIG:
krb5.conf
[logging]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
[libdefaults]
dns_lookup_realm = false
ticket_lifetime = 24h
renew_lifetime = 7d
