Skip to content

Conversation

@lenkis
Copy link
Contributor

@lenkis lenkis commented Jan 15, 2026

No description provided.

@lenkis lenkis changed the title Add info on release 3.6 What's new for release 3.6 Jan 15, 2026
@lenkis lenkis self-assigned this Jan 15, 2026
@github-actions github-actions bot temporarily deployed to branch-gh-5537-whats-new-3.6 January 15, 2026 16:18 Destroyed
@lenkis lenkis added the 3.6 label Jan 15, 2026
@github-actions github-actions bot temporarily deployed to branch-gh-5537-whats-new-3.6 January 15, 2026 16:36 Destroyed
@github-actions github-actions bot temporarily deployed to branch-gh-5537-whats-new-3.6 January 19, 2026 16:24 Destroyed
@github-actions github-actions bot temporarily deployed to branch-gh-5537-whats-new-3.6 January 27, 2026 10:15 Destroyed
@lenkis lenkis requested a review from sergepetrenko January 27, 2026 10:28
Copy link
Contributor

@sergepetrenko sergepetrenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarifications in the 2DC synchro section!
Please find a couple more comments below.


However, there are some limitations.
An important thing is that while data storages can be located in just 2 DCs,
the configuration storage (based on etcd or Tarantool) must be located in yet another DC
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I can parse this sentence correctly. Does it mean configuration storage has to be located in 3 datacenters or just in another DC, separate from the 2 used for storing data?

AFAIU, we should set up configuration storage in 3 DCs, the easiest way to do so is by using 2 existing "data" DCs + 1 extra "quorum" DC.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh, I deduced this from Alex Klenov's feedback: "Чтобы всё устойчиво работало, нужно чтобы хранилище конфигурации располагалось на трёх площадках. То есть данные мы храним в двух ЦОДах. Но при этом у нас есть третяя площадка для принятия решений."

So, I've guessed it wrong that we need only 1 configuration storage here -- the one located in DC #3.

Re-iterated it with Alex. Indeed, we need 3 config storages. Thanks for spotting!

to 1. The cluster keeps serving the clients.
b. DC #1 goes up and starts obtaining missed data from DC #2. The quorum size is still 1.
c. The data enrichment process for DC #1 is still in progress, but DC #2 goes down now.
In this case, the cluster becomes unavailable.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about case 1, let's ask @georgiy-belyanin for clarifications. Is this really what's going to happen?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants