Domain Synchronizer role removed?

%3CLINGO-SUB%20id%3D%22lingo-sub-1526268%22%20slang%3D%22en-US%22%3EDomain%20Synchronizer%20role%20removed%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1526268%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20currently%20deploying%20ATP%20to%20my%20DC%20fleet%20in%20one%20of%20my%20production%20domains%20and%20I'm%20seeing%20higher%20than%20normal%20CPU%20on%20one%20particular%20DC.%20My%20first%20thought%20was%20this%20was%20the%20Domain%20Synchronizer%20role%20doing%20%22extra%20work%22....%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20at%20the%20release%20notes%2C%20it%20seems%20the%20toggle%20button%20has%20been%20removed%20in%20release%20ATP%202.86.%20My%20questions%20--%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20How%20can%20I%20see%20which%20DC's%20are%20actually%20performing%20this%20function%20behind%20the%20scene%3F%20Logs%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20How%20can%20I%20manually%20change%20this%20now%20that%20the%20toggle%20button%20has%20been%20removed%3F%20I%20rather%20not%20have%20some%20of%20my%20heavily%20used%20DC's%20perform%20this%20function.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1526286%22%20slang%3D%22en-US%22%3ERe%3A%20Domain%20Synchronizer%20role%20removed%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1526286%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F377753%22%20target%3D%22_blank%22%3E%40ChadWst%3C%2FA%3E%26nbsp%3BHi%2C%3C%2FP%3E%0A%3CP%3ETo%20answer%20the%20questions%20above%3A%3C%2FP%3E%0A%3CP%3E-%20There%20is%20no%20way%20for%20the%20customer%20to%20see%20which%20sensor%20is%20currently%20doing%20a%20sync%3C%2FP%3E%0A%3CP%3E-%26nbsp%3B%20There%20is%20no%20way%20for%20customers%20to%20control%20which%20sensors%20will%20be%20used%20for%20the%20sync%3C%2FP%3E%0A%3CP%3EThe%20reason%20it%20became%20so%2C%20is%20that%20the%20sync%20process%20was%20refactored%2C%20and%20now%20is%20not%20effecting%20performance%20significantly%2C%20so%20it%20doesn't%20really%20matter%20which%20sensor%20does%20it.%20The%20option%20to%20configure%20was%20not%20effective%2C%20and%20customers%20tended%20to%20use%20it%20the%20wrong%20way%20creating%20negative%20effects%20on%20the%20system.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I'm currently deploying ATP to my DC fleet in one of my production domains and I'm seeing higher than normal CPU on one particular DC. My first thought was this was the Domain Synchronizer role doing "extra work".... 

 

Looking at the release notes, it seems the toggle button has been removed in release ATP 2.86. My questions --

 

- How can I see which DC's are actually performing this function behind the scene? Logs?

 

- How can I manually change this now that the toggle button has been removed? I rather not have some of my heavily used DC's perform this function. 

 

 

2 Replies
Highlighted

@ChadWst Hi,

To answer the questions above:

- There is no way for the customer to see which sensor is currently doing a sync

-  There is no way for customers to control which sensors will be used for the sync

The reason it became so, is that the sync process was refactored, and now is not effecting performance significantly, so it doesn't really matter which sensor does it. The option to configure was not effective, and customers tended to use it the wrong way creating negative effects on the system.

Highlighted

@Eli Ofek  -- Thx for the prompt response. I will open a case related to the HIGH CPU.