tree a949313365c18daed2d3286881d7bb5c681548af
parent dd2f2b83b0d8270b90e0dc6400527c54bf2cbb9b
author lakshmi-manasa-g <mgaduputi@linkedin.com> 1607356225 -0800
committer GitHub <noreply@github.com> 1607356225 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfzk9BCRBK7hj4Ov3rIwAAdHIIAFbQEaObJxx0PriquYSZsh40
 ByxtaW24zUZHjVjrYAbGMRhhhtVeqV9fmirSb0tcKn9ZSJ2Ax62xDS/8ut1t8M0E
 0p4LmVmD4q5mWocsGjaex31zS/HfzwkdDvLSjGg4NTEbtra8l5whkE2EPQV5pR4g
 hhC0SmAy70u7RdMaqS+YVY2gD7urwjWMUl4IGVvwGEa1ZAvRm+mh1lbOl1HPXrCl
 6L5wJzzqGRxuXHzSeMyrjACrQrVWWCIcfnUMJ16FhZ2uSAYhxZnZqzUNL+AOxOJG
 Oym3W9KgmYMsyfQQaKrkB4GpU6sIC1tgGJcBmgLBAhyvO6O2G2KzDGeMSU3olMs=
 =17dg
 -----END PGP SIGNATURE-----
 

SAMZA-2611: [AM-HA] heartbeat reestablish causes container's heartbeat thread to die (#1452)

Symptom: When new AM takes a long time to to start up, already running container's heartbeat thread silently dies and does not make any heartbeat requests to the new AM.

Cause: AM url (yarn.am.tracking.url) key-value is removed from Coordinator stream when new AM is starting up - as this config is present in old config (aka coordinator stream) but not in the new AM generated config. This causes the running container to fetch a null when its constantly fetching value for this key and thus throws NPE.

Changes: When AMHA is enabled, do not remove this config