Initializing values for deployment that does not start with clean RocksDB
pgebal opened this issue · 1 comments
pgebal commented
When we start with a clean state, we initialize RocksDB storage using release task.
When we deploy on a running environment, we do not have a way to set new values, which causes errors.
For example:
GenServer :in_flight_exit_deleted_processor terminating
** (MatchError) no match of right hand side value: :not_found
(omg 1.0.3) lib/omg/ethereum_event_listener.ex:104: OMG.EthereumEventListener.handle_continue/2
(stdlib 3.12) gen_server.erl:637: :gen_server.try_dispatch/4
(stdlib 3.12) gen_server.erl:388: :gen_server.loop/7
(stdlib 3.12) proc_lib.erl:249: :proc_lib.init_p_do_apply/3
Last message: {:continue, :setup}