Member since
10-21-2016
11
Posts
2
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1445 | 12-21-2016 02:47 PM | |
5293 | 10-26-2016 07:08 PM |
01-30-2017
06:25 PM
@apappu That was the hint I needed. It appears I had a keystore set for my HDFS ranger truststore. So no matter what I did, I would be unable to fix it. Once I corrected that issue, I see my namenode pulling the policy. Glad it was something stupid. Nick
... View more
12-21-2016
02:47 PM
@Ryan Cicak After staring at this with a hortonworks engineer (who was onsite for an unrelated reason), we figured out the problem. The whole time Ranger KMS was doing its job, but I had enabled compression on my mapper outputs with these changes: mapreduce.map.output.compress true mapreduce.output.fileoutputformat.compress true When I pulled the outputs of my sqoop job they looked like binary, but in reality they were just compressed. After deflating them everything is working correctly. Nick
... View more
10-26-2016
07:08 PM
Well I completely screwed this up. After that previous step it was working except my AD bind user had been locked out by my AD policy. So I completely started over by removing ranger and reinstalling it. After that I looked at Ancil's guide for setting up the trust store and when I restarted ranger it synced all of the users. Thanks everyone for pointing me toward the solution. Nick
... View more