2.2.26 VS (2.2.33 and 2.2.35)

[hossein-md]

OrientDB Version: 2.2.33, 2.2.35 and 2.2.26

OS: Windows

Expected behavior

I run the scenario that is explained in HERE with three different versions of Orientdb (2.2.33, 2.2.35 and 2.2.26)

It works as expected with the version 2.2.26 and it doesn't work with the versions 2.2.33 and 2.2.35

What is the difference between these versions? Is it a bug?

Steps to reproduce

HERE

[hossein-md]

Hi @luigidellaquila and @tglman

I read #8298 and saw that it used sharding. I've just tested version 2.2.30. It works! I don't know why
some versions of Orientdb have problem with sharding! Also I believe that version 2.2.30 isn't perfect
with sharding (at least with console and with my configuration), but at least it works and doesn't throw an error.

Do I have any mistakes with my configurations?

Thanks

[hossein-md]

I have worked more with 2.2.30.
With writeQuorum = 1 it doesn't throw an error but sometimes Orientdb returns wrong answer. For example, I use select * from #19:0 and Orientdb returns two records #19:0 and #19:1 or I traverse from all my vertex but it returns the nodes in one of the servers!