You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/06/06 02:29:18 UTC

[jira] [Updated] (KAFKA-5383) Additional Test Cases for ReplicaManager

     [ https://issues.apache.org/jira/browse/KAFKA-5383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson updated KAFKA-5383:
-----------------------------------
    Description: KAFKA-5355 and KAFKA-5376 have shown that current testing of ReplicaManager is inadequate. This is definitely the case when it comes to KIP-98 and is likely true in general. We should improve this.  (was: KAFKA-5355 and 5376 have shown that current testing of ReplicaManager is inadequate. This is definitely the case when it comes to KIP-98 and is likely true in general. We should improve this.)

> Additional Test Cases for ReplicaManager
> ----------------------------------------
>
>                 Key: KAFKA-5383
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5383
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, core, producer 
>            Reporter: Jason Gustafson
>             Fix For: 0.11.0.0
>
>
> KAFKA-5355 and KAFKA-5376 have shown that current testing of ReplicaManager is inadequate. This is definitely the case when it comes to KIP-98 and is likely true in general. We should improve this.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)