Confluence breaks when setting up master replication

I am trying to setup replication of anothter database (not confluence) and I have already succeeded in doing so. However, confluence datbase is on the master mysql server and I get this message after I start the master server.

Non Clustered Confluence: Database is being updated by another Confluence instance

I am not trying to replicate confluence at all, i am replicating a completely different database. How do I fix this?

5 answers

Hi Andre,

The error you are getting there is how a "normal", (non-clustered), Confluence panics when it thinks that more than one node is updating its database, as described in this document:'Database+is+being+updated+by+an+instance+which+is+not+part+of+the+current+cluster'+Error+Message

However, as I understand it the database shouldn't be being updated in anyway as part of the mirroring process because it should only be copying the contents so what you willl need to look into is why this is occurring because it sounds like the mirroring configuration is wrong and so I'd recommend reviewing the documentation here to ensure that the replication process is correctly configured:

All the best,

I set up replication with that exact link. I tried addiing only the specific database but no luck. Really as soon as server-id=0 is added to master my.cnf confluence breaks.

I have the same problem.

as soon as I add server-id=1 to my.cnf and restart mysql, Confluence breaks. The confluence document you mention above does not exist.

I would really appreciate some help.

the error is still present, when I tell mysql to only replicate a specific db and let confluence as is:

server-id = 1

log-bin = /var/log/mysql/xxxxx-mysql-bin.log



having same problem - confluence breaks when set up Master/Slave


What is the solution to this problem? We've followed the instructions for Master/Slave >> and no joy

We saw

caused by: java.sql.SQLException: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.

and it wouldn't work until we set binlog_format = row. We didn't test it heavily, however.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Dec 18, 2018 in Confluence Cloud

Happy holidays from our team to yours!

Hi Community!  2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...

459 views 3 18
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you