Calls to routers and storages when crud-router and crud-storage roles initialization is not finished yet

[savinov]

There are exceptions trown in cartridge-java driver due to crud-router and crud-storage roles initialization issues.

How to repoduce:

• run some load test to call crud.select (with prefer_replica=true and balance=true) and crud.upsert
• stop/start a few routers
• stop/start a few replicas (not leaders) in replicasets

Result for select:

org.springframework.dao.DataRetrievalFailureException: InnerErrorMessage:
code: 33
message: Procedure '_crud.select_on_storage' is not defined; nested exception is io.tarantool.driver.exceptions.TarantoolInternalException: InnerErrorMessage:
code: 33
message: Procedure '_crud.select_on_storage' is not defined

Result for upsert:

Caused by: io.tarantool.driver.exceptions.TarantoolInternalException: InnerErrorMessage:
code: 32
message: ...example.lua:100: variable 'crud' is not declared

[Totktonada]

The example.lua code that calls a crud function works on a router, correct? Whether this code is in a role, which depends on the 'crud-router' role? (Or, whether it is guaranteed that the call to crud is always performed after crud.init_router()?)

The documentation does not shed light on the order of roles initialization, but I guess that dependent roles are initialized first. I filed tarantool/doc#2371 regarding this several days ago.

[savinov]

Correct, example.lua works on a router. The code is in a role which depends on crud-router.
Somehow crud variable and _crud.select_on_storage function are not defined at the call moment.

[savinov]

SDK version: Tarantool Enterprise 2.7.3-0-gdddf926c3-r428
Cartridge version: 2.7.2
CRUD version: 0.9.0

[Totktonada]

The problem with storages should be generally resolved after tarantool/vshard#298, however we can implement some simple retrying strategy in crud even without this feature.

The problem with routers should be resolved by tarantool/cartridge-java#159 and, sadly, there is nothing that we can fix on the crud side.