Problem with Parity 2.7.2 service about ewf-token-bridge HOT 3 CLOSED

Sorry, false alarm, it started sync finally!

from ewf-token-bridge.

Update: this parity-2.7.2 service is still in sync, but it seems weird. I have attached an image showing docker logs, but the order of blocks is not correct, there are multiple skipped block, and also its way slower than the parity-2.5.13, which already synced since last night.

from ewf-token-bridge.

As we discussed on slack:

We wanted to use 2.7 but it was too buggy, so we downgraded our parities to 2.5 with hope that they will fix most of bugs.
Finally, parity contributors agreed that parity with higher version than 2.5 is not stable and they decided to start again from version 2.5.
Also, they recommended to use 2.5 for now.

The worst thing is that there is a difference in database structure between 2.5 and 2.7. It's not possible to downgrade versions using the same db.

Currently, they don't have solution for that.
There are three possibilities for now:

• Wait for version 3.1 which might have possibility to migrate from 2.7 to 3.1 (with they speed reaction we will wait months for that)
• Use 2.7 (or 3.0) which is not supported and fix errors manually (e.g. cron which restart parity each hours)
• Migrate to 2.5 version (it will require to sync whole db again)

Sources:

• https://medium.com/openethereum/vision-for-openethereum-ex-parity-client-eb7b11f6eef8
• https://github.com/openethereum/openethereum/issues/11858

from ewf-token-bridge.