You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/06/13 10:59:37 UTC
[GitHub] [pulsar] Koh-Meta opened a new issue, #16037: FlinkPulsarSink EXACTLY_ONCE issue
Koh-Meta opened a new issue, #16037:
URL: https://github.com/apache/pulsar/issues/16037
**Describe the bug**
FlinkPulsarSink encounter issue with PulsarSinkSemantic.EXACTLY_ONCE.
**To Reproduce**
Steps to reproduce the behavior:
1. In apache-pulsar/conf/broker.conf, set transactionCoordinatorEnabled=true
2. Restart the broker
3. Added PulsarSinkSemantic.EXACTLY_ONCE
4. Encountered error Namespace not found, similar to
#15996
Here is a screenshot of my error:
5. Ran command:
sudo apache-pulsar/bin/pulsar initialize-transaction-coordinator-metadata -c pulsar-cluster-1 -cs 192.168.3.1:2181
6. And encountered another error: Transaction coordinator with id 1 not found.
**Desktop**
- ubuntu 20, pulsar 2.10.0, kop 2.10, flink 1.12
--
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: commits-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar] github-actions[bot] commented on issue #16037: FlinkPulsarSink EXACTLY_ONCE issue
Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on issue #16037:
URL: https://github.com/apache/pulsar/issues/16037#issuecomment-1183906267
The issue had no activity for 30 days, mark with Stale label.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org