[jira] [Commented] (KAFKA-7656) ReplicaManager fetch fails on leader due to long/integer overflow

[ https://issues.apache.org/jira/browse/KAFKA-7656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722120#comment-16722120 ] Jason Gustafson commented on KAFKA-7656: [~phaas] I looked at the trace and it se

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722217#comment-16722217 ] Jun Rao commented on KAFKA-7297: [~lindong], good points. The current implementation is n

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722331#comment-16722331 ] Dong Lin commented on KAFKA-7297: - [~junrao] Yeah I agree. [~hzxa21] does this solution s

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722342#comment-16722342 ] Ismael Juma commented on KAFKA-7297: Another way to handle this is for mutating opera

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722347#comment-16722347 ] Dong Lin commented on KAFKA-7297: - [~ijuma] Atomic update is another good alternative to

[jira] [Commented] (KAFKA-7297) Both read/write access to Log.segments should be protected by lock

[ https://issues.apache.org/jira/browse/KAFKA-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722350#comment-16722350 ] Ismael Juma commented on KAFKA-7297: Yeah, you'd lock during writes and keep reads lo

[jira] [Commented] (KAFKA-7581) Issues in building kafka using gradle on a Ubuntu based docker container

[ https://issues.apache.org/jira/browse/KAFKA-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722349#comment-16722349 ] Jordan Moore commented on KAFKA-7581: - I'm not sure I understand the issue here. Are

[jira] [Commented] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722380#comment-16722380 ] Richard Yu commented on KAFKA-3184: --- As Ted pointed out, persistent() in {{InMemoryKeyV

[jira] [Comment Edited] (KAFKA-3184) Add Checkpoint for In-memory State Store

[ https://issues.apache.org/jira/browse/KAFKA-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16722380#comment-16722380 ] Richard Yu edited comment on KAFKA-3184 at 12/16/18 3:59 AM: -

[jira] [Updated] (KAFKA-7719) Improve fairness in SocketServer processors

[ https://issues.apache.org/jira/browse/KAFKA-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cw todd updated KAFKA-7719: --- Attachment: 20181128_005530_609.backup > Improve fairness in SocketServer processors > --

[jira] [Updated] (KAFKA-7374) Tiered Storage

[ https://issues.apache.org/jira/browse/KAFKA-7374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cw todd updated KAFKA-7374: --- Attachment: Google Photos > Tiered Storage > -- > > Key: KAFKA-7374 >