Eventstore: NonPromotable Clone

Created on 6 Oct 2014  Â·  13Comments  Â·  Source: EventStore/EventStore

useful feature or use a shoveler?

kinenhancement

Most helpful comment

I am looking at this today. Apparently its on an unmerged branch from years ago. I will be reviewing it and will follow through on it as its a quite useful feature.

All 13 comments

We want a clone in our office for dev work. Is this possible yet? Is there any documentation on setting up a shoveler?

Thanks

Basically subscribetoall and write. There is currently a branch with the
work on it to do with the replication protocol it just needs some testing

On Wed, May 20, 2015 at 9:08 AM, davidmarkellis [email protected]
wrote:

We want a clone in our office for dev work. Is this possible yet? Is there
any documentation on setting up a shoveler?

Thanks

—
Reply to this email directly or view it on GitHub
https://github.com/EventStore/EventStore/issues/263#issuecomment-103774268
.

Studying for the Turing test

@gregoryyoung I think this would be a nice and useful feature to have out of the box from the eventstore itself.

It will be (its a new replication model coming for multi-master).

On Fri, Jan 29, 2016 at 12:54 PM, Alex Henning Johannessen <
[email protected]> wrote:

I think this would be a nice and useful feature to have out of the box
from the eventstore itself.

—
Reply to this email directly or view it on GitHub
https://github.com/EventStore/EventStore/issues/263#issuecomment-176739460
.

Studying for the Turing test

:+1:

Hi,
I know this is an old request, but I was wondering if there is any way this can get on the road map again?
We are running in AWS and would like to have a cloned node in another region for backup and reduce of recovery in case of failure. We want to have this node always as a clone dont want it to come in to the cluster as a slave.

Thanks
Chris

Definitely would be a nice feature

We are we at on this? Is it possible to create a non-promotable clone yet?

I believe this was implemented a couple of years ago but need to verify.

How is the feature accessed? Obviously, I've checked documentation and not
found anything. Thank you

On Thu, Jul 26, 2018, 3:49 PM Greg Young, notifications@github.com wrote:

I believe this was implemented a couple of years ago but need to verify.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/EventStore/EventStore/issues/263#issuecomment-407984003,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYP5mdAWa3NEhbLZpNNk-bOCklYa3TBks5uKViGgaJpZM4CrbiC
.

I am looking at this today. Apparently its on an unmerged branch from years ago. I will be reviewing it and will follow through on it as its a quite useful feature.

Thank you!

On Thu, Jul 26, 2018 at 6:20 PM Greg Young notifications@github.com wrote:

I am looking at this today. Apparently its on an unmerged branch from
years ago. I will be reviewing it and will follow through on it as its a
quite useful feature.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/EventStore/EventStore/issues/263#issuecomment-408017269,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYP5h5QdYMKSEFb0F0OkXcmC1AA_k-Zks5uKXvrgaJpZM4CrbiC
.

--
Benjamin Boyle
Skype: benjaminboyle

Read only replica (formerly known as non promotable clone) is being released in v6 and there will be documentation to go with it. see #1976

Was this page helpful?
0 / 5 - 0 ratings