[jira] [Commented] (KAFKA-1757) Can not delete Topic index on Windows

[ https://issues.apache.org/jira/browse/KAFKA-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272676#comment-14272676 ] Sriharsha Chintalapani commented on KAFKA-1757: --- [~junrao] On windows Mapped

[jira] [Commented] (KAFKA-1757) Can not delete Topic index on Windows

[ https://issues.apache.org/jira/browse/KAFKA-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272675#comment-14272675 ] Sriharsha Chintalapani commented on KAFKA-1757: --- Created reviewboard https:/

Review Request 29794: Patch for KAFKA-1757

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29794/ --- Review request for kafka. Bugs: KAFKA-1757 https://issues.apache.org/jira/b

[jira] [Updated] (KAFKA-1757) Can not delete Topic index on Windows

[ https://issues.apache.org/jira/browse/KAFKA-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated KAFKA-1757: -- Attachment: KAFKA-1757.patch > Can not delete Topic index on Windows > -

Re: [DISCUSS] Compatability and KIPs

Jay, I totally agree with paying more attention to compatibility across versions. Incompatibility is indeed a big cause of customers' woes. Human checks, stringent reviews, will help, but I think having compatibility tests will be more effective. +INT_MAX for compatibility tests. - Ashish On Fri

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272579#comment-14272579 ] Jay Kreps commented on KAFKA-1853: -- The purpose of the async delete is to avoid locking f

[jira] [Updated] (KAFKA-1855) Topic unusable after unsuccessful UpdateMetadataRequest

[ https://issues.apache.org/jira/browse/KAFKA-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Stein updated KAFKA-1855: - Fix Version/s: 0.8.2 > Topic unusable after unsuccessful UpdateMetadataRequest > -

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Summary: Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the Log

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272498#comment-14272498 ] jaikiran pai commented on KAFKA-1853: - Created reviewboard https://reviews.apache.org/

Re: Review Request 29755: Patch for KAFKA-1853

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29755/ --- (Updated Jan. 10, 2015, 1:37 p.m.) Review request for kafka. Bugs: KAFKA-1853

Re: Review Request 29755: Patch for KAFKA-1853

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29755/ --- (Updated Jan. 10, 2015, 1:34 p.m.) Review request for kafka. Bugs: KAFKA-1853

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename attempt of LogSegment can leak files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272492#comment-14272492 ] jaikiran pai commented on KAFKA-1853: - Hi [~jkreps], you are right about the Java File

[jira] [Commented] (KAFKA-1855) Topic unusable after unsuccessful UpdateMetadataRequest

[ https://issues.apache.org/jira/browse/KAFKA-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272472#comment-14272472 ] Henri Pihkala commented on KAFKA-1855: -- I tried on 0.8.1.1 and didn't see this proble

[jira] [Comment Edited] (KAFKA-1850) Failed reassignment leads to additional replica

[ https://issues.apache.org/jira/browse/KAFKA-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272420#comment-14272420 ] Alex Tian edited comment on KAFKA-1850 at 1/10/15 9:42 AM: --- The

[jira] [Updated] (KAFKA-1850) Failed reassignment leads to additional replica

[ https://issues.apache.org/jira/browse/KAFKA-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Tian updated KAFKA-1850: - Attachment: track_on_testingTopic-9_movement_on_the_following_2_days.txt This attachment is for Jan. 6th a

[jira] [Commented] (KAFKA-1850) Failed reassignment leads to additional replica

[ https://issues.apache.org/jira/browse/KAFKA-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272417#comment-14272417 ] Alex Tian commented on KAFKA-1850: -- Hi Joe, I have attached related log output, just taki

[jira] [Updated] (KAFKA-1850) Failed reassignment leads to additional replica

[ https://issues.apache.org/jira/browse/KAFKA-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Tian updated KAFKA-1850: - Attachment: Track on testingTopic-9's movement.txt > Failed reassignment leads to additional replica > ---

[jira] [Commented] (KAFKA-1850) Failed reassignment leads to additional replica

[ https://issues.apache.org/jira/browse/KAFKA-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272414#comment-14272414 ] Alex Tian commented on KAFKA-1850: -- Hi Joe, Thank you very much for your help. Yeah, I wi