[jira] [Created] (KAFKA-7908) retention.ms and message.timestamp.difference.max.ms are tied

Ciprian Pascu created KAFKA-7908: Summary: retention.ms and message.timestamp.difference.max.ms are tied Key: KAFKA-7908 URL: https://issues.apache.org/jira/browse/KAFKA-7908 Project: Kafka

[jira] [Commented] (KAFKA-6832) Wrong start position in the log file on the leader, on fetch request.

[ https://issues.apache.org/jira/browse/KAFKA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468558#comment-16468558 ] Ciprian Pascu commented on KAFKA-6832: -- Hi, Unfortunately (or fortunately), I am not

[jira] [Commented] (KAFKA-6832) Wrong start position in the log file on the leader, on fetch request.

[ https://issues.apache.org/jira/browse/KAFKA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463725#comment-16463725 ] Ciprian Pascu commented on KAFKA-6832: -- Also, the content of leader-epoch-checkpoint

[jira] [Commented] (KAFKA-6832) Wrong start position in the log file on the leader, on fetch request.

[ https://issues.apache.org/jira/browse/KAFKA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463689#comment-16463689 ] Ciprian Pascu commented on KAFKA-6832: -- Hi, For us, the problem is easily reproducib

[jira] [Commented] (KAFKA-6832) Wrong start position in the log file on the leader, on fetch request.

[ https://issues.apache.org/jira/browse/KAFKA-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462351#comment-16462351 ] Ciprian Pascu commented on KAFKA-6832: -- Hi, I believe you are right; at the moment,

[jira] [Created] (KAFKA-6832) Wrong start position in the log file on the leader, on fetch request.

Ciprian Pascu created KAFKA-6832: Summary: Wrong start position in the log file on the leader, on fetch request. Key: KAFKA-6832 URL: https://issues.apache.org/jira/browse/KAFKA-6832 Project: Kafka