2018-11-25 10:23:12 UTC - Harald Gustafsson: @Matteo Merli I managed to make a
small example for the seg fault of the python consumer that I run using gdb
----
2018-11-25 10:23:51 UTC - Harald Gustafsson:
----
2018-11-25 10:25:14 UTC - Harald Gustafsson:
----
2018-11-25 10:25:50 UTC - Harald Gustafsson: this is run in a container based
on the python:3 image on docker hub
----
2018-11-25 10:28:36 UTC - Harald Gustafsson:
----
2018-11-25 10:29:02 UTC - bossbaby: i don't understand that why broker not
recopy data when move new broker
----
2018-11-25 10:30:55 UTC - Harald Gustafsson: My code runs when running on the
mac directly.
----
2018-11-25 10:37:02 UTC - Harald Gustafsson:
----
2018-11-25 13:15:33 UTC - Vincent Ngan: @Vincent Ngan has joined the channel
----
2018-11-25 13:56:20 UTC - Samuel Sun: Hi guys, anyone knows how to get the
allocator-name for this command options " allocator-stats dump allocator
stats
Usage: allocator-stats [options] allocator-name", thanks
----
2018-11-25 15:33:30 UTC - Matteo Merli: @Samuel Sun `default` is the allocator
used for all buffers used when reading/writing from sockets. `ml-cache` is used
to get memory for caching messages
----
2018-11-25 15:35:21 UTC - Matteo Merli: @Harald Gustafsson Thanks for the repro
steps. Let me take a look
----
2018-11-25 22:37:44 UTC - Sijie Guo: because the message data is not stored on
brokers, it is stored in a distributed storage (bookkeeper). so when a broker
fails, it only transfers the ownership instead of copying the data.
this blog provides a good idea about why.
----
2018-11-25 22:38:47 UTC - Sijie Guo: it should be per message basis. do you
have any code example to reproduce it? it might be worth filing a github issue
with instructions to reproduce, so we can take a closer look to see if it is a
bug.
----
2018-11-26 02:38:09 UTC - yjchu: @yjchu has joined the channel
----
2018-11-26 07:58:07 UTC - Olivier Chicha: @Olivier Chicha has joined the channel
----
2018-11-26 08:54:44 UTC - Olivier Chicha: Hi all, I am discovering Pulsar and I
have a question about java client consumers.
I want to consume within a single thread messages coming from multiple topics
(basically merging the events of the topics)
The list of topic is not predefined in advance (I need to be able to subscribe
/ unsubscribe from topics during the live time of my application)
The list of topic does not match a given pattern
I was expecting to be able to subscribe / unsubscribe a topic directly from the
consumer API but it is not possible
=> right now I create a single 'MessageListener' and a consumer per topic,
each consumer is configured with the unique MessageListener
it works fine but I wonder if it is as performant as creating a single Consumer
with multiple topics, especially as I may have hundreds of tousands of topics
to listen to
Reading the implementation I saw that the MultiTopicsConsumerImpl has a public
method called subscribeAsync(String topicName) that is used by the
PatternMultiTopicsConsumerImpl
unfortunately this method is not available through the public API
Off course I can still use directly the implementation class
my question is :
- is there something in the api that would allow me to avoid creating hundreds
of thousands of consumers ?
- else would using directly the implementation of MultiTopicsConsumerImpl be
the best way to achieve my objective?
regards
----
