> IMO, we should allow the producer to connect the topic.
I actually think the current producer_request_hold feature works based
on disconnecting a producer and only letting it connect when the topic
no longer exceeds its quota.
> It looks like we do not support the `producer_request_hold`
GitHub user michaeljmarshall added a comment to the discussion: Issue - Failed
to enable ssl with JKS
Note that the `Failed to resolve network location` log only indicates that you
have not configured racks for your bookies. It is not preventing TLS from
working, and it is not attempting to
GitHub user michaeljmarshall added a comment to the discussion: Tips -
Workaround incorrect DNS resolutions on MacOS
@tisonkun - thanks for your comment about DNS resolution. I've also found that
an issue can come from how the `/etc/hosts` file is configured for your
machine's hostname. I
GitHub user tisonkun edited a comment on the discussion: Issue - Failed to
enable ssl with JKS
@eronrunner can you provide which version (os & pulsar) in used?
OK. It seems Pulsar version=2.9.2. If it's on MacOS, DNS resolution can meet
issue described in
GitHub user tisonkun added a comment to the discussion: Issue - Failed to
enable ssl with JKS
@eronrunner can you provide which version (os & pulsar) in used?
GitHub link:
https://github.com/apache/pulsar/discussions/17065#discussioncomment-3380701
This is an automatically sent email
GitHub user nodece added a comment to the discussion: Issue - Failed to enable
ssl with JKS
It looks related to DNS.
GitHub link:
https://github.com/apache/pulsar/discussions/17065#discussioncomment-3380663
This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe,
+1 on the customized one.
Cheers
momo-jun
> I suggest to include 'topic' in the flag, we have too many entities in
> Pulsar
Thanks, change it to `topicTwoPhaseDeletionEnabled`.
+1 on the customized one
Thanks,
Yunze
> 2022年8月12日 00:25，Alexander Preuss
> 写道：
>
> Hi together,
>
> Thank you for driving this topic!
> I agree that our customized convention is better than the Angular one.
>
> +1 on the customized one
>
> Best,
> Alex
>
>
>
> On Thu, Aug 11, 2022
GitHub user Anonymitaet added a comment to the discussion: Tips - Workaround
incorrect DNS resolutions on MacOS
How about adding a `troubleshooting` or `QA` chapter to
https://pulsar.apache.org/docs/next/getting-started-standalone at the end?
The [`Install JDK on M1`
Hi together,
Thank you for driving this topic!
I agree that our customized convention is better than the Angular one.
+1 on the customized one
Best,
Alex
On Thu, Aug 11, 2022 at 11:02 AM Yu wrote:
> Hi team,
>
> For PIP 198: Standardize PR Naming Convention using GitHub Actions [1], we've
+1 It would be awesome to utilize the GitHub Project to track issues.
BTW, seems this is a Classic Project[2], and the New Project[1] can provide
more features than the Classic Project[2].
[1] https://github.com/apache/pulsar/projects?type=new
[2]
Hi all,
Recently I'm working on the release of 2.8.4 and it's near the vote of
the 1st candidate but I have some questions.
From the tutorial [1] we can see, the 8th step is "Run the vote".
However, the 7th step is "Write release notes", should we execute this
step later? I see the 16th step is
danny-krueger opened a new issue, #285:
URL: https://github.com/apache/pulsar-helm-chart/issues/285
**Describe the bug**
The reissued certificates from the Cert Manager will not be used by Pulsar
until the pods are rebooted.
**To Reproduce**
Steps to reproduce the behavior:
Hi,
TL;DR:
If you find an issue tagged as Stale or lifecycle/stale or generally
inactive, be confident to close it as not planned. Close as not planned is
a GitHub Issue feature[1] and here is an example[2].
The longer version:
I started a discussion about the stale bot and stale issues/prs
GitHub user tisonkun added a comment to the discussion: Tips - Workaround
incorrect DNS resolutions on MacOS
BTW, this can be a troubleshooting doc for running Pulsar on MacOS.
For the document part, cc @Anonymitaet @momo-jun
Do we have a place to attach such notes?
For the technical part,
GitHub user tisonkun created a discussion: Tips - Workaround incorrect DNS
resolutions on MacOS
I'd like to share my experience of workaround incorrect DNS resolutions on
MacOS for Pulsar standalone.
When you run Pulsar standalone by `bin/pulsar standalone` on MacOS, you should
always see
GitHub user asafm added a comment to the discussion: Issue - Failed to enable
ssl with JKS
@hangc0276 ?
GitHub link:
https://github.com/apache/pulsar/discussions/17065#discussioncomment-3374082
This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send
Hi, Penghui
I support your opinion.
It looks like we do not support the `producer_request_hold` semantics. We just
easily use the same behaviour like `producer_exception`. Maybe it's a missing
feature.
Best,
Mattison
On 2022/08/11 05:28:25 PengHui Li wrote:
> Hi all,
>
> Pulsar has a
GitHub user eronrunner edited a discussion: Issue - Failed to enable ssl with
JKS
I install pulsar by helm chart and try to add the properties
brokerServicePortTls: "{{.Values.broker.ports.pulsarssl}}"
webServicePortTls: "{{.Values.broker.ports.https}}"
tlsEnabled: "true"
Hi team,
For PIP 198: Standardize PR Naming Convention using GitHub Actions [1], we've
got many different suggestions on implementation details. Let's discuss
them one by one.
Discussion topic:
For PR titles, which convention should we follow?
- Angular convention [2] - Our
GitHub user eronrunner edited a discussion: Issue - Failed to enable ssl with
JKS
I install pulsar by helm chart and try to add the properties
brokerServicePortTls: "{{.Values.broker.ports.pulsarssl}}"
webServicePortTls: "{{.Values.broker.ports.https}}"
tlsEnabled: "true"
GitHub user eronrunner created a discussion: Issue - Failed to enable ssl with
JKS
I install pulsar by helm chart and try to add the properties
brokerServicePortTls: "{{.Values.broker.ports.pulsarssl}}"
webServicePortTls: "{{.Values.broker.ports.https}}"
tlsEnabled: "true"
# TLS
Hi team, Thanks for all your suggestions! I'll move PIP 198 forward since
we get 3 binding votes (Penghui, Lari, Michael) [1].
[1] https://lists.apache.org/thread/m7hfgpdjthrk8ogz3mnkprs018tkkc0m
Yu
Il Sab 23 Lug 2022, 03:26 Yan Zhao ha scritto:
> Yes, wo define `twoPhaseDeletionEnabled` in the Service Configuration.
>
Thanks.
I suggest to include 'topic' in the flag, we have too many entities in
Pulsar
Enrico
>
A Schema instance is stateful (and contians mutable state) and in the end
it contains a reference to the PulsarClient instance that is using it.
Look at how AutoConsume schema works for instance.
I don't think it is possible to support such API in the general case.
If you want to use it as a key
26 matches
Mail list logo
