GitHub user jesumyip added a comment to the discussion: struggling with pulsar
functions in kubernetes
I'm getting an error in the pod that runs the function. The error is
Failed reason: General OpenSslEngine problem
I then modified the pod so that instead of running all the shell commands t
GitHub user jesumyip edited a comment on the discussion: struggling with pulsar
functions in kubernetes
I'm getting an error in the pod that runs the function. The error is
Failed reason: General OpenSslEngine problem
I then modified the pod so that instead of running all the shell commands
GitHub user jesumyip edited a comment on the discussion: struggling with pulsar
functions in kubernetes
I'm getting an error in the pod that runs the function. The error is
`General OpenSslEngine problem`
I then modified the pod so that instead of running all the shell commands that
is by d
GitHub user eolivelli added a comment to the discussion: [Pulsar JVM Dashboard]
Zookeeper show No Data on column direct memory ?
which version of Pulsar ?
which dashboards are you using ?
GitHub link:
https://github.com/apache/pulsar/discussions/18382#discussioncomment-4084262
This is
GitHub user TheDungNTU added a comment to the discussion: [Pulsar JVM
Dashboard] Zookeeper show No Data on column direct memory ?
Pulsar version 2.9.2
Dashboard grafana
GitHub link:
https://github.com/apache/pulsar/discussions/18382#discussioncomment-4084571
This is an automatically se
Hi all,
Currently we have the following 5 implementations of MessageId:
- MessageIdImpl: (ledger id, entry id, partition index)
- BatchMessageIdImpl: adds (batch index, batch size, acker), where
acker is a wrapper of a BitSet.
- ChunkMessageIdImpl: adds another MessageIdImpl that represen
Il giorno mar 8 nov 2022 alle ore 11:25 Yunze Xu
ha scritto:
>
> Hi all,
>
> Currently we have the following 5 implementations of MessageId:
>
> - MessageIdImpl: (ledger id, entry id, partition index)
> - BatchMessageIdImpl: adds (batch index, batch size, acker), where
> acker is a wrapper o
Hi Enrico,
> We also need a way to represent this as a String or a byte[]
We already have the `toByteArray` method, right?
Thanks,
Yunze
On Tue, Nov 8, 2022 at 6:43 PM Enrico Olivelli wrote:
>
> Il giorno mar 8 nov 2022 alle ore 11:25 Yunze Xu
> ha scritto:
> >
> > Hi all,
> >
> > Currently w
Il giorno mar 8 nov 2022 alle ore 11:52 Yunze Xu
ha scritto:
>
> Hi Enrico,
>
> > We also need a way to represent this as a String or a byte[]
>
> We already have the `toByteArray` method, right?
Yes, correct. So we are fine. I forgot about it and I answered too quickly.
I am not sure if this ca
I didn't look into these two methods at the moment. But I think it's possible to
retain only the `fromByteArray`.
Thanks,
Yunze
On Tue, Nov 8, 2022 at 7:02 PM Enrico Olivelli wrote:
>
> Il giorno mar 8 nov 2022 alle ore 11:52 Yunze Xu
> ha scritto:
> >
> > Hi Enrico,
> >
> > > We also need a wa
Ok.
I would list what you wrote in your original PIP for context.
What is your future improvement you plan?
On Thu, Nov 3, 2022 at 11:46 AM 丛搏 wrote:
> Good question!
> It is a scene for our subsequent optimization, and we are implementing
> it with minimal changes.
>
> Asaf Mesika 于2022年11月3
Thanks, Enrico (sorry for replying late - I'm hugely backlogged on this
mailing list).
I wanted to contribute what you wrote in the Contributors guide, but I
couldn't find any reference to the process of PIP. Do you know where it is
documented in the Pulsar website?
On Thu, Sep 1, 2022 at 5:0
Hi Asaf,
Currently, the dev docs about PIP are located at:
https://github.com/apache/pulsar/tree/master/wiki/proposals
I'm writing the contribute guide at: https://pulsar.apache.org/contributing
... but the PIP process update should go through more discussion so I don't
cover it yet.
Best,
tison
Hi Jiuming,
I have a few questions:
Motivation
>
> Currently, there's no way to track CommandPartitionedTopicMetadata
> requests. There's no metrics that indicate that a broker is handling
> CommandPartitionedTopicMetadata requests.
>
> Misconfigured clients might flood brokers with
> CommandPart
>Maybe this design is to hidden some details, but if
users don't know the details like ledger id and entry id, how could
you know what does "0:0:-1:0" mean?
Abstractions exist for a reason. Ledgerid and entryid are implementation
details, and an application should not be interpreting that at all
Dear Pulsar Community,
Please review and vote on this PIP.
PIP link: https://github.com/apache/pulsar/issues/18099
Thank you,
-Heesung
Hi Joe,
Then what would we expect users to do with the MessageId? It should only
be passed to Consumer#seek or ReaderBuilder#startMessageId?
What about the partition index? We have a `TopicMetadata` interface that returns
the number of partitions. If the partition is also "implementation
details"
Overall, this makes sense to me.
The current status of MessageId is a bit messy, especially for client
developers and senior users who are interested in the implementation
details.
But please make sure we have to make it compatible with previous
implementations, like the `toString` method, I bet so
In the future, I will add a config for `BatchReceivePolicy.class`, I
haven't thought of a name yet. The config will control the
`MultiTopicsConsumerImpl.class` whether use
`ConsumerImpl.class`.batchReceive() directly or use
`ConsumerBase.class` `incomingMessages`.
Asaf Mesika 于2022年11月8日周二 21:30写
19 matches
Mail list logo
