hey,
Currently i am unable to reproduce the issue via test case. I guess this
happened when one update query was terminated abruptly. I was running a
python script which had update queries for orientdb, it was terminated
abruptly.
I thought there might be a work around if by any chance there was a miss
match in versions across distributed system.
Thanks
On Tuesday, July 18, 2017 at 4:54:31 PM UTC+5:30, Zeeshan Ahmad wrote:
>
> hey,
>
> I have 2 master distributed setup of orientdb in production.
> My default-distributed-db-config.json
>
> {
> "replication": true,
> "hotAlignment" : true,
> "autoDeploy": true,
> "readQuorum": 1,
> "writeQuorum": "majority",
> "executionMode": "undefined",
> "readYourWrites": true,
> "newNodeStrategy": "dynamic",
> "servers": {
> "orientMaster": "master",
> "orientMaster2": "master"
> },
> "clusters": {
> "internal": {
> },
> "*": {
> "servers": ["<NEW_NODE>"]
> }
> }
> }
>
> somehow few of the records have different version id's of the different
> servers. One of them has v57 and other v55
> Because of this i am getting :
> "Cannot UPDATE the record #25:426820 because the version is not the
> latest. Probably you are updating an old record or it has been modified by
> another user (db=v57 your=v55)\r\n\tDB name=\"superuser\""
> at client side.
>
> I am using orientdb 2.2.21
>
> Is this a known issue? how can i fix this?. how is this not detected in
> synchronisation?
> Need help immediately because i am using this in production.
>
> Thanks,
> Zeeshan
>
>
>
--
---
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.
