Incorrect syncker db reload on slave

[Amerio.Stephane]

Hello,

In our IG with multiple slaves, with 2.13, when a world_reload is triggered, we have multiple syncker error in the logs on the *slaves*:

Unigine~# world_reload
World loading "shared_MAR/ah_vdb_f_g.world" 1241ms
ERROR:	Syncker::Slave::read_node(): can't find node with slave id: 1289336846 (master id: 1289336846)!
ERROR:	Syncker::Slave::read_node(): can't find node with slave id: 1289336846 (master id: 1289336846)!
ERROR:	Syncker::Slave::read_node(): can't find node with slave id: 1542426868 (master id: 1542426868)!

In this case, the nodes are "rain_mist_Particles" and "rain_particles" (not placed by us, generated by the IG itself I guess), or even the "particles" node itself. Strangely, the slave is looking for a node with a slave id equal to the master id... Of course, slaves and master have the exact same version of the db+exe.

(Note: this seems independent from the bug reported in the private support thread)

 

[silent]

Hi Stephane,

Quote

In this case, the nodes are "rain_mist_Particles" and "rain_particles" (not placed by us, generated by the IG itself I guess), or even the "particles" node itself. Strangely, the slave is looking for a node with a slave id equal to the master id... Of course, slaves and master have the exact same version of the db+exe.

That's has been already fixed in our internal builds.

 

Errors with can't find node will be fixed later (the root cause is known, but there is no easy fix available right now). Will see if it's possible to implement if prior to upcoming hotfix or not. 

Thanks!