I was finally able to use async replication. I misunderstood that the
initialization and the application were two different steps ... I thought
that when the init was done the replication was started but that's not what
I observed and starting it manually worked.
The other questions remained regarding the connection to a cluster and
about the best way to replicate data with consistency.
On Monday, October 16, 2017 at 6:27:01 PM UTC-4, srand06 wrote:
>
> Hi guys,
>
> What's the best way to backup data on an Arango cluster ? I read that
> using arangodump doesn't prevent any write during the dump. Then how do we
> end with a consistent backup ? Is there a way to just backup WAL after the
> dump has been done and be able to replay it after having restored to be
> sure to end with a consistent restored cluster ?
>
> I've read that using Asynchronous replication is also a way to do backup.
> But how do we setup one or more boxes to replicate data asynchronously from
> a cluster. I tried to it on a 5 nodes (1 coordinator, 3 agency nodes, 5 dbs
> nodes) cluster and a single node. That single node gets issues when it
> tries to replicate data from one of the dbs :
>
> 127.0.0.1:8529@_system> replication.getSyncResult(id)
> false
> 127.0.0.1:8529@_system> replication.getSyncResult(id)
> false
> 127.0.0.1:8529@_system> replication.getSyncResult(id)
> {
> "collections" : [
> {
> "id" : "10020066",
> "name" : "s10002"
> },
> {
> "id" : "10020067",
> "name" : "s10004"
> },
> {
> "id" : "10020068",
> "name" : "s10007"
> },
> {
> "id" : "10020069",
> "name" : "s10009"
> },
> {
> "id" : "10020070",
> "name" : "s10014"
> },
> {
> "id" : "10020071",
> "name" : "s10016"
> },
> {
> "id" : "10020072",
> "name" : "s10019"
> },
> {
> "id" : "10020073",
> "name" : "s10022"
> },
> {
> "id" : "10020074",
> "name" : "s10025"
> },
> {
> "id" : "10020075",
> "name" : "s10027"
> },
> {
> "id" : "10020076",
> "name" : "s10029"
> },
> {
> "id" : "10020077",
> "name" : "s10034"
> },
> {
> "id" : "10020078",
> "name" : "s10037"
> }
> ],
> "lastLogTick" : "10802463"
> }
> 127.0.0.1:8529@_system> replication.getSyncResult(id)
> JavaScript exception in file
> '/usr/share/arangodb3/js/client/modules/@arangodb/arangosh.js' at 98,7:
> ArangoError 404: Not Found
> ! throw error;
> ! ^
> stacktrace: ArangoError: Not Found
> at Object.exports.checkRequestResult (/usr/share/arangodb3/js/client/
> modules/@arangodb/arangosh.js:96:21)
> at Object.getSyncResult (/usr/share/arangodb3/js/client/modules/
> @arangodb/replication.js:281:12)
> at <shell command>:1:13
>
> And I can't tell what is the exact error ... I'm wondering if it's an
> unsupported operation with a cluster for example.
>
> But if there is a better way, I'm all ears.
>
> Thanks
>
>
--
You received this message because you are subscribed to the Google Groups
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
