[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1755: Resolution: Fixed Fix Version/s: 0.9.0.0 Status: Resolved (was: Patch Available) This was in fact committed to trunk and is in 0.9.0.0: commit 1cd6ed9e2c07a63474ed80a8224bd431d5d4243c Joel Koshy committed on Mar 3 https://github.com/apache/kafka/commit/1cd6ed9e2c07a63474ed80a8224bd431d5d4243c#diff-d7330411812d23e8a34889bee42fedfe > Improve error handling in log cleaner > - > > Key: KAFKA-1755 > URL: https://issues.apache.org/jira/browse/KAFKA-1755 > Project: Kafka > Issue Type: Bug >Reporter: Joel Koshy >Assignee: Joel Koshy > Labels: newbie++ > Fix For: 0.9.0.0 > > Attachments: KAFKA-1755.patch, KAFKA-1755_2015-02-23_14:29:54.patch, > KAFKA-1755_2015-02-26_10:54:50.patch > > > The log cleaner is a critical process when using compacted topics. > However, if there is any error in any topic (notably if a key is missing) > then the cleaner exits and all other compacted topics will also be adversely > affected - i.e., compaction stops across the board. > This can be improved by just aborting compaction for a topic on any error and > keep the thread from exiting. > Another improvement would be to reject messages without keys that are sent to > compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1755: Fix Version/s: (was: 0.8.3) > Improve error handling in log cleaner > - > > Key: KAFKA-1755 > URL: https://issues.apache.org/jira/browse/KAFKA-1755 > Project: Kafka > Issue Type: Bug >Reporter: Joel Koshy >Assignee: Joel Koshy > Labels: newbie++ > Attachments: KAFKA-1755.patch, KAFKA-1755_2015-02-23_14:29:54.patch, > KAFKA-1755_2015-02-26_10:54:50.patch > > > The log cleaner is a critical process when using compacted topics. > However, if there is any error in any topic (notably if a key is missing) > then the cleaner exits and all other compacted topics will also be adversely > affected - i.e., compaction stops across the board. > This can be improved by just aborting compaction for a topic on any error and > keep the thread from exiting. > Another improvement would be to reject messages without keys that are sent to > compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-1755: --- Reviewer: Jay Kreps Improve error handling in log cleaner - Key: KAFKA-1755 URL: https://issues.apache.org/jira/browse/KAFKA-1755 Project: Kafka Issue Type: Bug Reporter: Joel Koshy Assignee: Joel Koshy Labels: newbie++ Fix For: 0.8.3 Attachments: KAFKA-1755.patch, KAFKA-1755_2015-02-23_14:29:54.patch, KAFKA-1755_2015-02-26_10:54:50.patch The log cleaner is a critical process when using compacted topics. However, if there is any error in any topic (notably if a key is missing) then the cleaner exits and all other compacted topics will also be adversely affected - i.e., compaction stops across the board. This can be improved by just aborting compaction for a topic on any error and keep the thread from exiting. Another improvement would be to reject messages without keys that are sent to compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1755: -- Attachment: KAFKA-1755_2015-02-26_10:54:50.patch Improve error handling in log cleaner - Key: KAFKA-1755 URL: https://issues.apache.org/jira/browse/KAFKA-1755 Project: Kafka Issue Type: Bug Reporter: Joel Koshy Assignee: Joel Koshy Labels: newbie++ Fix For: 0.8.3 Attachments: KAFKA-1755.patch, KAFKA-1755_2015-02-23_14:29:54.patch, KAFKA-1755_2015-02-26_10:54:50.patch The log cleaner is a critical process when using compacted topics. However, if there is any error in any topic (notably if a key is missing) then the cleaner exits and all other compacted topics will also be adversely affected - i.e., compaction stops across the board. This can be improved by just aborting compaction for a topic on any error and keep the thread from exiting. Another improvement would be to reject messages without keys that are sent to compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1755: -- Status: Patch Available (was: Open) Improve error handling in log cleaner - Key: KAFKA-1755 URL: https://issues.apache.org/jira/browse/KAFKA-1755 Project: Kafka Issue Type: Bug Reporter: Joel Koshy Assignee: Joel Koshy Labels: newbie++ Fix For: 0.8.3 Attachments: KAFKA-1755.patch The log cleaner is a critical process when using compacted topics. However, if there is any error in any topic (notably if a key is missing) then the cleaner exits and all other compacted topics will also be adversely affected - i.e., compaction stops across the board. This can be improved by just aborting compaction for a topic on any error and keep the thread from exiting. Another improvement would be to reject messages without keys that are sent to compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1755: -- Attachment: KAFKA-1755.patch Improve error handling in log cleaner - Key: KAFKA-1755 URL: https://issues.apache.org/jira/browse/KAFKA-1755 Project: Kafka Issue Type: Bug Reporter: Joel Koshy Assignee: Joel Koshy Labels: newbie++ Fix For: 0.8.3 Attachments: KAFKA-1755.patch The log cleaner is a critical process when using compacted topics. However, if there is any error in any topic (notably if a key is missing) then the cleaner exits and all other compacted topics will also be adversely affected - i.e., compaction stops across the board. This can be improved by just aborting compaction for a topic on any error and keep the thread from exiting. Another improvement would be to reject messages without keys that are sent to compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1755: -- Attachment: KAFKA-1755_2015-02-23_14:29:54.patch Improve error handling in log cleaner - Key: KAFKA-1755 URL: https://issues.apache.org/jira/browse/KAFKA-1755 Project: Kafka Issue Type: Bug Reporter: Joel Koshy Assignee: Joel Koshy Labels: newbie++ Fix For: 0.8.3 Attachments: KAFKA-1755.patch, KAFKA-1755_2015-02-23_14:29:54.patch The log cleaner is a critical process when using compacted topics. However, if there is any error in any topic (notably if a key is missing) then the cleaner exits and all other compacted topics will also be adversely affected - i.e., compaction stops across the board. This can be improved by just aborting compaction for a topic on any error and keep the thread from exiting. Another improvement would be to reject messages without keys that are sent to compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1755: -- Summary: Improve error handling in log cleaner (was: Log cleaner thread should not exit on errors) Improve error handling in log cleaner - Key: KAFKA-1755 URL: https://issues.apache.org/jira/browse/KAFKA-1755 Project: Kafka Issue Type: Bug Reporter: Joel Koshy Labels: newbie++ Fix For: 0.8.3 The log cleaner is a critical process when using compacted topics. However, if there is any error in any topic (notably if a key is missing) then the cleaner exits and all other compacted topics will also be adversely affected - i.e., compaction stops across the board. This can be improved by just aborting compaction for a topic on any error and keep the thread from exiting. Another improvement would be to reject messages without keys that are sent to compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-1755) Improve error handling in log cleaner
[ https://issues.apache.org/jira/browse/KAFKA-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Koshy updated KAFKA-1755: -- Assignee: Joel Koshy Improve error handling in log cleaner - Key: KAFKA-1755 URL: https://issues.apache.org/jira/browse/KAFKA-1755 Project: Kafka Issue Type: Bug Reporter: Joel Koshy Assignee: Joel Koshy Labels: newbie++ Fix For: 0.8.3 The log cleaner is a critical process when using compacted topics. However, if there is any error in any topic (notably if a key is missing) then the cleaner exits and all other compacted topics will also be adversely affected - i.e., compaction stops across the board. This can be improved by just aborting compaction for a topic on any error and keep the thread from exiting. Another improvement would be to reject messages without keys that are sent to compacted topics although this is not enough by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
