[
https://issues.apache.org/jira/browse/KAFKA-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997719#comment-13997719
]
Simon Cooper commented on KAFKA-1352:
-------------------------------------
Another example is when there's an exception in the ReplicaFetcherThread:
{code}
[2014-05-14 12:33:37,811] WARN [ReplicaFetcherThread-0-2], Error in fetch Name:
FetchRequest; Version: 0; CorrelationId: 36409; ClientId:
ReplicaFetcherThread-0-2; ReplicaId: 1; MaxWait: 500 ms; MinBytes: 1 bytes;
RequestInfo: <queues and PartitionFetchInfos>
java.net.ConnectException: Connection refused
at sun.nio.ch.Net.connect0(Native Method)
at sun.nio.ch.Net.connect(Net.java:465)
at sun.nio.ch.Net.connect(Net.java:457)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:670)
at kafka.network.BlockingChannel.connect(BlockingChannel.scala:57)
at kafka.consumer.SimpleConsumer.connect(SimpleConsumer.scala:44)
at kafka.consumer.SimpleConsumer.reconnect(SimpleConsumer.scala:57)
at kafka.consumer.SimpleConsumer.liftedTree1$1(SimpleConsumer.scala:79)
at
kafka.consumer.SimpleConsumer.kafka$consumer$SimpleConsumer$$sendRequest(SimpleConsumer.scala:71)
at
kafka.consumer.SimpleConsumer$$anonfun$fetch$1$$anonfun$apply$mcV$sp$1.apply$mcV$sp(SimpleConsumer.scala:110)
at
kafka.consumer.SimpleConsumer$$anonfun$fetch$1$$anonfun$apply$mcV$sp$1.apply(SimpleConsumer.scala:110)
at
kafka.consumer.SimpleConsumer$$anonfun$fetch$1$$anonfun$apply$mcV$sp$1.apply(SimpleConsumer.scala:110)
at kafka.metrics.KafkaTimer.time(KafkaTimer.scala:33)
at
kafka.consumer.SimpleConsumer$$anonfun$fetch$1.apply$mcV$sp(SimpleConsumer.scala:109)
at
kafka.consumer.SimpleConsumer$$anonfun$fetch$1.apply(SimpleConsumer.scala:109)
at
kafka.consumer.SimpleConsumer$$anonfun$fetch$1.apply(SimpleConsumer.scala:109)
at kafka.metrics.KafkaTimer.time(KafkaTimer.scala:33)
at kafka.consumer.SimpleConsumer.fetch(SimpleConsumer.scala:108)
at
kafka.server.AbstractFetcherThread.processFetchRequest(AbstractFetcherThread.scala:94)
at
kafka.server.AbstractFetcherThread.doWork(AbstractFetcherThread.scala:86)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:51)
[2014-05-14 12:33:37,811] INFO Reconnect due to socket error: null
(kafka.consumer.SimpleConsumer)
{code}
In this case, this error is printed out to the console every *millisecond*,
causing the daemon log file to become *very* large *very* quickly.
> Reduce logging on the server
> ----------------------------
>
> Key: KAFKA-1352
> URL: https://issues.apache.org/jira/browse/KAFKA-1352
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.0, 0.8.1
> Reporter: Neha Narkhede
> Assignee: Ivan Lyutov
> Labels: newbie, usability
> Fix For: 0.8.2
>
> Attachments: KAFKA-1352.patch, KAFKA-1352.patch,
> KAFKA-1352_2014-04-04_21:20:31.patch
>
>
> We have excessive logging in the server, making the logs unreadable and also
> affecting the performance of the server in practice. We need to clean the
> logs to address these issues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
