Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Geo Replication Synced or Asynced #22

Closed
yiguolei opened this issue Sep 19, 2016 · 1 comment
Closed

Geo Replication Synced or Asynced #22

yiguolei opened this issue Sep 19, 2016 · 1 comment
Labels
deprecated/question Questions should happened in GitHub Discussions

Comments

@yiguolei
Copy link

In geo replication scenario, user's request will write to multi region and give user ack? or write to local region and give user ack then forward to other regions asynchronously ?
@merlimat merlimat added the deprecated/question Questions should happened in GitHub Discussions label Sep 19, 2016
@merlimat
Copy link
Contributor

From https://github.com/yahoo/pulsar/blob/master/docs/GeoReplication.md

Messages are first persisted in the local cluster, and then forwarded asynchronously to the remote clusters.

The request is written in the local region (with the configured number of replicas), producer will receive ack, and then the messages will be forwarded to remote regions.

sijie pushed a commit to sijie/pulsar that referenced this issue Mar 4, 2018
@srkukarni @sijie
Opt (apache#22)
9766676 
* Create pulsar-functions module (#1)

* Create pulsar-functions module

* rename `sdk` package to `api`

* Added the first cut of the Java interface for Pulsar functions (#2)

* Don't wait for the result. Instead chain it via CompletedFuture
@LutzWeischerFujitsu LutzWeischerFujitsu mentioned this issue Mar 17, 2021
Closed
hangc0276 referenced this issue in hangc0276/pulsar May 26, 2021
@sijie @jiazhai
Port delayed operations implementation from Kafka (#22)
511679d 
* Port Kafka timer classes

*Motivation*

Need to port Kafka's coordinator algorithm. It requires using Kafka's timer and deplayed operations.

* Port delayed operations implementation from Kafka
@xiaotongwang1 xiaotongwang1 mentioned this issue Aug 4, 2021
Closed
@paladin-dalao paladin-dalao mentioned this issue Jan 13, 2022
Closed
eolivelli referenced this issue in eolivelli/pulsar Feb 25, 2022
Fix the default maxRetries=-1 (#22)
ad512d6
dlg99 pushed a commit to dlg99/pulsar that referenced this issue Mar 4, 2022
@nicoloboschi
Fix the default maxRetries=-1 (apache#22)
7e6c5f2 
(cherry picked from commit ad512d6)
aloyszhang referenced this issue in aloyszhang/pulsar Aug 5, 2022
@baomingyu
Merge branch 'fix-consume-metric' into 'inlong-2.8.1.1' (merge reques…
fcb57c3 
…t !26)


fix-consume-metric
Fixes #22 
### Motivation
fix consume metric not print problem;
add metrics for pengdingAcks and pendingAckTimeAndSize;
add ut for new metrics about pengding ack
@ZHr-UChiHa ZHr-UChiHa mentioned this issue Jun 3, 2023
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
deprecated/question Questions should happened in GitHub Discussions
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@merlimat @yiguolei