2020-08-19 12:53:32 UTC - Ming: @Jay Sun It seems like you do need a file. The client library reads a cert file currently. I think it is a common practice to provision certificate as a separate step that makes sense to reading a cert file <https://github.com/apache/pulsar-client-go/blob/5d57012b94851a6f32618ac2260c356c355c1a34/pulsar/internal/connection.go#L774> ---- 2020-08-19 15:10:58 UTC - Addison Higham: there really isn't a hard limit on numbers of topics, but it does cause more and more tuning challenges and more resources to reach those levels and beyond.
If only a small subset of those topics will actually exist at once that should be quite a bit easier to do. Also, whenever discussing lots and lots of topics I do like to bring up partitioned topics and key_shared, which can be an alternative in some use cases ---- 2020-08-19 15:13:40 UTC - Addison Higham: in shared (and perhaps key shared... not sure of nack behavior there), that is the case, but in exclusive/failover, nacks still preserve order ---- 2020-08-19 15:14:40 UTC - Addison Higham: you can try a `pulsar-admin namespace unload <namespace>` to see if that fixes the issue. ---- 2020-08-19 15:41:26 UTC - Sijie Guo: You can set message key. Then the messages would be routed to a given partition. The “order” that Pulsar guarantees is the order of messages produced (appended) to a topic partition. ---- 2020-08-19 17:29:22 UTC - Maksym Domarev: Thats true, I but I need also an order, so fo me exclusive is rather an alternative. If I don’t use a topic for a while, will it delete it ? or retention works only on a message level ? ---- 2020-08-19 18:44:41 UTC - Nazia Firdous: @Nazia Firdous has joined the channel ---- 2020-08-19 18:45:38 UTC - Addison Higham: there is configuration to have pulsar clean up "inactive" topics. It is somewhat configurable, you can delete topics that don't have any subscriptions or any connected producers/consumer after X amount of time. You can also have subscriptions be deleted that are inactive ---- 2020-08-19 18:45:42 UTC - Addison Higham: so yes, that is all possible :slightly_smiling_face: ---- 2020-08-19 19:13:02 UTC - Nazia Firdous: Hi Can anyone let me know how to produce and consume a message on different host(like if it is two host h218 and h219)..h218 producing the messages and h219 consuming the messages... ---- 2020-08-19 20:43:35 UTC - Sumit Mudliar: @Sumit Mudliar has joined the channel ---- 2020-08-19 21:10:28 UTC - Muljadi: Hi.. where can I find more on how pulsar producer generates the AES Data Key for encryption? I’d like to get more in-depth flow of how it works in the code. Thanks! ---- 2020-08-19 21:23:25 UTC - Derek Moore: Current version download links are dead for me here: <http://pulsar.apache.org/en/download/> The few mirrors I've checked only have the 2.6.0 release. ---- 2020-08-19 21:34:56 UTC - Addison Higham: we are right in the middle of the 2.6.1 release, so the website has been update but the release is still being uploaded, apologies! ---- 2020-08-19 21:35:27 UTC - Derek Moore: no worries, just wanted to give a heads up :slightly_smiling_face: I grabbed 2.6.0 for now ---- 2020-08-19 21:36:00 UTC - Addison Higham: np, yeah, we should tweak the release process to upload first and then update website to avoid this ---- 2020-08-20 00:33:20 UTC - Muljadi: walking through code, `org.apache.pulsar.client.impl.crypto.MessageCryptoBc` maintain the data key. When a `MessageCrypto.decrypt` called, it checked whether the `dataKey` has been created. If it has not, it then lookup at the `MessageMetaData.getEncryptionKeyList` and attempt to decrypt the `dataKey` with the given `KeyReader` and return the first successful one. ---- 2020-08-20 07:13:27 UTC - Arthur: Thanks. When load balancing? So it's something normal? ---- 2020-08-20 07:34:07 UTC - Raghav: Is there a way to limit the produce/consumer throughput of a producer/consumer at topic level instead of changing broker settings at global level? I didn’t get documentation regarding this using pulsar-admin cli for topics. ----
