[
https://issues.apache.org/jira/browse/KAFKA-7574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Maas updated KAFKA-7574:
----------------------------
Description:
The initial error is that Kafka believes it is unable to delete a log segment
file. This causes Kafka to mark the log directory as unavailable and eventually
shut down without flushing data to disk (which is probably the right thing to
do). There are no indications in the OS logs of a failed filesystem or any
other OS level issue. We have verified that filesystem is consistent.
Is there a IO timeout of some kind that can be adjusted or is something else
happening? Potential duplicate of race condition seen in KAFKA-6194.
See attached files for config and example log pattern.
was:
The initial error is that Kafka believes it is unable to delete a log segment
file. This causes Kafka to mark the log directory as unavailable and eventually
shut down without flushing data to disk. There are no indications in the OS
logs of a failed filesystem or any other OS level issue. We have verified that
filesystem is consistent.
Is there a IO timeout of some kind that can be adjusted or is something else
happening? Potential duplicate of race condition seen in KAFKA-6194.
See attached files for config and example log pattern.
> Kafka unable to delete segment file in Linux
> --------------------------------------------
>
> Key: KAFKA-7574
> URL: https://issues.apache.org/jira/browse/KAFKA-7574
> Project: Kafka
> Issue Type: Bug
> Components: core, log
> Affects Versions: 1.0.0
> Environment: Debian Stretch
> Reporter: Ben Maas
> Priority: Major
> Attachments: kafka-config.log, kafka-delete_error_pattern.log
>
>
> The initial error is that Kafka believes it is unable to delete a log segment
> file. This causes Kafka to mark the log directory as unavailable and
> eventually shut down without flushing data to disk (which is probably the
> right thing to do). There are no indications in the OS logs of a failed
> filesystem or any other OS level issue. We have verified that filesystem is
> consistent.
> Is there a IO timeout of some kind that can be adjusted or is something else
> happening? Potential duplicate of race condition seen in KAFKA-6194.
> See attached files for config and example log pattern.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
