Skip to content
This repository has been archived by the owner on Apr 1, 2024. It is now read-only.

ISSUE-16037: FlinkPulsarSink EXACTLY_ONCE issue #4369

Open
sijie opened this issue Jun 13, 2022 · 0 comments
Open

ISSUE-16037: FlinkPulsarSink EXACTLY_ONCE issue #4369

sijie opened this issue Jun 13, 2022 · 0 comments

Comments

@sijie
Copy link
Member

sijie commented Jun 13, 2022

Original Issue: apache#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
    image
  4. Encountered error Namespace not found, similar to
    [bug][java-client] Client creation fails with enableTransactions=true if topic transaction_coordinator_assign has not been created yet  apache/pulsar#15996
    Here is a screenshot of my error:
    image
  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
@sijie sijie added the type/bug label Jun 13, 2022
@sijie sijie added the Stale label Jul 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant