The old code doesn't look like it was able to send TASK_LOST updates in
such situation either. The failed over master simply doesn't have enough
information to do it, because it never heard from the agent that can tell
the master about its tasks. Could it be that the doc refers to TASK_LOST
updates produced in response to explicit reconciliation requests?

BTW, the doc seems to be a bit outdated. It mentions shutting down agents
that try to re-register after being removed due to failed health checks,
which is no longer true. Plus there's nothing about partition awareness.

On Mon, Jul 17, 2017 at 7:23 PM, David McLaughlin <[EMAIL PROTECTED]>
wrote:

Ilya Pronin
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB