[ https://issues.apache.org/jira/browse/KAFKA-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272263#comment-15272263 ]
ASF GitHub Bot commented on KAFKA-3660: --------------------------------------- GitHub user fpj opened a pull request: https://github.com/apache/kafka/pull/1325 KAFKA-3660: Log exception message in ControllerBrokerRequestBatch You can merge this pull request into a Git repository by running: $ git pull https://github.com/fpj/kafka KAFKA-3660 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1325.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1325 ---- commit e9c9fd342f99e6d4afa2f8fd85321e0c68824608 Author: Flavio Junqueira <f...@apache.org> Date: 2016-05-05T12:48:22Z KAFKA-3660: Log exception message in ControllerBrokerRequestBatch ---- > Log exception message in ControllerBrokerRequestBatch > ----------------------------------------------------- > > Key: KAFKA-3660 > URL: https://issues.apache.org/jira/browse/KAFKA-3660 > Project: Kafka > Issue Type: Sub-task > Affects Versions: 0.9.0.1 > Reporter: Flavio Junqueira > Assignee: Flavio Junqueira > Fix For: 0.10.0.0 > > > In the main task, we observed that the exception that is causing a dirty > batch isn't being logged. We add here to the current logging so that we can > see the exception message to help us debug the main issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)