Long-run user thread(such as HiveThriftServer2) causes the 'process leak' in yarn-client mode

Recently when I use the Yarn HA mode to test the HiveThriftServer2 I found a problem that the driver can't exit by itself.
To reappear it, you can do as fellow:
1.use yarn HA mode and set am.maxAttemp = 1for convenience
2.kill the active resouce manager in cluster

The expect result is just failed, because the maxAttemp was 1.

But the actual result is that: all executor was ended but the driver was still there and never close.