You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (Created) (JIRA)" <ji...@apache.org> on 2012/02/17 00:12:59 UTC
[jira] [Created] (KAFKA-274) Handle corrupted messages cleanly
Handle corrupted messages cleanly
---------------------------------
Key: KAFKA-274
URL: https://issues.apache.org/jira/browse/KAFKA-274
Project: Kafka
Issue Type: Improvement
Components: core
Affects Versions: 0.7
Reporter: Neha Narkhede
Assignee: Neha Narkhede
Fix For: 0.7.1
Attachments: KAFKA-274.patch
This is related to KAFKA-273 and is filed to improve the code to have more defensive checks against corrupted data. The data could get corrupted either due to a Kafka bug or due to bit flipping on the network. The message iterator should check if the message is valid before trying to decompress it. On the producer side, defensive checks can be turned on to verify the messages before writing those to the socket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (KAFKA-274) Handle corrupted messages cleanly
Posted by "Neha Narkhede (Work started) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on KAFKA-274 started by Neha Narkhede.
> Handle corrupted messages cleanly
> ---------------------------------
>
> Key: KAFKA-274
> URL: https://issues.apache.org/jira/browse/KAFKA-274
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.7
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Fix For: 0.7.1
>
> Attachments: KAFKA-274.patch
>
>
> This is related to KAFKA-273 and is filed to improve the code to have more defensive checks against corrupted data. The data could get corrupted either due to a Kafka bug or due to bit flipping on the network. The message iterator should check if the message is valid before trying to decompress it. On the producer side, defensive checks can be turned on to verify the messages before writing those to the socket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-274) Handle corrupted messages cleanly
Posted by "Neha Narkhede (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-274:
--------------------------------
Attachment: KAFKA-274_v2.patch
Guarded against message set sizes > Int.MaxValue
> Handle corrupted messages cleanly
> ---------------------------------
>
> Key: KAFKA-274
> URL: https://issues.apache.org/jira/browse/KAFKA-274
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.7
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Fix For: 0.7.1
>
> Attachments: KAFKA-274.patch, KAFKA-274_v2.patch
>
>
> This is related to KAFKA-273 and is filed to improve the code to have more defensive checks against corrupted data. The data could get corrupted either due to a Kafka bug or due to bit flipping on the network. The message iterator should check if the message is valid before trying to decompress it. On the producer side, defensive checks can be turned on to verify the messages before writing those to the socket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-274) Handle corrupted messages cleanly
Posted by "Jun Rao (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209993#comment-13209993 ]
Jun Rao commented on KAFKA-274:
-------------------------------
+1 for the patch.
> Handle corrupted messages cleanly
> ---------------------------------
>
> Key: KAFKA-274
> URL: https://issues.apache.org/jira/browse/KAFKA-274
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.7
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Fix For: 0.7.1
>
> Attachments: KAFKA-274.patch, KAFKA-274_v2.patch
>
>
> This is related to KAFKA-273 and is filed to improve the code to have more defensive checks against corrupted data. The data could get corrupted either due to a Kafka bug or due to bit flipping on the network. The message iterator should check if the message is valid before trying to decompress it. On the producer side, defensive checks can be turned on to verify the messages before writing those to the socket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-274) Handle corrupted messages cleanly
Posted by "Neha Narkhede (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-274:
--------------------------------
Attachment: KAFKA-274.patch
> Handle corrupted messages cleanly
> ---------------------------------
>
> Key: KAFKA-274
> URL: https://issues.apache.org/jira/browse/KAFKA-274
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.7
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Fix For: 0.7.1
>
> Attachments: KAFKA-274.patch
>
>
> This is related to KAFKA-273 and is filed to improve the code to have more defensive checks against corrupted data. The data could get corrupted either due to a Kafka bug or due to bit flipping on the network. The message iterator should check if the message is valid before trying to decompress it. On the producer side, defensive checks can be turned on to verify the messages before writing those to the socket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-274) Handle corrupted messages cleanly
Posted by "Neha Narkhede (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede updated KAFKA-274:
--------------------------------
Status: Patch Available (was: In Progress)
> Handle corrupted messages cleanly
> ---------------------------------
>
> Key: KAFKA-274
> URL: https://issues.apache.org/jira/browse/KAFKA-274
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.7
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Fix For: 0.7.1
>
> Attachments: KAFKA-274.patch, KAFKA-274_v2.patch
>
>
> This is related to KAFKA-273 and is filed to improve the code to have more defensive checks against corrupted data. The data could get corrupted either due to a Kafka bug or due to bit flipping on the network. The message iterator should check if the message is valid before trying to decompress it. On the producer side, defensive checks can be turned on to verify the messages before writing those to the socket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira