This is a known issue impacting NSX-T Data Center.
Workaround:
Reboot the NSX-T managers one by one.
Before rebooting a manager, make sure the cluster is up and healthy, as
admin on the NSX-T manager cli, run:
get cluster status -> ensure all services are up
Then proceed and reboot the next manager.