@RunLLM namesapce unload

To unload a namespace in StreamNative or Apache Pulsar, use the CLI command:

pulsarctl namespaces unload <tenant>/<namespace>

This operation removes all producers, consumers, and connections for the namespace from the current broker, causing topics to be reassigned to other brokers. You can also unload specific bundles within a namespace. For more details, see StreamNative CLI unload documentation and Apache Pulsar unload documentation. Would you like more detail on bundle unloading or the effects of this operation? Sources: - StreamNative CLI unload documentation - Apache Pulsar unload documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@RunLLM namespaces unload is giving 504 gateway timeout error

A 504 Gateway Timeout error during namespace unload typically indicates that the unload operation is taking too long to complete, often due to broker overload, slow topic cleanup, or issues with the extensible load manager. This is a known issue in Pulsar, especially when unloading large namespaces or many bundles, and can be exacerbated by network or broker performance problems. Recent fixes have targeted long unload times and stuck unloads with the extensible load manager, but timeouts can still occur if the operation exceeds the configured timeout window or if the broker is under heavy load (GitHub Issue 22136, StreamNative Release Notes). To mitigate, ensure you are running a supported Pulsar version with recent fixes, avoid unloading too many bundles at once, and consider increasing the unload timeout if necessary. If the problem persists, check broker logs for errors related to namespace unloading and review cluster health and resource usage. Would you like more detail on troubleshooting steps or configuration options? Sources: - GitHub Issue 22136 - StreamNative Release Notes 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.