[jira] [Commented] (KAFKA-1908) Split brain

[ https://issues.apache.org/jira/browse/KAFKA-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15800988#comment-15800988 ] Alexey Ozeritskiy commented on KAFKA-1908: -- Now I think this is not a problem. In the above

[jira] [Commented] (KAFKA-1923) Negative offsets in replication-offset-checkpoint file

[ https://issues.apache.org/jira/browse/KAFKA-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15772787#comment-15772787 ] Alexey Ozeritskiy commented on KAFKA-1923: -- Problem stil exists (v0.10.1.1). Trying to reproduce

[jira] [Updated] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4205: - Status: Patch Available (was: Open) > NullPointerException in fetchOffsetsBefore >

[jira] [Updated] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4205: - Assignee: Anton Karamanov > NullPointerException in fetchOffsetsBefore >

[jira] [Commented] (KAFKA-4205) NullPointerException in fetchOffsetsBefore

[ https://issues.apache.org/jira/browse/KAFKA-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715179#comment-15715179 ] Alexey Ozeritskiy commented on KAFKA-4205: -- We see this on 0.10.1. ~20-30 errors per day on every

[jira] [Commented] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658044#comment-15658044 ] Alexey Ozeritskiy commented on KAFKA-4399: -- As for now I think you can use the following config

[jira] [Updated] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4399: - Status: Patch Available (was: Open) > Deadlock between cleanupGroupMetadata and offset

[jira] [Commented] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658027#comment-15658027 ] Alexey Ozeritskiy commented on KAFKA-4399: -- The simplest way to fix it is to move complicated

[jira] [Updated] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

[ https://issues.apache.org/jira/browse/KAFKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4399: - Attachment: deadlock-stack > Deadlock between cleanupGroupMetadata and offset commit >

[jira] [Created] (KAFKA-4399) Deadlock between cleanupGroupMetadata and offset commit

Alexey Ozeritskiy created KAFKA-4399: Summary: Deadlock between cleanupGroupMetadata and offset commit Key: KAFKA-4399 URL: https://issues.apache.org/jira/browse/KAFKA-4399 Project: Kafka

[jira] [Updated] (KAFKA-4319) AbstractFetcherManager shutdown speedup

[ https://issues.apache.org/jira/browse/KAFKA-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4319: - Status: Patch Available (was: Open) https://github.com/apache/kafka/pull/2023 >

[jira] [Created] (KAFKA-4319) AbstractFetcherManager shutdown speedup

Alexey Ozeritskiy created KAFKA-4319: Summary: AbstractFetcherManager shutdown speedup Key: KAFKA-4319 URL: https://issues.apache.org/jira/browse/KAFKA-4319 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487885#comment-15487885 ] Alexey Ozeritskiy commented on KAFKA-2063: -- Thanks Andrey, I agree with you. > Bound fetch

[jira] [Updated] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2063: - Assignee: Andrey Neporada (was: Alexey Ozeritskiy) > Bound fetch response size (KIP-74)

[jira] [Comment Edited] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485357#comment-15485357 ] Alexey Ozeritskiy edited comment on KAFKA-2063 at 9/12/16 9:37 PM: --- The

[jira] [Commented] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485357#comment-15485357 ] Alexey Ozeritskiy commented on KAFKA-2063: -- The approah KAFKA-3979 is better for configurations

[jira] [Assigned] (KAFKA-2063) Bound fetch response size (KIP-74)

[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy reassigned KAFKA-2063: Assignee: Alexey Ozeritskiy (was: Andrey Neporada) > Bound fetch response size

[jira] [Commented] (KAFKA-4071) Corruptted replication-offset-checkpoint leads to kafka server disfunctional

[ https://issues.apache.org/jira/browse/KAFKA-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431056#comment-15431056 ] Alexey Ozeritskiy commented on KAFKA-4071: -- Thanks [~zanezhang]. Could you attach

[jira] [Updated] (KAFKA-4039) Exit Strategy: using exceptions instead of inline invocation of exit/halt

[ https://issues.apache.org/jira/browse/KAFKA-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-4039: - Attachment: deadlock-stack2 > Exit Strategy: using exceptions instead of inline

[jira] [Commented] (KAFKA-1530) howto update continuously

[ https://issues.apache.org/jira/browse/KAFKA-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425454#comment-15425454 ] Alexey Ozeritskiy commented on KAFKA-1530: -- I think this ticket may be closed

[jira] [Commented] (KAFKA-4039) Exit Strategy: using exceptions instead of inline invocation of exit/halt

[ https://issues.apache.org/jira/browse/KAFKA-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424201#comment-15424201 ] Alexey Ozeritskiy commented on KAFKA-4039: -- Thanks [~maysamyabandeh] I'll be happy to test your

[jira] [Commented] (KAFKA-4039) Exit Strategy: using exceptions instead of inline invocation of exit/halt

[ https://issues.apache.org/jira/browse/KAFKA-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423298#comment-15423298 ] Alexey Ozeritskiy commented on KAFKA-4039: -- Thanks [~maysamyabandeh]. I think we have to decide

[jira] [Resolved] (KAFKA-3979) Optimize memory used by replication process by using adaptive fetch message size

[ https://issues.apache.org/jira/browse/KAFKA-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy resolved KAFKA-3979. -- Resolution: Won't Fix There is a better solution: KAFKA-2063 > Optimize memory used by

[jira] [Commented] (KAFKA-3924) Data loss due to halting when LEO is larger than leader's LEO

[ https://issues.apache.org/jira/browse/KAFKA-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420251#comment-15420251 ] Alexey Ozeritskiy commented on KAFKA-3924: -- IMHO the simplest way to solve the problem is to

[jira] [Updated] (KAFKA-3924) Data loss due to halting when LEO is larger than leader's LEO

[ https://issues.apache.org/jira/browse/KAFKA-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3924: - Attachment: deadlock-stack > Data loss due to halting when LEO is larger than leader's

[jira] [Commented] (KAFKA-3924) Data loss due to halting when LEO is larger than leader's LEO

[ https://issues.apache.org/jira/browse/KAFKA-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419873#comment-15419873 ] Alexey Ozeritskiy commented on KAFKA-3924: -- I've got the deadlock with that patch. Stack traces:

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Issue Type: Improvement (was: Bug) > Halting because log truncation is not allowed and

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Description: When follower wants to truncate partition and it is not allowed it prints

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Description: When follower wants to truncate partition and it is not allowed it print the

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Attachment: KAFKA-3997.patch > Halting because log truncation is not allowed and

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Status: Patch Available (was: Open) > Halting because log truncation is not allowed and

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Description: When follower wants to truncate partition and it is not allowed it print the

[jira] [Updated] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

[ https://issues.apache.org/jira/browse/KAFKA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-3997: - Description: When follower wants to truncate partition and it is not allowed it print the

[jira] [Created] (KAFKA-3997) Halting because log truncation is not allowed and suspicious logging

Alexey Ozeritskiy created KAFKA-3997: Summary: Halting because log truncation is not allowed and suspicious logging Key: KAFKA-3997 URL: https://issues.apache.org/jira/browse/KAFKA-3997 Project:

[jira] [Commented] (KAFKA-3693) Race condition between highwatermark-checkpoint thread and handleLeaderAndIsrRequest at broker start-up

[ https://issues.apache.org/jira/browse/KAFKA-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381452#comment-15381452 ] Alexey Ozeritskiy commented on KAFKA-3693: -- It seems this issue is related to KAFKA-2178 > Race

[jira] [Commented] (KAFKA-1543) Changing replication factor

[ https://issues.apache.org/jira/browse/KAFKA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708037#comment-14708037 ] Alexey Ozeritskiy commented on KAFKA-1543: -- I think refactoring should be a

[jira] [Commented] (KAFKA-1543) Changing replication factor

[ https://issues.apache.org/jira/browse/KAFKA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708039#comment-14708039 ] Alexey Ozeritskiy commented on KAFKA-1543: -- A you sure that your aproach will

[jira] [Updated] (KAFKA-2178) Loss of highwatermarks on incorrect cluster shutdown/restart

[ https://issues.apache.org/jira/browse/KAFKA-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2178: - Status: Patch Available (was: Open) Loss of highwatermarks on incorrect cluster

[jira] [Updated] (KAFKA-2178) Loss of highwatermarks on incorrect cluster shutdown/restart

[ https://issues.apache.org/jira/browse/KAFKA-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2178: - Attachment: KAFKA-2178.patch Loss of highwatermarks on incorrect cluster

[jira] [Created] (KAFKA-2178) Loss of highwatermarks on incorrect cluster shutdown/restart

Alexey Ozeritskiy created KAFKA-2178: Summary: Loss of highwatermarks on incorrect cluster shutdown/restart Key: KAFKA-2178 URL: https://issues.apache.org/jira/browse/KAFKA-2178 Project: Kafka

[jira] [Updated] (KAFKA-2174) Wrong TopicMetadata deserialization

[ https://issues.apache.org/jira/browse/KAFKA-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2174: - Attachment: KAFKA-2174.patch Wrong TopicMetadata deserialization

[jira] [Updated] (KAFKA-2174) Wrong TopicMetadata deserialization

[ https://issues.apache.org/jira/browse/KAFKA-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2174: - Status: Patch Available (was: Open) Wrong TopicMetadata deserialization

[jira] [Created] (KAFKA-2174) Wrong TopicMetadata deserialization

Alexey Ozeritskiy created KAFKA-2174: Summary: Wrong TopicMetadata deserialization Key: KAFKA-2174 URL: https://issues.apache.org/jira/browse/KAFKA-2174 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-2164) ReplicaFetcherThread: suspicious log message on reset offset

[ https://issues.apache.org/jira/browse/KAFKA-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2164: - Status: Patch Available (was: Open) ReplicaFetcherThread: suspicious log message on

[jira] [Updated] (KAFKA-2164) ReplicaFetcherThread: suspicious log message on reset offset

[ https://issues.apache.org/jira/browse/KAFKA-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2164: - Attachment: KAFKA-2164.patch ReplicaFetcherThread: suspicious log message on reset

[jira] [Updated] (KAFKA-2165) ReplicaFetcherThread: data loss on unknown exception

[ https://issues.apache.org/jira/browse/KAFKA-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2165: - Status: Patch Available (was: Open) ReplicaFetcherThread: data loss on unknown

[jira] [Updated] (KAFKA-2165) ReplicaFetcherThread: data loss on unknown exception

[ https://issues.apache.org/jira/browse/KAFKA-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2165: - Attachment: KAFKA-2165.patch ReplicaFetcherThread: data loss on unknown exception

[jira] [Created] (KAFKA-2165) ReplicaFetcherThread: data loss on unknown exception

Alexey Ozeritskiy created KAFKA-2165: Summary: ReplicaFetcherThread: data loss on unknown exception Key: KAFKA-2165 URL: https://issues.apache.org/jira/browse/KAFKA-2165 Project: Kafka

[jira] [Updated] (KAFKA-2164) ReplicaFetcherThread: suspicious log message on reset offset

[ https://issues.apache.org/jira/browse/KAFKA-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-2164: - Description: If log.logEndOffset leaderStartOffset the follower resets its offset and

[jira] [Created] (KAFKA-2133) Deadlock in DeleteTopicsThread

Alexey Ozeritskiy created KAFKA-2133: Summary: Deadlock in DeleteTopicsThread Key: KAFKA-2133 URL: https://issues.apache.org/jira/browse/KAFKA-2133 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-2133) Deadlock in DeleteTopicsThread

[ https://issues.apache.org/jira/browse/KAFKA-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14502028#comment-14502028 ] Alexey Ozeritskiy commented on KAFKA-2133: -- We've set it to 128. I think that

[jira] [Resolved] (KAFKA-2133) Deadlock in DeleteTopicsThread

[ https://issues.apache.org/jira/browse/KAFKA-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy resolved KAFKA-2133. -- Resolution: Fixed Deadlock in DeleteTopicsThread --

[jira] [Commented] (KAFKA-1908) Split brain

[ https://issues.apache.org/jira/browse/KAFKA-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347063#comment-14347063 ] Alexey Ozeritskiy commented on KAFKA-1908: -- Hi all, the following is our

[jira] [Created] (KAFKA-1908) Split brain

Alexey Ozeritskiy created KAFKA-1908: Summary: Split brain Key: KAFKA-1908 URL: https://issues.apache.org/jira/browse/KAFKA-1908 Project: Kafka Issue Type: Bug Components: core

[jira] [Commented] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14287713#comment-14287713 ] Alexey Ozeritskiy commented on KAFKA-1804: -- The last time we saw the bug during

[jira] [Updated] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1804: - Priority: Critical (was: Major) Kafka network thread lacks top exception handler

[jira] [Comment Edited] (KAFKA-1804) Kafka network thread lacks top exception handler

[ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14279396#comment-14279396 ] Alexey Ozeritskiy edited comment on KAFKA-1804 at 1/16/15 7:44 AM:

[jira] [Commented] (KAFKA-1644) Inherit FetchResponse from RequestOrResponse

[ https://issues.apache.org/jira/browse/KAFKA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158114#comment-14158114 ] Alexey Ozeritskiy commented on KAFKA-1644: -- This patch simplifies writing

[jira] [Updated] (KAFKA-1644) Inherit FetchResponse from RequestOrResponse

[ https://issues.apache.org/jira/browse/KAFKA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1644: - Issue Type: Improvement (was: Bug) Inherit FetchResponse from RequestOrResponse

[jira] [Commented] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067872#comment-14067872 ] Alexey Ozeritskiy commented on KAFKA-1414: -- Anton, your patch is not working for

[jira] [Commented] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067917#comment-14067917 ] Alexey Ozeritskiy commented on KAFKA-1414: -- You must create an instance of

[jira] [Comment Edited] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067917#comment-14067917 ] Alexey Ozeritskiy edited comment on KAFKA-1414 at 7/20/14 12:48 PM:

[jira] [Comment Edited] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067917#comment-14067917 ] Alexey Ozeritskiy edited comment on KAFKA-1414 at 7/20/14 12:54 PM:

[jira] [Updated] (KAFKA-1551) Configuration example errors

[ https://issues.apache.org/jira/browse/KAFKA-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1551: - Description: A Production Server Config

[jira] [Created] (KAFKA-1543) Changing replication factor

Alexey Ozeritskiy created KAFKA-1543: Summary: Changing replication factor Key: KAFKA-1543 URL: https://issues.apache.org/jira/browse/KAFKA-1543 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-1543) Changing replication factor

[ https://issues.apache.org/jira/browse/KAFKA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1543: - Attachment: can-change-replication.patch Changing replication factor

[jira] [Updated] (KAFKA-1543) Changing replication factor

[ https://issues.apache.org/jira/browse/KAFKA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1543: - Description: It is difficult to change replication factor by manual editing json config.

[jira] [Updated] (KAFKA-1543) Changing replication factor

[ https://issues.apache.org/jira/browse/KAFKA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1543: - Status: Patch Available (was: Open) Changing replication factor

[jira] [Commented] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14061957#comment-14061957 ] Alexey Ozeritskiy commented on KAFKA-1414: -- Anton, you forget to use new config

[jira] [Updated] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1414: - Attachment: parallel-dir-loading-trunk-threadpool.patch Speedup broker startup after

[jira] [Commented] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056358#comment-14056358 ] Alexey Ozeritskiy commented on KAFKA-1414: -- 1. Ok 2. If any thread fails we get

[jira] [Updated] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1414: - Attachment: parallel-dir-loading-trunk.patch

[jira] [Updated] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1414: - Affects Version/s: (was: 0.8.1) 0.9.0

[jira] [Commented] (KAFKA-1414) Speedup broker startup after hard reset

[ https://issues.apache.org/jira/browse/KAFKA-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13980971#comment-13980971 ] Alexey Ozeritskiy commented on KAFKA-1414: -- What to do with exceptions? Maybe we

[jira] [Updated] (KAFKA-1322) slow startup after unclean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1322: - Resolution: Won't Fix Status: Resolved (was: Patch Available) ok slow startup

[jira] [Commented] (KAFKA-1322) slow startup after unclean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944376#comment-13944376 ] Alexey Ozeritskiy commented on KAFKA-1322: -- Can't reproduce now. I had unclean

[jira] [Created] (KAFKA-1322) slow start on unclean shutdown

Alexey Ozeritskiy created KAFKA-1322: Summary: slow start on unclean shutdown Key: KAFKA-1322 URL: https://issues.apache.org/jira/browse/KAFKA-1322 Project: Kafka Issue Type: Bug

[jira] [Updated] (KAFKA-1322) slow start on unclean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1322: - Status: Patch Available (was: Open) slow start on unclean shutdown

[jira] [Updated] (KAFKA-1322) slow start on unclean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1322: - Attachment: kafka.patch slow start on unclean shutdown --

[jira] [Updated] (KAFKA-1322) slow startup after unclean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Ozeritskiy updated KAFKA-1322: - Summary: slow startup after unclean shutdown (was: slow start on unclean shutdown)

[jira] [Commented] (KAFKA-937) ConsumerFetcherThread can deadlock

[ https://issues.apache.org/jira/browse/KAFKA-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692816#comment-13692816 ] Alexey Ozeritskiy commented on KAFKA-937: - This patch works, thanks.

[jira] [Commented] (KAFKA-937) ConsumerFetcherThread can deadlock

[ https://issues.apache.org/jira/browse/KAFKA-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692418#comment-13692418 ] Alexey Ozeritskiy commented on KAFKA-937: -

[jira] [Comment Edited] (KAFKA-937) ConsumerFetcherThread can deadlock

[ https://issues.apache.org/jira/browse/KAFKA-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692418#comment-13692418 ] Alexey Ozeritskiy edited comment on KAFKA-937 at 6/24/13 9:44 PM: