Thanks @yan's great inputs! I couldn't agree more almost of them.
> Also the API is not just what the machine reads but all the documentation
associated with it, right? It depends on what the documentation says; what
the user _should_ expect.
I think different users may have different expectation
I'm in favor of A & B. I find it provides a better "first experience" to
users.
>From my experience you usually have to have an explicit reason to not want
to checkpoint. Most people assume the semantics provided by the checkpoint
behavior is default and it can be a frustrating experience for them
good point, +1
2016-10-13 0:27 GMT+08:00 Jie Yu :
> Stephan,
>
> I think the only time the framework needs to set LIBPROCESS_ADVERTISE_IP is
> when DNAT is necessary for the container (e.g., bridge). In that
> case, LIBPROCESS_ADVERTISE_IP should always be agent ip and
> the relevant host port al
+1 to A and B
Aurora has enabled checkpointing for years and requires operators to enable
checkpointing on the slaves.
On Sat, Oct 15, 2016 at 11:57 AM, Joris Van Remoortere
wrote:
> I'm in favor of A & B. I find it provides a better "first experience" to
> users.
> From my experience you usual