urfreespace merged pull request #6:
URL: https://github.com/apache/pulsar-site/pull/6
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr
urfreespace merged pull request #7:
URL: https://github.com/apache/pulsar-site/pull/7
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr
Hi Jiuming,
Could you please check if the Prometheus client
can be used to reduce the JVM heap usage?
If yes, I think we can consider using the Prometheus
client instead of the current implementation together.
Otherwise, we'd better focus on the heap memory usage
enhancement for this discussion. U
Hi Penghui,
I had read `io.prometheus.client.exporter.HttpServer` source code, in
`HttpMetricsHandler#handle` method, it uses thread local cached
`ByteArrayOutputStream` , it’s similar with our current implemention(with heap
memory resizes and mem_copy).
It will spend a plenty of heap memory,
I'm recently releasing pulsar node client 1.6, I'm very sorry, just now I
deleted the pulsar-client package on npmjs by mistake, that doesn't seem to
be recoverable, if you install pulsar-client you may see this warning
`Package no longer supported`, I'm now releasing a small version for each
branc
Thanks for the heads up
Enrico
Il Lun 28 Feb 2022, 14:55 Guangning E ha scritto:
> I'm recently releasing pulsar node client 1.6, I'm very sorry, just now I
> deleted the pulsar-client package on npmjs by mistake, that doesn't seem to
> be recoverable, if you install pulsar-client you may see
Hi everyone,
Please review and vote on the release candidate #2 for the version 1.6.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
This is the first release candidate for Apache Pulsar Node.js client,
version 1.6.0.
It fixes the fo
lhotari opened a new pull request #239:
URL: https://github.com/apache/pulsar-helm-chart/pull/239
This reverts commit 40a4d50923bd93c960a4ef940930177ca80cb77e.
Supporting `cert-manager.io/v1` api version requires changes made in #233 or
#238. In addition, the change should be made in
lhotari commented on pull request #238:
URL:
https://github.com/apache/pulsar-helm-chart/pull/238#issuecomment-1054352998
@toneill818 Thank you for the contribution. It looks like there's a similar
change in #233. I created #239 to first rollback #204 changes so that we have a
time to pre
lhotari commented on pull request #233:
URL:
https://github.com/apache/pulsar-helm-chart/pull/233#issuecomment-1054368281
@smazurov Thanks for the contribution. I created a PR to first revert #204
changes so that we have time to prepare a better solution for migrating to use
`cert-manager
lhotari edited a comment on pull request #233:
URL:
https://github.com/apache/pulsar-helm-chart/pull/233#issuecomment-1054368281
@smazurov Thanks for the contribution. I created a PR to first revert #204
changes so that we have time to prepare a better solution for migrating to use
`cert-
Rohlik commented on pull request #227:
URL:
https://github.com/apache/pulsar-helm-chart/pull/227#issuecomment-1054403222
I just hit on this problem too. Looking forward to see this PR merged 🙏🏽 .
--
This is an automated message from the Apache Git Service.
To respond to the message, plea
toneill818 closed pull request #238:
URL: https://github.com/apache/pulsar-helm-chart/pull/238
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev
toneill818 commented on pull request #238:
URL:
https://github.com/apache/pulsar-helm-chart/pull/238#issuecomment-1054526089
@lhotari That works for me
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
toneill818 commented on pull request #239:
URL:
https://github.com/apache/pulsar-helm-chart/pull/239#issuecomment-1054553884
@lhotari Would you be interested in having cert-manager installed as a
dependency if enabled, or kept outside this chart? If we require it as a
dependency we can us
smazurov commented on pull request #233:
URL:
https://github.com/apache/pulsar-helm-chart/pull/233#issuecomment-1054586894
assuming kube is aware of both apis, upgrading is straightfoward. So the
change is fine as long as the new spec for v1 is actually followed. Once
cert-manager is upgr
michaeljmarshall commented on pull request #227:
URL:
https://github.com/apache/pulsar-helm-chart/pull/227#issuecomment-1054648279
@mkoertgen - thanks for your contribution. Do we still need this PR? Based
on the discussion in
https://github.com/prometheus-operator/prometheus-operator/iss
massakam opened a new pull request #197:
URL: https://github.com/apache/pulsar-client-node/pull/197
There is a step in [the release
process](https://github.com/apache/pulsar-client-node/wiki/Release-process) to
run `npm run license: addheader`, which will add the license header to the
sou
Hi,
Thanks for the update,
I agree to have the JVM heap usage enhancement.
+1
Penghui
On Mon, Feb 28, 2022 at 5:33 PM Jiuming Tao
wrote:
> Hi Penghui,
>
> I had read `io.prometheus.client.exporter.HttpServer` source code, in
> `HttpMetricsHandler#handle` method, it uses thread local cached
>
> Either replicated topic or non-replicated topic, we should provide the
> same topic deletion behavior, the topic can be deleted if no active
> user's producers/consumers, should not be affected by the Pulsar
> internal producers/consumers.
I agree with you that it'd be nice to provide the same d
Hi, Guangning
I undeprecated v1.5.0 and some versions by referring to following document.
https://docs.npmjs.com/deprecating-and-undeprecating-packages-or-package-versions#undeprecating-a-package-or-version
At the same time, I deprecated all versions uploaded recently.
Could you let me know what
> I agree with you that it'd be nice to provide the same deletion
behavior. However, because geo-replication's configuration is
decentralized, I think namespace or topic deletion is more complicated
than unreplicated deletion. Note that users cannot currently delete
namespaces that are configured w
22 matches
Mail list logo
