[GitHub] [pulsar] momo-jun added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

GitHub user momo-jun added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 Sorry for my late reply. As discussed with @RobertIndie, we both think the docs are okay by clarifying the attribute (bucket name) and providing an example (pul

[GitHub] [pulsar] liguangcheng added a comment to the discussion: geo replicated subscribers

GitHub user liguangcheng added a comment to the discussion: geo replicated subscribers @volfco & @sijie Now whether the replication subscription status is available, the version I tested is 2.8.0, and it does not work normally at present. One site produces 10 messages and consumes two. anothe

[GitHub] [pulsar] volfco added a comment to the discussion: geo replicated subscribers

GitHub user volfco added a comment to the discussion: geo replicated subscribers @merlimat Sure. Prometheus Metrics: ```# TYPE pulsar_replicated_subscriptions_pending_snapshots gauge pulsar_replicated_subscriptions_pending_snapshots{cluster="iad"} 0.0 # TYPE pulsar_replicated_subscriptions_snap

[GitHub] [pulsar] merlimat added a comment to the discussion: geo replicated subscribers

GitHub user merlimat added a comment to the discussion: geo replicated subscribers Can you check on the broker logs if it's enabling the replicated subscription on that topic? GitHub link: https://github.com/apache/pulsar/discussions/18983#discussioncomment-4447451 This is an automati

[GitHub] [pulsar] volfco added a comment to the discussion: geo replicated subscribers

GitHub user volfco added a comment to the discussion: geo replicated subscribers @merlimat These logs tell me that replication has been enabled: ``` 4:55:14.350 [bookkeeper-ml-workers-OrderedExecutor-3-0] INFO org.apache.pulsar.broker.service.persistent.PersistentTopic - [persistent://develo

[GitHub] [pulsar] merlimat added a comment to the discussion: geo replicated subscribers

GitHub user merlimat added a comment to the discussion: geo replicated subscribers > This is not what I'm seeing. I can start the consumer in AUS, it'll start > reading. I close it at message 10 and wait a few seconds and start an IAD > consumer. Ok, missed that you mentioned you're waiting

[GitHub] [pulsar] merlimat added a comment to the discussion: geo replicated subscribers

GitHub user merlimat added a comment to the discussion: geo replicated subscribers Ok, that doesn't look correct then. Can you enable debug logs on `org.apache.pulsar.broker.service.persistent.{ReplicatedSubscriptionsController,ReplicatedSubscriptionSnapshotCache,ReplicatedSubscriptionsSnapsho

[GitHub] [pulsar] sijie added a comment to the discussion: geo replicated subscribers

GitHub user sijie added a comment to the discussion: geo replicated subscribers @volfco you might check out the replicated subscription introduced in 2.4.0. that can potentially solve you problem. GitHub link: https://github.com/apache/pulsar/discussions/18983#discussioncomment-4447446

[GitHub] [pulsar] volfco added a comment to the discussion: geo replicated subscribers

GitHub user volfco added a comment to the discussion: geo replicated subscribers @sijie I'll try that tomorrow and let you know if it meets my need. I didn't see that in my search of the docs GitHub link: https://github.com/apache/pulsar/discussions/18983#discussioncomment-4447447 This

[GitHub] [pulsar] merlimat added a comment to the discussion: geo replicated subscribers

GitHub user merlimat added a comment to the discussion: geo replicated subscribers Keep in mind that the subscription state in asynchronously replicated at configurable interval. Take a look at broker.conf: ``` # Frequency of snapshots for replicated subscriptions tracking. replicatedSubscri

[GitHub] [pulsar] aahmed-se added a comment to the discussion: geo replicated subscribers

GitHub user aahmed-se added a comment to the discussion: geo replicated subscribers There has been some discussion on geo replicated subscriptions @merlimat can provide more insights. GitHub link: https://github.com/apache/pulsar/discussions/18983#discussioncomment-4447444 This is an a

[GitHub] [pulsar] volfco added a comment to the discussion: geo replicated subscribers

GitHub user volfco added a comment to the discussion: geo replicated subscribers @sijie I've gotten a MVP cluster setup between two DCs that are ~40ms apart with replication between them. This is my code (I'm horrible at java): ```java import org.apache.pulsar.client.api.*; public class Main

[GitHub] [pulsar] volfco added a comment to the discussion: geo replicated subscribers

GitHub user volfco added a comment to the discussion: geo replicated subscribers The one thing I thought of in the background is that messages would have to be replicated with origin DC and origin ID or part of an Avro schema- as currently message IDs are unique per DC (from my understanding)

[GitHub] [pulsar] volfco created a discussion: geo replicated subscribers

GitHub user volfco created a discussion: geo replicated subscribers One of the big things missing in my book, is a way to have multiple subscribers across datacenters consume messages "exactly" once. DC A produces 5 messages. DC A has a consume subscription named TEST. DC B has a consumer wi

[GitHub] [pulsar] michaeljmarshall added a comment to the discussion: Zero receiver queue size for multi topic consumers

GitHub user michaeljmarshall added a comment to the discussion: Zero receiver queue size for multi topic consumers The documentation indicating that it cannot be done for a partitioned topic is going to provide the same justification: https://github.com/apache/pulsar/blame/master/site2/websit

[GitHub] [pulsar] congbobo184 added a comment to the discussion: Cannot parse schema

GitHub user congbobo184 added a comment to the discussion: Cannot parse schema @robshep @dhinesherode91 could you please check if the topic has multiple schemas by the problem when it happens? or upgrade the pulsar version and test if this problem has been fixed @tisonkun it seems like a

[GitHub] [pulsar] tisonkun added a comment to the discussion: Cannot parse schema

GitHub user tisonkun added a comment to the discussion: Cannot parse schema Moved to the Q&A category. If we find some bugs later, we can create issues correspondingly. GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-4414978 This is an automatically s

[GitHub] [pulsar] nodece added a comment to the discussion: Cannot parse schema

GitHub user nodece added a comment to the discussion: Cannot parse schema Thanks @robshep feedback. GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-4414974 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an ema

[GitHub] [pulsar] nodece added a comment to the discussion: Cannot parse schema

GitHub user nodece added a comment to the discussion: Cannot parse schema Do you have a stable way to reproduce this issue? GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-4414972 This is an automatically sent email for dev@pulsar.apache.org. To unsubs

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema I can't relaiably re-produce this, but the issue persists. Thanks @dhinesherode91 for adding your observations. We do not have this load. We have a single standalone running on ample VM (no cpu, memory , i/o or disk

[GitHub] [pulsar] tisonkun added a comment to the discussion: Cannot parse schema

GitHub user tisonkun added a comment to the discussion: Cannot parse schema @nodece is this issue a bug in the Pulsar side or depending on how users use it? GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-4414976 This is an automatically sent email for

[GitHub] [pulsar] nodece added a comment to the discussion: Cannot parse schema

GitHub user nodece added a comment to the discussion: Cannot parse schema I did a test to reproduce this case: ```java public class Main { public static void main(String[] args) throws Exception { var pulsarClient = PulsarClient.builder().serviceUrl("pulsar://localhost:6650").build

[GitHub] [pulsar] dhinesherode91 added a comment to the discussion: Cannot parse schema

GitHub user dhinesherode91 added a comment to the discussion: Cannot parse schema Thanks for the information. In my case, in my local I am running a standalone Pulsar and Consumer applications are Spring boot application. The above issue is not occurring in local. But in staging and produc

[GitHub] [pulsar] dhinesherode91 added a comment to the discussion: Cannot parse schema

GitHub user dhinesherode91 added a comment to the discussion: Cannot parse schema @congbobo184 The issue is not yet resolved. We are using Pulsar 2.7.1. Both broker and Pulsar client are using the same version. Our consumer is subscribed to a single topic only. Ours is an AVRO schema based t

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Hi No, sadly I cannot recreate this issue in isolation. But It occurs on ~50% of redeploys and requires repeated restarts of the application to clear it. We use TestContainers as part of the integration tests to spin

[GitHub] [pulsar] congbobo184 added a comment to the discussion: Cannot parse schema

GitHub user congbobo184 added a comment to the discussion: Cannot parse schema @dhinesherode91 hi, this issue problem solved? if not, could you please provide the broker version and client version. Do your consumers consume multiple topics? look at the source code, it does not store the `NON

[GitHub] [pulsar] dhinesherode91 added a comment to the discussion: Cannot parse schema

GitHub user dhinesherode91 added a comment to the discussion: Cannot parse schema Hey, I am facing a similar issue. I am running pulsar 2.7.1 and I have a topic with AVRO schema where my producers push avro messages and consumer receives and process the avro data. My consumer application re

[GitHub] [pulsar] congbobo184 added a comment to the discussion: Cannot parse schema

GitHub user congbobo184 added a comment to the discussion: Cannot parse schema if restart, this topic `persistent://myorg/myappA/ingress` not recover you can use admin api to check is the schema exist. GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-4414963

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Thank you, Attached is the application log from the first time this happened. It isn't clear exaclty which topic the consumer finds a null schema, but you can see in this example it was both consumers. On this occ

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Thank you, If the components are generally stable then there could be issues with my setup? In this case I am grateful for your support, and will look you up on slack With thanks R Get Outlook for iOS

[GitHub] [pulsar] congbobo184 added a comment to the discussion: Cannot parse schema

GitHub user congbobo184 added a comment to the discussion: Cannot parse schema @robshep Sorry to hear that, AvroSchema has been in the production environment for a long time. It is a stable feature. I think you can use one topic to test and use ```./pulsar-admin schemas get persistent://t

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Hi, This is still happening and we still need to keep restarting connected producers/consumers after updating our application. Occasionally if 20+restarts does not clear it, we destroy the (docker standalone) broker

[GitHub] [pulsar] codelipenghui added a comment to the discussion: Cannot parse schema

GitHub user codelipenghui added a comment to the discussion: Cannot parse schema @robshep Could you please provide more information about the schema configuration? Which schema compatibility policy are you using? how the schema of the topic looks like now(You can use the pulsar-admin schemas

[GitHub] [pulsar] codelipenghui added a comment to the discussion: Cannot parse schema

GitHub user codelipenghui added a comment to the discussion: Cannot parse schema @robshep Thanks, seems the schema definition is not the problem, I think maybe the problem is the reader cache in the StructSchema. @congbobo184 Could you please help take a look at this issue? GitHub link: ht

[GitHub] [pulsar] congbobo184 added a comment to the discussion: Cannot parse schema

GitHub user congbobo184 added a comment to the discussion: Cannot parse schema @robshep could you please provide more detailed information from app3, log and which topic the consumer `Cannot parse schema` GitHub link: https://github.com/apache/pulsar/discussions/18948#discussioncomment-441

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Thank you, I'm afraid I don't know how to get the schema compatibility policy of a topic - please can you advise. I don't see a cli command to show this) On the few occasions this has happened, it typically works OK

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema Hi, thanks for taking a look. There are 3 topics in use in this deployment. All have schemas. None of this code, or the Payload objects have changed for many months. I notice in App1 there is another topic `-RETRY`

[GitHub] [pulsar] congbobo184 added a comment to the discussion: Cannot parse schema

GitHub user congbobo184 added a comment to the discussion: Cannot parse schema @robshep hello, I look up your log and are you consume more than one topic in your consumer? it look like one topic does not have schema. GitHub link: https://github.com/apache/pulsar/discussions/18948#discussio

[GitHub] [pulsar] robshep added a comment to the discussion: Cannot parse schema

GitHub user robshep added a comment to the discussion: Cannot parse schema A log file showing the same issue encountered just now. A restart of the application recovered, but seemingly wasn't able to recover itself. [thingping.log](https://github.com/apache/pulsar/files/5490475/thingping.l

[GitHub] [pulsar] robshep created a discussion: Cannot parse schema

GitHub user robshep created a discussion: Cannot parse schema **Describe the bug** Reconnecting an updated consumer application that had NOT changed any of the following: * Any connection or topic details * Any message object details used to generate the AvroSchema This system was restarted

[GitHub] [pulsar] Amiaozhou edited a discussion: OOM on running pulsar-perf

GitHub user Amiaozhou edited a discussion: OOM on running pulsar-perf ### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version OS：Linux version 3.10.0-1160.el7.x86_64 Pulsar： apache-pulsar-2.10.1 ### Minimal

[GitHub] [pulsar] tisonkun added a comment to the discussion: [Bug] OOM on running pulsar-perf

GitHub user tisonkun added a comment to the discussion: [Bug] OOM on running pulsar-perf Cannot reproduce locally. I suspect it's about configuration issues or your local env restrictions. Moved to the Q&A form. GitHub link: https://github.com/apache/pulsar/discussions/18930#discussioncommen

[GitHub] [pulsar] michaeljmarshall added a comment to the discussion: Enable TLS hostname verification by default

GitHub user michaeljmarshall added a comment to the discussion: Enable TLS hostname verification by default This issue is still relevant. I have wanted to submit a PIP to do this, and to make sure that all configuration names for hostname verification are the same, but I haven't had a chance.

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

GitHub user github-actions[bot] added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18876#discussioncomment-4370052 This is an

[GitHub] [pulsar] wang-yeliang added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

GitHub user wang-yeliang added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin Maybe I missed the information before. Who developed lua-resty-kafka for Kafka? Eric Shen ***@***.***> 于2021年12月8日周三 20:53写道：

[GitHub] [pulsar] wang-yeliang added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

GitHub user wang-yeliang added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin We are looking forward to the development of pulsar community friends Lua Pulsar Library and APISIX Pulsar Plugin. Let's enrich the surrounding ecology of Aapche Pulsar. Eric S

[GitHub] [pulsar] ericsyh added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

GitHub user ericsyh added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin After a brief discuss with @wang-yeliang and @jiazhai, it'll be better to develop the APISIX plugin with native Lua cause of the performance and usability than using the [Plugin Ru

[GitHub] [pulsar] ericsyh added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

GitHub user ericsyh added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin I also take some attention on this point and I think the current challenge for Pulsar is lacking of the Lua client library like [lua-resty-kafka](https://github.com/doujiang24/lua-r

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin

GitHub user github-actions[bot] added a comment to the discussion: [DISCUSS] proposal: APISIX support Pulsar service plugin The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18876#discussioncomment-4370053 This is an

[GitHub] [pulsar] tisonkun added a comment to the discussion: Pulsar function Should support Generic output Message

GitHub user tisonkun added a comment to the discussion: Pulsar function Should support Generic output Message Move feature "request" to the discussion forum. GitHub link: https://github.com/apache/pulsar/discussions/18875#discussioncomment-4370033 This is an automatically sent email for

[GitHub] [pulsar] codelipenghui added a comment to the discussion: Pulsar function Should support Generic output Message

GitHub user codelipenghui added a comment to the discussion: Pulsar function Should support Generic output Message The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18875#discussioncomment-4370032 This is an automatic

[GitHub] [pulsar] eolivelli added a comment to the discussion: Pulsar function Should support Generic output Message

GitHub user eolivelli added a comment to the discussion: Pulsar function Should support Generic output Message This is related to: https://github.com/apache/pulsar/pull/9590 and to https://github.com/apache/pulsar/pull/9481 I really would like to see this feature land soon. I believe that the

[GitHub] [pulsar] pointearth created a discussion: Pulsar function Should support Generic output Message

GitHub user pointearth created a discussion: Pulsar function Should support Generic output Message **Is your feature request related to a problem? Please describe.** In the pulsar function, I don't want to define a particular class as O in `public interface Function { O process(I var1, Cont

[GitHub] [pulsar] codelipenghui added a comment to the discussion: Enable TLS hostname verification by default

GitHub user codelipenghui added a comment to the discussion: Enable TLS hostname verification by default The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18874#discussioncomment-4370027 This is an automatically sent

[GitHub] [pulsar] tisonkun added a comment to the discussion: Enable TLS hostname verification by default

GitHub user tisonkun added a comment to the discussion: Enable TLS hostname verification by default FYI @nodece is this issue still relevant? GitHub link: https://github.com/apache/pulsar/discussions/18874#discussioncomment-4370028 This is an automatically sent email for dev@pulsar.apac

[GitHub] [pulsar] tisonkun added a comment to the discussion: Enable TLS hostname verification by default

GitHub user tisonkun added a comment to the discussion: Enable TLS hostname verification by default Thanks for your explanation. Then moved to the discussion forum. GitHub link: https://github.com/apache/pulsar/discussions/18874#discussioncomment-4370030 This is an automatically sent em

[GitHub] [pulsar] nodece added a comment to the discussion: Enable TLS hostname verification by default

GitHub user nodece added a comment to the discussion: Enable TLS hostname verification by default This idea makes sense, but this change breaks user behavior. GitHub link: https://github.com/apache/pulsar/discussions/18874#discussioncomment-4370029 This is an automatically sent email fo

[GitHub] [pulsar] EronWright created a discussion: Enable TLS hostname verification by default

GitHub user EronWright created a discussion: Enable TLS hostname verification by default **Is your enhancement request related to a problem? Please describe.** Hostname verification is a critical aspect of TLS, especially when using the system-provided certificate bundle. TLS server authentic

[GitHub] [pulsar] Jason918 added a comment to the discussion: Throttle the ledger rollover

GitHub user Jason918 added a comment to the discussion: Throttle the ledger rollover @codelipenghui HI, I'll be happy to participate. Please check this more detailed solution. Add a new parameter `managedLedgerRolloverRateLimit`, rate limit the amount of rollover per second in one broker. Thi

[GitHub] [pulsar] codelipenghui created a discussion: Throttle the ledger rollover

GitHub user codelipenghui created a discussion: Throttle the ledger rollover **Is your feature request related to a problem? Please describe.** High ledger rollover frequency may lead to zookeeper in heavy workload. In order to make zookeeper run more stable, we should limit the ledger rollover

[GitHub] [pulsar] tisonkun added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

GitHub user tisonkun added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) @Redirts you can fork and patch the upstream ClickHouse connector for your use case in this situation. GitHub link: https://github.com/apache/pulsar/discussions/18872#discussionco

[GitHub] [pulsar] jiazhai added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

GitHub user jiazhai added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) would also like to have @vzhikserg in the thread, who is the author for clickhouse connector. GitHub link: https://github.com/apache/pulsar/discussions/18872#discussioncomment-4369

[GitHub] [pulsar] jiazhai added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

GitHub user jiazhai added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) @Redirts is this link help? https://pulsar.apache.org/docs/en/io-quickstart/#connect-pulsar-to-postgresql GitHub link: https://github.com/apache/pulsar/discussions/18872#discussio

[GitHub] [pulsar] Redirts added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

GitHub user Redirts added a comment to the discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) Hi, The link you provide describes setting up the jdbc sink without writing any line of code. I would like to be able to manipulate the data before it is sent to clickhouse via java

[GitHub] [pulsar] Redirts created a discussion: Question: Pulsar IO JDBC Java class example (Clickhouse)

GitHub user Redirts created a discussion: Question: Pulsar IO JDBC Java class example (Clickhouse) >From what I understand it is possible to create a custom Java class that reads >from pulsar and writes via JDBC to a database (in my I would like it to be >clickhouse). https://github.com/apac

[GitHub] [pulsar] Shoothzj created a discussion: Support report unrecoverable failure warnning by plugin

GitHub user Shoothzj created a discussion: Support report unrecoverable failure warnning by plugin **Is your feature request related to a problem? Please describe.** Sometimes, we are meeting some unrecovered problems. For example, delete zk topic node error, split bundle error **Describe the

[GitHub] [pulsar] tisonkun added a comment to the discussion: Update certificates used in TLS tests to use RSA keys & SHA-256 signature algorithm so that TLSv1.3 support can be added

GitHub user tisonkun added a comment to the discussion: Update certificates used in TLS tests to use RSA keys & SHA-256 signature algorithm so that TLSv1.3 support can be added @lhotari what's the status of this issue today? GitHub link: https://github.com/apache/pulsar/discussions/18870#dis

[GitHub] [pulsar] lhotari created a discussion: Update certificates used in TLS tests to use RSA keys & SHA-256 signature algorithm so that TLSv1.3 support can be added

GitHub user lhotari created a discussion: Update certificates used in TLS tests to use RSA keys & SHA-256 signature algorithm so that TLSv1.3 support can be added **Problem** In TLSv1.3, certificates using SHA-1 signature algorithm are considered legacy and it's not recommended that TLSv1.3

[GitHub] [pulsar] tisonkun added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

GitHub user tisonkun added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 cc @momo-jun This can indicate a doc issue. GitHub link: https://github.com/apache/pulsar/discussions/18868#discussioncomment-4369906 This is an automatic

[GitHub] [pulsar] codelipenghui added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

GitHub user codelipenghui added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 @devinbost Seems we should clarify it in the document, are you interested in fix it? GitHub link: https://github.com/apache/pulsar/discussions/18868#discu

[GitHub] [pulsar] devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

GitHub user devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 I removed the "gs://" prefix from the bucket name in broker.conf, and the issue was resolved. GitHub link: https://github.com/apache/pulsar/discussions/18868

[GitHub] [pulsar] devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

GitHub user devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 Could the bucket path be incorrect? Perhaps it doesn't like the prefix. GitHub link: https://github.com/apache/pulsar/discussions/18868#discussioncomment-43699

[GitHub] [pulsar] devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

GitHub user devinbost added a comment to the discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 FYI @david-streamlio GitHub link: https://github.com/apache/pulsar/discussions/18868#discussioncomment-4369902 This is an automatically sent email for d

[GitHub] [pulsar] devinbost created a discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1

GitHub user devinbost created a discussion: GCP Tiered Storage org.jclouds.rest.ResourceNotFoundException - Pulsar 2.6.1 I have a heartbeat topic that receives messages on the topic `persistent://public/default/canary`, and I configured retention on this topic to test tiered storage in GCP. W

[GitHub] [pulsar] tisonkun added a comment to the discussion: Multi-Topic subscription across tenant and namespace using regex in Java client throws IllegalArgumentException

GitHub user tisonkun added a comment to the discussion: Multi-Topic subscription across tenant and namespace using regex in Java client throws IllegalArgumentException Moved to discussion forum. This seems an interesting feature request, but it requires volunteers work on it and more design d

[GitHub] [pulsar] jiazhai added a comment to the discussion: Multi-Topic subscription across tenant and namespace using regex in Java client throws IllegalArgumentException

GitHub user jiazhai added a comment to the discussion: Multi-Topic subscription across tenant and namespace using regex in Java client throws IllegalArgumentException @rnowacoski currently regex subscription supports the topics in the same namespace. change this issue into a feature request.

[GitHub] [pulsar] tisonkun added a comment to the discussion: Multi-Topic subscription across tenant and namespace using regex in Java client throws IllegalArgumentException

GitHub user tisonkun added a comment to the discussion: Multi-Topic subscription across tenant and namespace using regex in Java client throws IllegalArgumentException Closed as stale. Please create a new issue if it's still relevant to the maintained versions. GitHub link: https://github.c

[GitHub] [pulsar] rnowacoski created a discussion: Multi-Topic subscription across tenant and namespace using regex in Java client throws IllegalArgumentException

GitHub user rnowacoski created a discussion: Multi-Topic subscription across tenant and namespace using regex in Java client throws IllegalArgumentException **Describe the bug** When using a regex to create a consumer and a regex pattern is present in the tenant or namespace section of the pat

[GitHub] [pulsar] yebai1105 added a comment to the discussion: negativeAcknowledge() parameter does not take effect

GitHub user yebai1105 added a comment to the discussion: negativeAcknowledge() parameter does not take effect Unacknowledged messages will be redelivered by default. If A acked message can not be redeliver again, what is the role of "negativeAcknowledge"?In what scenarios is the "negativeAckn

[GitHub] [pulsar] codelipenghui added a comment to the discussion: negativeAcknowledge() parameter does not take effect

GitHub user codelipenghui added a comment to the discussion: negativeAcknowledge() parameter does not take effect @yebai1105 You can acked the message at ``` msg = (Message) obj; System.out.println("Message received: " + msg.getValue()); consumer.acknowledge(msg); ``` A acked message can not

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: we have a use case where requires send message across multiple data centers . A through B to C。

GitHub user github-actions[bot] added a comment to the discussion: we have a use case where requires send message across multiple data centers . A through B to C。 The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18856#dis

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: negativeAcknowledge() parameter does not take effect

GitHub user github-actions[bot] added a comment to the discussion: negativeAcknowledge() parameter does not take effect The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18857#discussioncomment-4352726 This is an auto

[GitHub] [pulsar] drriguz added a comment to the discussion: negativeAcknowledge() parameter does not take effect

GitHub user drriguz added a comment to the discussion: negativeAcknowledge() parameter does not take effect I'm also confused about this, I found that messages are not redelivered in my application by using the following code: ```java try { MetaDataChangedEvent message = messageDe

[GitHub] [pulsar] codelipenghui added a comment to the discussion: we have a use case where requires send message across multiple data centers . A through B to C。

GitHub user codelipenghui added a comment to the discussion: we have a use case where requires send message across multiple data centers . A through B to C。 @fengxiaokai In the above case you provided, you should also add cluster-3 for the namespace in cluster-1 GitHub link: https://github.c

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: we have a use case where requires send message across multiple data centers . A through B to C。

GitHub user github-actions[bot] added a comment to the discussion: we have a use case where requires send message across multiple data centers . A through B to C。 The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18856#dis

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: What is the advertage of InputStream for MultipartFile ？

GitHub user github-actions[bot] added a comment to the discussion: What is the advertage of InputStream for MultipartFile ？ The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18855#discussioncomment-4352711 This is a

[GitHub] [pulsar] wangjialing218 added a comment to the discussion: we have a use case where requires send message across multiple data centers . A through B to C。

GitHub user wangjialing218 added a comment to the discussion: we have a use case where requires send message across multiple data centers . A through B to C。 the messages replicated from cluster1 to cluster2 are marked as "replicated message", these message will not replicate again to cluster

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: What is the advertage of InputStream for MultipartFile ？

GitHub user github-actions[bot] added a comment to the discussion: What is the advertage of InputStream for MultipartFile ？ The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18855#discussioncomment-4352710 This is a

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: Failed messages 1 with no more exception message

GitHub user github-actions[bot] added a comment to the discussion: Failed messages 1 with no more exception message The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18854#discussioncomment-4352701 This is an automati

[GitHub] [pulsar] codelipenghui added a comment to the discussion: Failed messages 1 with no more exception message

GitHub user codelipenghui added a comment to the discussion: Failed messages 1 with no more exception message @Aaronzk There is an internal pending queue with 1000 messages by default for a producer. if the server-side with a slow response but the application send messages very fast that will

[GitHub] [pulsar] Aaronzk added a comment to the discussion: Failed messages 1 with no more exception message

GitHub user Aaronzk added a comment to the discussion: Failed messages 1 with no more exception message @codelipenghui why not set `blockIfQueueFull(true)` as default? GitHub link: https://github.com/apache/pulsar/discussions/18854#discussioncomment-4352700 This is an automatically sen

[GitHub] [pulsar] github-actions[bot] added a comment to the discussion: How to dynamically produce and consume topic data

GitHub user github-actions[bot] added a comment to the discussion: How to dynamically produce and consume topic data The issue had no activity for 30 days, mark with Stale label. GitHub link: https://github.com/apache/pulsar/discussions/18853#discussioncomment-4352696 This is an automat

[GitHub] [pulsar] lhotari added a comment to the discussion: How to dynamically produce and consume topic data

GitHub user lhotari added a comment to the discussion: How to dynamically produce and consume topic data > When producing data, I want to dynamically send it to different topics. The > topics may be in different namespaces and different tenants. In Pulsar client, you must create a separate pr

[GitHub] [pulsar] beyondyinjl2 added a comment to the discussion: How to dynamically produce and consume topic data

GitHub user beyondyinjl2 added a comment to the discussion: How to dynamically produce and consume topic data When producing data, I want to dynamically send it to different topics. The topics may be in different namespaces and different tenants. GitHub link: https://github.com/apache/pulsar

[GitHub] [pulsar] liangyuanpeng added a comment to the discussion: How to dynamically produce and consume topic data

GitHub user liangyuanpeng added a comment to the discussion: How to dynamically produce and consume topic data You can use `client.newConsumer().topicsPattern()` for multiple topics. GitHub link: https://github.com/apache/pulsar/discussions/18853#discussioncomment-4352694 This is an aut

[GitHub] [pulsar] beyondyinjl2 added a comment to the discussion: How to dynamically produce and consume topic data

GitHub user beyondyinjl2 added a comment to the discussion: How to dynamically produce and consume topic data Like mqtt, a producer can send data on any topic, and a consumer can subscribe to topics dynamically GitHub link: https://github.com/apache/pulsar/discussions/18853#discussioncomment

[GitHub] [pulsar] beyondyinjl2 added a comment to the discussion: How to dynamically produce and consume topic data

GitHub user beyondyinjl2 added a comment to the discussion: How to dynamically produce and consume topic data For example, first subscribe to topic:persistent://public/default/my-topic: Consumer consumer = client.newConsumer() .topic("persistent://public/default/my-topic")

[GitHub] [pulsar] beyondyinjl2 created a discussion: How to dynamically produce and consume topic data

GitHub user beyondyinjl2 created a discussion: How to dynamically produce and consume topic data After creating a Producer, I want to send data to multiple different topics, or create a Consumer, I want to consume data from multiple topics GitHub link: https://github.com/apache/pulsar/discuss

[GitHub] [pulsar] eolivelli added a comment to the discussion: ManagedLedger should streamline the read requests

GitHub user eolivelli added a comment to the discussion: ManagedLedger should streamline the read requests @michaeljmarshall you can start a discussion with a proposal. you can start on dev@pulsar in order to have more people in the discussion. GitHub link: https://github.com/apache/pulsar/d

[GitHub] [pulsar] michaeljmarshall added a comment to the discussion: ManagedLedger should streamline the read requests

GitHub user michaeljmarshall added a comment to the discussion: ManagedLedger should streamline the read requests @eolivelli - thanks, I'll do that. GitHub link: https://github.com/apache/pulsar/discussions/18852#discussioncomment-4352616 This is an automatically sent email for dev@puls

  1   2   3   4   5   6   7   8   9   10   >