Do I expect OE 3.1 to warp when there is a partially synced DB? about openethereum HOT 4 CLOSED

Is this a duplicate of #63?

from openethereum.

No these are different behaviors.

#63: Starting from clean datadir, if snapshot is interrupted, OE will not be able to resume snapshot. It will also not be able to sync at all. Datadir needs to be cleaned out again for OE to succeed on snapshot after restart.

This: Starting from partially synced 2.5.13 DB, OE will not attempt to snapshot (like OE 2.5.13 did), but instead will resume sync from where 2.5.13 was partial.

from openethereum.

@yorickdowne, the current behavior AFAIK is:

• only if database is fresh & empty start to warp sync
• if in the process of warp syncing there are no peers available for warp syncing, after 5 seconds, go to normal sync,

from openethereum.

Got it, thank you. This differs from 2.5.13, then. 2.5.13 would warp sync even if db was not fresh & empty.

The behavior as-is in 3.1 is fine, I think.

from openethereum.