[
https://issues.apache.org/jira/browse/FLUME-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890777#comment-15890777
]
ASF GitHub Bot commented on FLUME-3064:
---------------------------------------
GitHub user K0zka opened a pull request:
https://github.com/apache/flume/pull/111
NPE fix
https://issues.apache.org/jira/browse/FLUME-3064
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/K0zka/flume trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flume/pull/111.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 #111
----
commit 89c9b7e4de76b605948aacc3062e26c399743187
Author: Laszlo Hornyak <[email protected]>
Date: 2017-02-28T06:39:53Z
FLUME-3064. warn level logging when exception (instead of info)
Signed-off-by: Laszlo Hornyak <[email protected]>
commit d53c1c0527fdddb3036e7a57a98f9b34d9e7953c
Author: Laszlo Hornyak <[email protected]>
Date: 2017-02-28T06:41:35Z
FLUME-3064. fixed typo: ofset -> offset - to make it easier to search the
logs
Signed-off-by: Laszlo Hornyak <[email protected]>
commit 0c7edca70345baf4228cefb4d09953fcd5dbeefd
Author: Laszlo Hornyak <[email protected]>
Date: 2017-02-28T06:45:34Z
FLUME-3064. fix for NPE: metadata can be null
Signed-off-by: Laszlo Hornyak <[email protected]>
commit fb1871d43a917a46cce563e506b4aae432d20c2d
Author: Laszlo Hornyak <[email protected]>
Date: 2017-02-28T07:42:58Z
FLUME-3064. log level changed from trace to warn when logging exception,
also log the stack trace
Signed-off-by: Laszlo Hornyak <[email protected]>
----
> NullPointerException when communication issue with kafka server
> ---------------------------------------------------------------
>
> Key: FLUME-3064
> URL: https://issues.apache.org/jira/browse/FLUME-3064
> Project: Flume
> Issue Type: Bug
> Components: Kafka Channel, Sinks+Sources
> Affects Versions: v1.7.0
> Environment: logging level must be DEBUG
> Reporter: Laszlo Hornyak
> Priority: Minor
>
> When flume has communication issues with kafka and the logging level is set
> to DEBUG, additionally to the log of the communication error an NPE will be
> thrown. This happens because kafka callback metadata parameter [can be
> null|https://kafka.apache.org/082/javadoc/org/apache/kafka/clients/producer/Callback.html#onCompletion(org.apache.kafka.clients.producer.RecordMetadata,%20java.lang.Exception)],
> this is not handled, but it is only evaluated if the log level is DEBUG.
> The problem affects the kafka source and the channel.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)