question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Doc] Cluster-level failover shouldn't be part of Java client chapter

See original GitHub issue

Search before asking

  • I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?

When I read the Java client document, I found a very long chapter to introduce cluster-level failover. Seems that cluster-level failover is a feature of Pulsar rather than the Java client, so I think this part needs to be moved to another place.

What is your suggestion?

I think we should move the introduction of cluster-level failover to the next chapter of Geo Replication, and just give code snippets in client library pages (if supported).

cc @tisonkun @Anonymitaet @momo-jun @codelipenghui

Any reference?

https://pulsar.apache.org/docs/next/client-libraries-java#cluster-level-failover

Are you willing to submit a PR?

  • I’m willing to submit a PR!

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
labuladongcommented, Sep 4, 2022

though, this feature is only available in Java client for now, see client feature matrix: https://docs.google.com/spreadsheets/d/1YHYTkIXR8-Ql103u-IMI18TXLlGStK8uJjDsOOA0T20/edit#gid=1784579914

Thanks for pointing out that, but I think moving the chapter is better. Reasons:

  1. Cluster-level failover is a concept based on Geo replacation rather than a feature of the client.
  2. Advanced features shouldn’t be at the beginning of documentation.

We can emphasize this feature is only ready for the Java client yet, and add usage examples at the end of the Java client doc.

1reaction
D-2-Edcommented, Sep 6, 2022

@momo-jun > I think you can go ahead. The IA redesign is a long-term project with continuous improvements. I agree the overall IA work is a long-term project, but as we touch any content we should apply the best practices so we can make incremental improvements in keeping with the overall strategy.

Read more comments on GitHub >

github_iconTop Results From Across the Web

10 Client Failover Best Practices for Highly Available Oracle ...
This section describes Oracle Database 12c configuration best practices to automatically transition application connections from a failed primary database to a ...
Read more >
Chapter 39. High Availability and Failover - JBoss.org
A part of high availability is failover which we define as the ability for client connections to migrate from one server to another...
Read more >
Chapter 22. Client Failover Red Hat AMQ 7.1
To implement application-level failover when using JMS, set an ExceptionListener class on the JMS connection. The ExceptionListener is called by the broker in ......
Read more >
Administering a Cluster
This chapter describes how the Novell exteNd Application Server uses server clustering to implement load balancing and failover. It explains how to set...
Read more >
Chapter 27. High Availability, Load Balancing, and Replication
Database servers can work together to allow a second server to take over quickly if ... This guarantees that a failover will not...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found