Technoboy- commented on code in PR #14795:
URL: https://github.com/apache/pulsar/pull/14795#discussion_r894110247
##########
site2/docs/concepts-messaging.md:
##########
@@ -857,6 +857,38 @@ Producer<byte[]> producer = client.newProducer()
```
+## System topic
+
+System topic is a predefined topic for internal use within Pulsar. It can be
either persistent or non-persistent topic.
+
+System topics serve to implement certain features and eliminate dependencies
on third-party components, such as transactions, heartbeat detections,
topic-level policies, and resource group services. System topics empower the
implementation of these features to be simplified, dependent, and flexible.
Take heartbeat detections for example, you can leverage the system topic for
healthcheck to internally enable producer/reader to procude/consume messages
under the heartbeat namespace, which can detect whether the current service is
still alive.
+
+There are diverse system topics depending on namespaces. The following table
outlines the available system topics for each specific namespace.
+
+| Namespace | TopicName | Domain | Count | Usage |
+|-----------|-----------|--------|-------|-------|
+| pulsar/system | `transaction_coordinator_assign_${id}` | Persistent |
Default 16 | Transaction coordinator |
+| pulsar/system | `_transaction_log${tc_id}` | Persistent | Default 16 |
Transaction log |
Review Comment:
yes, right.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
