I am not aware any ticket related to this, so creating a ticket for
tracking the issue would be great.
- Jie
On Tue, Jun 5, 2018 at 9:30 AM, Meghdoot bhattacharya <
meghdoo...@yahoo.com.invalid> wrote:
> Thx Joseph. Writing back the entire blob is costly instead of writing back
> only the 2
Thx Joseph. Writing back the entire blob is costly instead of writing back only
the 2 bytes. In this case this record is just a chunk of large snapshot that is
getting written. So it multiplies.
Should I open a jira to track and resolve this or something like this is
already open?
Thx
> On
The two-byte difference is most likely coming from the "learned" field:
https://github.com/apache/mesos/blob/master/src/messages/log.proto#L49
The first time an entry is recorded, the entry is "unlearned", basically
meaning that the entry has not been written to a quorum of masters (yet).
Once a
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
