new note added after creating a topic to alert users if the broker is…

… down (#423) * new note added after creating a topic to alert users if the broker is down * new note with additional suggestion * new note with oOhn suggestion * Update README.adoc Remove stray hyphen Co-authored-by: John Byrne <[email protected]>
redhat-developer · Apr 1, 2022 · 1b61b32 · 1b61b32
1 parent c5f76b7
commit 1b61b32
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/docs/kafka/getting-started-kafka/README.adoc b/docs/kafka/getting-started-kafka/README.adoc
@@ -287,6 +287,9 @@ image::sak-create-topic.png[Image of wizard to create a topic]
 * *Replicas*: For this release of {product-kafka}, the replicas are preconfigured. The number of partition replicas for the topic is set to `3` and the minimum number of follower replicas that must be in sync with a partition leader is set to `2`. Replicas are copies of partitions in a topic. Partition replicas are distributed over multiple brokers in the cluster to ensure topic availability if a broker fails. When a follower replica is in sync with a partition leader, the follower replica can become the new partition leader if needed.
 
 After you complete the topic setup, the new Kafka topic is listed in the topics table. You can now start producing and consuming messages to and from this topic using services that you connect to this instance.
+
+NOTE: If your topic creation is unsuccessful and you receive an error message, try to create your topic again later. This situation might occur, for example, if your selected cloud provider has a temporary availability problem that affects your Kafka instance.
+
 --
 . In the topics table, on the right side of the Kafka topic, use the options icon (three vertical dots) to edit or delete the topic as needed.
 +