Member since
09-25-2015
33
Posts
41
Kudos Received
9
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2824 | 04-11-2016 07:43 PM | |
5021 | 01-13-2016 01:27 AM | |
11241 | 12-17-2015 03:29 AM | |
3519 | 12-16-2015 11:13 PM | |
1164 | 12-08-2015 04:54 PM |
01-15-2016
01:12 AM
1 Kudo
Also look into the Ranger Audits from the Ranger Admin. If Ranger is allowing the request, then it will have policy which gave the permission.
... View more
01-13-2016
05:32 PM
You will have to first see where the bottle neck is. Regardless how much you are going to push to the Solr server, it can only index only so many. If you feel transport is the main issue, then you can just create couple of threads and each thread can have it's own solrClient instance. Secondly, you need to batch all your requests and you shouldn't commit from the client side. You should configure auto-commit on the Solr Server side and let it do the final commit. Between Solr doing the buffering v/s you doing the batching, I am not sure what would be the difference.
... View more
01-13-2016
01:27 AM
@sdutta in SolrCloud you should be using CloudSolrClient class. It should take care of everything you mentioned. Gets the active Solr servers from Zookeeper. And when you add the document, it will automatically send it to the server which is hosting the shard for the id, etc. It also keeps track if any Solr server is out of commission and automatically reconfigures itself. CloudSolrClient solrCloudClient = new CloudSolrClient(zkHosts); solrCloudClient.setDefaultCollection(collectionName);
... View more
01-05-2016
01:57 AM
1 Kudo
If you are using SolrJ from your client, then it will connect to zookeeper and automatically do the load balancing for you. If you are going to use SolrJ, then make sure use CloudSolrClient class
... View more
12-17-2015
05:02 AM
1 Kudo
Yes, this is the expected behavior. Ranger Policies are just for the ACL and not for ownership. The right way to do out here is to use Ranger for all the ACLs. You should you want root to access /user/oozie/test1, then from Ranger Admin, you should give "root" the required access to the folder. Ideally, you shouldn't play with owner and group.
... View more
12-17-2015
03:29 AM
2 Kudos
@Kuldeep Kulkarni, how are you setting user admin as administrator? Is the user admin in dfs.cluster.administrators? Do you have access to user "hdfs"?
... View more
12-17-2015
03:19 AM
1 Kudo
I agree, just because we can do it doesn't mean we should do it. From operation point of view, it is better to have one ranger per ambari cluster. This makes management very simple. Also, when it comes to upgrade, it will cause less headache.
... View more
12-17-2015
03:11 AM
There is no native support from Ambari to do this. If you are using Ambari in all env, then the Ambari which is hosting the main Ranger instance is oblivious of the clusters Ranger is supporting. The Ambari which is hosting Ranger will automatically configure Ranger for the components within it's cluster. For the other clusters, you have to go to each component and modify Ranger properties. E.g. you will have to set ranger.plugin.hbase.policy.rest.url property and few others. You also need to add all the services/repo using Ranger Admin UI.
... View more
12-16-2015
11:13 PM
2 Kudos
The primary limitation is wrt to UserSync. If there are multiple clusters, but using the same AD/LDAP, then you can use the same the Ranger instance to manage all of them.
... View more
12-08-2015
05:05 PM
1 Kudo
The upcoming patch for Ranger should support giving Zookeeper quorum used by Ranger as the property.
... View more