Saw the following in the master logs:
After this, master becomes follower, and then leader again. However, it seems like the AuthorizerInstantiatorService does not start again when the master becomes leader. This is likely because AuthorizerInstantiatorService is bound as a singleton. But this issue needs more investigation because of the following:
1. It seems like AuthorizerInstantiantiatorService needs to be started whether or not authorization is enabled. This was by design, since we wanted to better control the lifecycle of authorizers.
2. When AuthorizerInstantiatorService is not started, CDAP is unusable, even if authorization is disabled. This should not happen.
Targeting this for 3.5.0 but we should perhaps include this in 3.4.1 if ever there is such a release.