Abhay – I’m not sure I understand which settings you mean. Are you saying this should be the same as "application.properties” “atlas.cluster.name"?
[cid:[email protected]] -- Sean Roberts Partner Engineering, EMEA @seano From: Abhay Kulkarni <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Monday, 3 April 2017 at 19:19 To: "[email protected]" <[email protected]> Subject: Re: Tag based policies not functioning (tagsync gives 400) Sean, One of the possible reasons for this type of error when Atlas is used in conjunction with Ranger to tag entities, is that there is a mismatch between entity’s Atlas cluster-name and corresponding Ranger Service-Name. Can you please check if they are identical? Thanks, -Abhay From: Abhay Kulkarni <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, April 3, 2017 at 10:01 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Tag based policies not functioning (tagsync gives 400) Hi Sean, What is the scenario when you run into this error? Can you please attach debug logs ranger-tagsync and ranger-admin (after setting logging level to DEBUG)? Thanks, -Abhay From: Sean Roberts <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, April 3, 2017 at 9:56 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Tag based policies not functioning (tagsync gives 400) Ranger folks – I’m getting the following error in tagsync.log: 03 Apr 2017 16:44:12 ERROR TagAdminRESTSink [Thread-8] - 177 Upload of service-tags failed with message HTTP 400 And tag based policies are not working. -- Sean Roberts Partner Engineering, EMEA @seano
