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.

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

Implement master slave scheme #2618

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Implement master slave scheme #2618

monetdb-team opened this issue Nov 30, 2020 · 0 comments


Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2010-07-16 13:43:23 +0200
From: @grobian
To: MonetDB5 devs <>
Version: -- development
CC: @mlkersten, @yzchang

Last updated: 2015-08-28 13:41:43 +0200

Comment 14436

Date: 2010-07-16 13:43:23 +0200
From: @grobian

MonetDB lacks a master/slave replication scheme, such as e.g. MySQL has.

Many ingredients are already implemented in the development branch. The master and slave properties are being handled by monetdb and merovingian, and a merovingian_url property is passed onto each database being started by merovingian.
The feature should be finished in a generic way, e.g. it shouldn't only just work on the same machine by accident because the IPs of master and slave are the same.

Comment 16029

Date: 2011-07-29 10:59:40 +0200
From: @sjoerdmullender

Apr2011-SP2 has been released.

Comment 16266

Date: 2011-09-16 15:09:14 +0200
From: @sjoerdmullender

The Aug2011 version has been released.

Comment 17355

Date: 2012-06-12 08:36:18 +0200
From: @grobian

as long as this is not working, we should remove the handles from monetdbd for this

Comment 17359

Date: 2012-06-13 16:03:32 +0200
From: @grobian

Changeset 877b04706e12 made by Fabian Groffen in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=877b04706e12

Changeset description:

master/slave replication: remove non-functional work in progress

The master/slave replication work will be committed in a separate
branch that will track the progress for bug #2618.
For as long as that work is not finished, we remove the work in progress
from the default (and so release) branche not to confuse users of the
system by presenting options for non-functional bits.

Comment 18105

Date: 2012-11-27 15:08:37 +0100
From: @yzchang

Don't know if possible and how to add test for this

Comment 19963

Date: 2014-08-06 14:59:06 +0200
From: @mlkersten

This request is dealt with in MonetDB Solutions context.
The code becomes available in an upcoming feature release.

Comment 21183

Date: 2015-08-28 13:41:43 +0200
From: @sjoerdmullender

Jul2015 has been released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant