[jira] [Updated] (KAFKA-10304) Revisit and improve the tests of MirrorMaker 2
[ https://issues.apache.org/jira/browse/KAFKA-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ning Zhang updated KAFKA-10304: --- Description: In a different MM2 change, [some concerns|https://github.com/apache/kafka/pull/9029#issuecomment-663094946] on tests were raised. It may be a good time to revisit and refactor the tests, possibly in the following way: (1) are 100 messages good enough for integration tests? (2) what about the broker failure in the middle of integration tests? (3) other validations to check (e.g. topic config sync) was: In a different MM2 change https://github.com/apache/kafka/pull/9029, some concerns on tests were raised. It may be a good time to revisit and refactor the tests, possibly in the following way: (1) are 100 messages good enough for integration tests? (2) what about the broker failure in the middle of integration tests? (3) other validations to check (e.g. topic config sync) > Revisit and improve the tests of MirrorMaker 2 > -- > > Key: KAFKA-10304 > URL: https://issues.apache.org/jira/browse/KAFKA-10304 > Project: Kafka > Issue Type: Test > Components: KafkaConnect, mirrormaker >Reporter: Ning Zhang >Assignee: Ning Zhang >Priority: Minor > Fix For: 2.8.0 > > > In a different MM2 change, [some > concerns|https://github.com/apache/kafka/pull/9029#issuecomment-663094946] on > tests were raised. It may be a good time to revisit and refactor the tests, > possibly in the following way: > (1) are 100 messages good enough for integration tests? > (2) what about the broker failure in the middle of integration tests? > (3) other validations to check (e.g. topic config sync) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10304) Revisit and improve the tests of MirrorMaker 2
[ https://issues.apache.org/jira/browse/KAFKA-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ning Zhang updated KAFKA-10304: --- Description: In a different MM2 change https://github.com/apache/kafka/pull/9029, some concerns on tests were raised. It may be a good time to revisit and refactor the tests, possibly in the following way: (1) are 100 messages good enough for integration tests? (2) what about the broker failure in the middle of integration tests? (3) other validations to check (e.g. topic config sync) was: due to the quick development of Kafka MM 2, unit and integration tests of MirrorMaker 2 were made just for covering each individual feature and some of them are simply copy-n-paste from the existing tests with small tweaks. It may be a good time to revisit and improve the tests, possibly in the following way: (1) are 100 messages good enough for integration tests? (2) what about the failure in the middle of integration tests? (3) Do we want to check other messages (e.g. checkpoint, heartbeat, offset sync..) beyond the mirrored message in integration tests? > Revisit and improve the tests of MirrorMaker 2 > -- > > Key: KAFKA-10304 > URL: https://issues.apache.org/jira/browse/KAFKA-10304 > Project: Kafka > Issue Type: Test > Components: KafkaConnect, mirrormaker >Reporter: Ning Zhang >Assignee: Ning Zhang >Priority: Minor > Fix For: 2.8.0 > > > In a different MM2 change https://github.com/apache/kafka/pull/9029, some > concerns on tests were raised. It may be a good time to revisit and refactor > the tests, possibly in the following way: > (1) are 100 messages good enough for integration tests? > (2) what about the broker failure in the middle of integration tests? > (3) other validations to check (e.g. topic config sync) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10304) Revisit and improve the tests of MirrorMaker 2
[ https://issues.apache.org/jira/browse/KAFKA-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ning Zhang updated KAFKA-10304: --- Component/s: mirrormaker > Revisit and improve the tests of MirrorMaker 2 > -- > > Key: KAFKA-10304 > URL: https://issues.apache.org/jira/browse/KAFKA-10304 > Project: Kafka > Issue Type: Test > Components: KafkaConnect, mirrormaker >Reporter: Ning Zhang >Assignee: Ning Zhang >Priority: Minor > > due to the quick development of Kafka MM 2, unit and integration tests of > MirrorMaker 2 were made just for covering each individual feature and some of > them are simply copy-n-paste from the existing tests with small tweaks. It > may be a good time to revisit and improve the tests, possibly in the > following way: > (1) are 100 messages good enough for integration tests? > (2) what about the failure in the middle of integration tests? > (3) Do we want to check other messages (e.g. checkpoint, heartbeat, offset > sync..) beyond the mirrored message in integration tests? -- This message was sent by Atlassian Jira (v8.3.4#803005)
