Member since
03-04-2016
165
Posts
35
Kudos Received
7
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1739 | 06-20-2017 03:08 PM | |
8971 | 05-11-2017 09:59 AM | |
8964 | 01-12-2017 01:50 PM | |
1327 | 10-26-2016 03:02 PM | |
5415 | 09-06-2016 07:40 AM |
01-12-2017
02:27 PM
Please check also whether your ranger-ugsync-site.xml file contains proper value of sleeptimeinmillisbetweensynccycle parameter. The file should be here: /usr/hdp/current/ranger-usersync/conf
... View more
01-12-2017
02:16 PM
Newly created users should be synced during next synchronization which is 1 minute maximum in your case. If newly created user gets synced successfully, there is no problem in Ranger AD configuration. It seems that you have connection problems / delay with your AD server. What is the ping time when you do "ping ad-server-ip-address"? Try to ping your ad server with "-t 60" parameter, and observe if the connection is OK all the time.
... View more
01-12-2017
01:50 PM
1 Kudo
Try to increase your memory. Edit: export HADOOP_OPTS="-XX:NewRatio=12 -Xmx4096m -XX:MaxHeapFreeRatio=40 -XX:MinHeapFreeRatio=15 -XX:+UseGCOverheadLimit -XX:+UseConcMarkSweepGC" hive-env template in Advanced hive-env tab. The -Xmx****m parameter represents the amount of memory in MB.
... View more
01-12-2017
01:44 PM
If your users and groups were synced for the first time, and now when you add user to AD he is not synced, the reason may be with your filter. Are you sure the user meets filter expression?
... View more
01-12-2017
01:40 PM
Changing the value to <6000 causes the default value to be set, which is 1 min (which was also your previous value - 60000millis). Can you check in usersync.log if the sync is really happening?
... View more
01-12-2017
01:31 PM
Hi, could you check your "ranger.usersync.sleeptimeinmillisbetweensynccycle" parameter's value? It can be found in "Advanced ranger-ugsync-site" in Ambari. It's value is time in milliseconds between every sync cycle. In usersync.log you can see your last sync time. Therefore you can determine the reason why the user is not added.
... View more
01-11-2017
11:35 AM
Thanks. I said after a while and I meant that after 30secs-1min Ambari Collector goes down. Ok then, if you cant remove the whole folder, did you try to move it to another place? i.e. /tmp. What operating system are you using? Try to move/delete also the location of "hbase.rootdir" (Ambari Metrics -> Config -> Advanced ams-hbase-site)
... View more
01-10-2017
02:41 PM
I am having the same issue. When I restart Metrics Collector sometimes it goes down after a while. Deleting the content of hbase-tmp/.../version-2/* helps. I am using HDP 2.5. Could you please share the collector log?
... View more
01-09-2017
02:26 PM
ok, nevermind. "lsattr" command lists attributes of file, and some attribute can be used to block file deletion, but when it is set, the output is different, so thats not the reason. Instead of deleting the whole folder, delete only the content of /hbase-tmp/zookeeper/zookeeper_0/version-2/* and restart Metrics Collector
... View more
01-09-2017
10:44 AM
Can you please provide the output of the command "lsattr" in your hbase-tmp folder.
... View more