mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From meghdoot bhattacharya <meghdoo...@yahoo.com.INVALID>
Subject Mesos replicated log dual writes
Date Tue, 05 Jun 2018 07:30:10 GMT
Recently investigation of logs of aurora around snapshot creations in replicated log come up
with this
I0601 21:57:27.322444   144 log.cpp:577] Attempting to append 524304 bytes to the logI0601
21:57:27.322501   144 coordinator.cpp:348] Coordinator attempting to write APPEND action
at position 6506690I0601 21:57:27.323122   139 replica.cpp:539] Replica received write request
for position 6506690 from __req_res__(3685)@x.x.x.x:yyyyI0601 21:57:27.443131   139 leveldb.cpp:341]
Persisting action (524331 bytes) to leveldb took 119.847993msI0601 21:57:27.443208   139
replica.cpp:710] Persisted action APPEND at position 6506690I0601 21:57:27.443437   139 replica.cpp:693]
Replica received learned notice for position 6506690 from @0.0.0.0:0I0601 21:57:27.478754
  139 leveldb.cpp:341] Persisting action (524333 bytes) to leveldb took 35.278735msI0601
21:57:27.478818   139 replica.cpp:710] Persisted action APPEND at position 6506690


It seems there are dual writes to leveldb for the same record (with 2 byte diff). Becomes
expensive if that is the case for large records. Hoping to get some insights.
Thx

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message