merlimat commented on issue #2025: Allow non-pesistent topics to be retrieved along with persistent ones from the "GetTopicsOfNamespace" method URL: https://github.com/apache/incubator-pulsar/pull/2025#issuecomment-400041637 > Unfortunately I don't really know if non-persistent themselves work in multi-broker setups. I have recently asked on Slack if non-persistent topics are being replicated in any way and @merlimat's response was that they don't. Also it seems to be that some other methods that are working with non-persistent topics are using this very same collection. * A single topic (or partition of a topic) is assigned to a single broker, at a given point in time. * Topics belonging to a namespace can be assigned to different brokers (that is true for both persistent and non-persistent topics) * Persistent topics use BookKeeper to persist data and maintain state --> When a broker crashes, the topic can move immediately to a different broker and restart with the same exact state. * Non-persistent topics do not store any kind of state durably. The messages are kept for a very short amount of time in memory in the broker and dropped if they cannot be delivered immediately. The data for a single non-persistent topic is not stored in multiple machines. If the broker crashes, some messages will be lost and the topic will continue on the new broker.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
