You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2015/09/02 17:06:46 UTC
[jira] [Updated] (KAFKA-2274) Add integration test for consumer
coordinator
[ https://issues.apache.org/jira/browse/KAFKA-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao updated KAFKA-2274:
---------------------------
Priority: Blocker (was: Critical)
> Add integration test for consumer coordinator
> ---------------------------------------------
>
> Key: KAFKA-2274
> URL: https://issues.apache.org/jira/browse/KAFKA-2274
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Reporter: Guozhang Wang
> Assignee: Jason Gustafson
> Priority: Blocker
> Fix For: 0.8.3
>
>
> As discussed with Onur offline, here are some things we could test / simulate:
> - consumer kill -9 (tested in ConsumerTest)
> - broker kill -9 (tested in ConsumerTest)
> - consumer very long GC
> - broker very long GC
> - consumer network cable unplugged
> - broker network cable unplugged
> - consumer power cord unplugged
> - broker power cord unplugged
> Quoting Onur: " Another motivating factor is to verify if response.wasDisconnected is good enough or if we actually need consumers to detect coordinator failures with timeouts.
> GC’s can be simulated with SIGSTOP and SIGCONT. I think we might be able to simulate network cable being unplugged with "ifconfig eth0 down”, but I’m not sure."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)