You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2021/02/27 00:51:00 UTC
[jira] [Created] (KAFKA-12381) Incompatible change in
verifiable_producer.log in 2.8
Colin McCabe created KAFKA-12381:
------------------------------------
Summary: Incompatible change in verifiable_producer.log in 2.8
Key: KAFKA-12381
URL: https://issues.apache.org/jira/browse/KAFKA-12381
Project: Kafka
Issue Type: Bug
Reporter: Colin McCabe
In test_verifiable_producer.py , we used to see this error message in verifiable_producer.log when a topic couldn't be created:
WARN [Producer clientId=producer-1] Error while fetching metadata with correlation id 1 : {test_topic=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.NetworkClient)
The test does a grep LEADER_NOT_AVAILABLE on the log in this case, and it used to pass.
Now we are instead seeing this in the log file:
WARN [Producer clientId=producer-1] Error while fetching metadata with correlation id 1 : {test_topic=INVALID_REPLICATION_FACTOR} (org.apache.kafka.clients.NetworkClient)
And of course now the test fails.
The INVALID_REPLICATION_FACTOR is coming from the new auto topic creation manager.
It is a simple matter to make the test pass -- I have confirmed that it passes if we grep for INVALID_REPLICATION_FACTOR in the log file instead of LEADER_NOT_AVAILABLE.
I think we just need to decide if this change in behavior is acceptable or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)