In a setup where we have load balanced CM servers and publishers and they are located in multiple datacenters. The publishers that are not co-located in the same datacenter where the CMSDB exists, those publishing jobs take longer time during rendering/resolving phase of publishing. This is due to the network latency when publisher is going across datacenter to get to CMS DB before handing over the package to Transport service. We want to keep all publisher up and running and have an active-active setup for CM servers and Publishers in all datacenters. CMS admin should be able to mark a publisher online/offline on need basis.