@RunLLM Can transactions be used without the transaction coordinator initialized?

No, transactions cannot be used without the transaction coordinator being initialized. The transaction coordinator must be enabled and its metadata initialized before any transactional operations can be performed; otherwise, attempts to use transactions will result in errors such as "The broker doesn't enable the transaction coordinator, or the transaction coordinator has not initialized" or "Transaction coordinator with id X not found" according to Pulsar Transactions API and Pulsar Transactions Usage Guide. Would you like more detail on how to enable and initialize the transaction coordinator? Sources: - Pulsar Transactions API - Pulsar Transactions Usage Guide 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@RunLLM Can transactions be used without the transaction coordinator metadata initialized?

No, transactions cannot be used without initializing the transaction coordinator metadata. If the metadata is not initialized, you will encounter errors such as "Transaction coordinator with id X not found" and transactional features will not function, as described in the Pulsar Transactions API and Pulsar Transactions Usage Guide. Would you like more detail on how to initialize the transaction coordinator metadata? Sources: - Pulsar Transactions API - Pulsar Transactions Usage Guide 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@RunLLM How can I check if the transaction coordinator metadata is initialized?

You can check if the transaction coordinator metadata is initialized by verifying the existence of the

transaction_coordinator_assign

partitioned topic in the

pulsar/system

namespace. If this topic exists with the expected number of partitions, the metadata is initialized. You can also use the Pulsar Admin API to list transaction coordinators or get their stats; if you receive "Transaction coordinator not found" errors, the metadata is not initialized (Pulsar Transactions Usage Guide, Pulsar Admin API Transactions). Would you like more detail on the specific admin commands to use? Sources: - Pulsar Transactions Usage Guide - Pulsar Admin API Transactions 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@RunLLM What are the values available for the broker configuration field

transactionMetadataStoreProviderClassName

?

It seems likely that the default value for

transactionMetadataStoreProviderClassName

is

org.apache.pulsar.transaction.coordinator.impl.MLTransactionMetadataStoreProvider

, which uses the managed ledger implementation. The data sources do not explicitly list other available values or implementations for this field (ServiceConfiguration.java). Would you like more detail on how to implement or use a custom provider? Sources: - ServiceConfiguration.java 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@RunLLM What should I consider when setting the number of transaction coordinators when initializing the transaction coordinator metadata

When setting the number of transaction coordinators, consider your expected transactional throughput and cluster size. More coordinators can improve performance and load balancing, but increasing the number after initialization is only supported for scale-up, not scale-down (Pulsar Transactions Usage Guide, Admin API Transactions). Would you like more detail on how to choose an optimal number or how to scale coordinators later? Sources: - Pulsar Transactions Usage Guide - Admin API Transactions 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.