Hi Alexander, Unfortunately changing the distributed cfg at run-time is a feature of Enterprise Edition.
The rule of the thumb is: - get the cfg in cluster - if it's not present, load the cfg in database directory - if it's not present, load the cfg in $ORIENTDB_HOME/config/distributed-config.json Lvc@ On 28 November 2014 at 11:29, Alexander Sahler <[email protected]> wrote: > Hello everybody. > > I tried to change distributed-config.json of a certain database (running > on version 1.7.9). While two instances are running, I put one instance down > and changed the file. After bringing the instance back it synchronized from > the running instance and took over the distributed-config.json from it, > overwriting the changes I made. > > So I tried another approach: Bring both nodes down, change both > of distributed-config.json and bring up the instances again. But in this > scenario, the distributed-config.json will be overwritten with > default-distributed-db-config.json from config directory! Changing this > file affects ALL databases that are contained in databases directory. > > How to do it right? > > Regards, Alexander. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" 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. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" 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.
