Lari Hotari
04/02/2024, 7:50 AMLari Hotari
04/02/2024, 7:50 AMLari Hotari
04/03/2024, 10:52 AMkailevy
04/03/2024, 5:18 PMNaresh
04/04/2024, 1:15 AMFailover
, Exclusive
, Shared
, Key_Shared
Subscriptions work on all the partitions in a topic or they are limited to only one partition in a topic ? When using OpenMessagingBenchmark with Failover mode, we see that there is delay up on a partitioned topic. Wondering whats the behaviour of these subscription modes on a partitioned topic
QQ #2: We are creating a tenant (c1, c2, c3 .. cN, cAgg)
, namespace (c1, c2, c3,. ... cN, cAgg)
, topic (c1, c2, c3 ... CN, cAgg)
and using per message replication clusters to (cAgg)
this gives us flexibility to aggregate messages from all (1..N) clusters to (cAgg). Any scalability concerns to be worried about when N (number of clusters) are in few thousands ?Conor
04/05/2024, 12:40 PMConor
04/05/2024, 12:45 PMYang Ou
04/05/2024, 9:05 PMorg.apache.bookkeeper.mledger.ManagedLedgerException$CursorNotFoundException: ManagedCursor not found: <kop-consumer-cursor-persistent://kafka/archiving/useractions.json-partition-2-54292994-105331-8af2e1e053>
2024-04-05T20:56:33,844+0000 [pulsar-ph-kafka-57-2] ERROR io.streamnative.pulsar.handlers.kop.KafkaRequestHandler - Caught error in handler, closing channel
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
2024-04-05T20:56:33,844+0000 [pulsar-ph-kafka-57-2] WARN io.streamnative.pulsar.handlers.kop.KafkaTopicConsumerManager - [[id: 0x0dc8a7e7, L:/172.31.202.83:9092 ! R:/172.31.102.64:49270]] Error deleting cursor <kop-consumer-cursor-persistent://kafka/archiving/useractions.json-partition-3-54293005-103622-18337c3188> for topic <persistent://kafka/archiving/useractions.json-partition-3> for reason: TopicConsumerManager close but cursor is still outstanding.
org.apache.bookkeeper.mledger.ManagedLedgerException$CursorNotFoundException: ManagedCursor not found: <kop-consumer-cursor-persistent://kafka/archiving/useractions.json-partition-3-54293005-103622-18337c3188>
2024-04-05T20:56:33,844+0000 [pulsar-ph-kafka-57-2] WARN io.streamnative.pulsar.handlers.kop.KafkaTopicConsumerManager - [[id: 0x0dc8a7e7, L:/172.31.202.83:9092 ! R:/172.31.102.64:49270]] Error deleting cursor <kop-consumer-cursor-persistent://kafka/archiving/useractions.json-partition-2-54292994-105019-d8f0fd1536> for topic <persistent://kafka/archiving/useractions.json-partition-2> for reason: TopicConsumerManager close but cursor is still outstanding.
org.apache.bookkeeper.mledger.ManagedLedgerException$CursorNotFoundException: ManagedCursor not found: <kop-consumer-cursor-persistent://kafka/archiving/useractions.json-partition-2-54292994-105019-d8f0fd1536>
2024-04-05T20:56:33,844+0000 [pulsar-ph-kafka-57-2] WARN io.streamnative.pulsar.handlers.kop.KafkaTopicConsumerManager - [[id: 0x0dc8a7e7, L:/172.31.202.83:9092 ! R:/172.31.102.64:49270]] Error deleting cursor <kop-consumer-cursor-persistent://kafka/archiving/useractions.json-partition-6-54293135-93039-fd084b5e53> for topic <persistent://kafka/archiving/useractions.json-partition-6> for reason: TopicConsumerManager close but cursor is still outstanding.
org.apache.bookkeeper.mledger.ManagedLedgerException$CursorNotFoundException: ManagedCursor not found: <kop-consumer-cursor-persistent://kafka/archiving/useractions.json-partition-6-54293135-93039-fd084b5e53>
2024-04-05T20:56:33,844+0000 [pulsar-ph-kafka-57-2] WARN io.streamnative.pulsar.handlers.kop.KafkaTopicConsumerManager - [[id: 0x0dc8a7e7, L:/172.31.202.83:9092 ! R:/172.31.102.64:49270]] Error deleting cursor <kop-consumer-cursor-persistent://kafka/archiving/useractions.json-partition-20-54293101-95875-881b89ac5e> for topic <persistent://kafka/archiving/useractions.json-partition-20> for reason: TopicConsumerManager close but cursor is still outstanding.
Could anyone help point out what might have been the issues?Rahul
04/08/2024, 2:33 PMAlexander Brown
04/08/2024, 3:25 PMGilles Barbier
04/08/2024, 6:20 PMGergely Fábián
04/09/2024, 8:49 AMVishal Pimpale
04/09/2024, 12:22 PMZachary Benavides
04/09/2024, 8:09 PMMarek Prochera
04/10/2024, 12:49 PMTom Korn
04/10/2024, 2:14 PMTom Korn
04/12/2024, 7:07 AMAlexandre Brilhante
04/19/2024, 9:35 PMLari Hotari
04/20/2024, 2:01 PMWallace Peng
04/21/2024, 5:34 AMbin/pulsar-admin topics stats-internal <persistent://pulsar/pulsar/pulsar-broker-0.pulsar-broker.pulsar.svc.cluster.local:8080/healthcheck>
No such ledger exists on Metadata Server
Reason: No such ledger exists on Metadata Server
Danial Mirza
04/24/2024, 5:07 AMGilles Barbier
04/24/2024, 12:40 PMGergely Fábián
04/24/2024, 4:31 PMitowey
04/24/2024, 11:11 PMfunctionsWorkerEnabled=true
). Functions are deployed using the Process Runtime in the broker/Function Worker (FW) under a single container. (Note: This is a legacy deployment. Our plan is to upgrade to pulsar 3.0 and deploy the Function Worker as a set of standalone containers with Process Runtime, with the final step of moving to a Kubernetes StatefulSet and deploying functions on Kubernetes.)
The cluster had been running for an extended period without any downtime. However, after restarting the broker container, the Function Worker (along with all function endpoints) became unresponsive, with only about 10% of the expected functions restarting. Despite observing the Function Worker leadership reassigning after the broker container restart, it would not respond to any pulsar-admin
commands.
Has anyone encountered a similar issue or has any suggestions on how to debug this situation?Gilles Barbier
04/25/2024, 3:30 PMFrank Kelly
04/25/2024, 3:40 PMDavid K
04/25/2024, 3:51 PMGirish Sharma
04/25/2024, 5:31 PMJeff Bolle
04/26/2024, 12:49 PMSchemaConverter.convertPulsarAvroSchemaToNonNullSchema
function. With one of my test schemas it is throwing an UnsupportedOperationException
, though I can't find anything in the Hudi documentation laying out why this field configuration would be unsupported. That all said, I'm new to the datalake world and would like to learn the intent behind this function and understand what I need to do to validate that a schema is appropriate for writing to Hudi (since that is my only use case).Alexander Brown
04/26/2024, 3:56 PM