2020-03-29 16:26:17 UTC - Sijie Guo: Can you see where are the high cpu usage from? I. E which component? Also how many CPU and memory are you allocating to Mac Docker? And how many CPU and memory do you allocate to each component? ---- 2020-03-29 17:32:54 UTC - Vince Pergolizzi: ---- 2020-03-29 18:43:44 UTC - Vince Pergolizzi: This is what I see when I run `top` inside the container ---- 2020-03-29 18:44:22 UTC - Vince Pergolizzi: This is the docker-compose Im using: <https://github.com/apache/pulsar-dotpulsar/blob/master/tests/docker-compose-standalone-tests.yml> ---- 2020-03-29 19:16:34 UTC - Fernando: how to set the message “Key” in python?? ---- 2020-03-29 23:45:30 UTC - Matteo Minardi: @Matteo Minardi has joined the channel ---- 2020-03-30 00:26:11 UTC - Hiroyuki Yamada: Hi, I feel it is possibly a bug of Key_Shared if I don’t do something completely wrong. Can anyone take a look ? <http://mail-archives.apache.org/mod_mbox/pulsar-users/202003.mbox/%3CCAPDOW74LN3WtdhpG_cgCCSg9MuMmkNV6giCGD5p%3DW1wWji0W7w%40mail.gmail.com%3E> ---- 2020-03-30 00:36:39 UTC - Penghui Li: Hi, the key_shared subscription split key hash range automatically when new consumer connected. So, at this time, messages with same key may dispatch to multiple consumers. You can try to use sticky consumer with fixed key hash ranges. ---- 2020-03-30 00:43:28 UTC - Hiroyuki Yamada: @Penghui Li Thanks. So it is an expected behavior ? ---- 2020-03-30 00:45:20 UTC - Penghui Li: Currently yes, I think we can try to improve it in the future. ---- 2020-03-30 00:45:54 UTC - Hiroyuki Yamada: OK, thanks. ---- 2020-03-30 00:46:24 UTC - Penghui Li: You are welcome. ---- 2020-03-30 00:47:34 UTC - Hiroyuki Yamada: I think it would be great if it is improved since the number of consumers can be easily changed in failure cases. ---- 2020-03-30 00:51:32 UTC - Penghui Li: Yes, maybe we can stop dispatch new messages to the old consumer for a key hash range when a new consumer trigger the key hash range split. And resume it when all dispatched messages are acked. +1 : Hiroyuki Yamada man-bowing : Hiroyuki Yamada ---- 2020-03-30 03:06:54 UTC - Penghui Li: @Hiroyuki Yamada There is a Github issue <https://github.com/apache/pulsar/issues/6554> tracking this feature. ---- 2020-03-30 03:09:49 UTC - Hiroyuki Yamada: Oh, great. Thank you ! ---- 2020-03-30 06:25:59 UTC - Rattanjot Singh: can you connect me with them ---- 2020-03-30 08:50:02 UTC - Alex Sim: @Alex Sim has joined the channel ---- 2020-03-30 09:04:07 UTC - Alex Sim: Hiya, so sorry to ask so soon after joining, but I'm having trouble with enabling the peek message function. I've set pulsar.peek.message to true and restarted my server, backend, and front end, but the manager still tells me to enable it in application.properties. Perhaps I'm restarting my services wrongly? We currently don't have TLS so I did not add the path of the certification. ---- 2020-03-30 09:05:02 UTC - Alex Sim: It'd be great if someone could point me into the right direction.. :disappointed_relieved: ----
