About naveen1

zuoseven · ‎07-01-2019

hi，man, did you fixed this problem,i have the same too.

Jerry · ‎03-12-2019

Hi Naveen, If you have limited number of ports available. You can assign port for each application. --conf "spark.driver.port=4050" —conf "spark.executor.port=51001" --conf "spark.ui.port=4005" Hope it helps Thanks Jerry

nirustr · ‎05-30-2017

Hi Naveen, I realized my understanding is wrong and understoop that system sees "joy" as the user who is trying to write and permissions would be enforced against "joy". So I set up an ACL for joy and my program worked fine. Now I understand ACL's usage with respect to impersonation. Thanks for the pointer. Regards, Niranjan

mbigelow · ‎05-24-2017

https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/ArchivalStorage.html I recommend opening a new topic you have any other questions on storage pools. That way this discussion can stay on topic.

naveen1 · ‎05-24-2017

After recomission can just add the datanode back and Name node will identify all the blocks that were previously present in this datanode. Once Namenode identifies this information, It will wipe out the third replica that it created during the datanode decomission. You may have to run hdfs balancer if you format the disks and then recomision it to the cluster which is not a best practise.

naveen1 · ‎05-01-2017

I had to check grant in hr_role instead of emp_role. This is the solution for this question.

cjervis · ‎05-03-2016

I'm happy to see you found it. Thanks for sharing. 🙂

venkatsambath · ‎03-30-2016

Hi, Encryption at rest is used for protecting your data from an unauthorized user who has no read permission in hdfs or has no access to cluster and is trying to read it from the disk directly. In your example the directory /tmp/user1zone1 has read access for all cluster users and hence user2 is allowed to read from it. drwxr-xr-x - user1 supergroup 0 2016-02-10 02:42 /tmp/user1zone1

naveen1 · ‎01-28-2016

Thank you all for your time, logical workaround sounds good to me.

ben.hemphill · ‎01-18-2016

You won't save HDFS filesystem space by "archiving" or "combining" small files. In many scenarios you will get a performance boost from combining. You will also reduce the metadata overhead on the namenode by combining as well.

Online	Offline
Last Visited	‎07-31-2019 03:12 PM

Member Since	‎12-28-2015 09:51 AM
Last Visited	‎07-31-2019 03:12 PM
Posts	47
Kudos received	2

Cloudera Community

Re: Error while trying to impersonate a user to ac...

Re: Sentry grant on a table

Re: listing hdfs files as per timestamp

Re: HDFS encryption confusion

Re: Cloudera 5.4.x cluster randomly reports "Clock...

Re: Spark port binding issue

Re: Error while trying to impersonate a user to ac...

Re: Hadoop Data Node: why is there a "magic" numbe...

Re: Best practices to join nodes back into the clu...

Re: Sentry grant on a table

Re: listing hdfs files as per timestamp

Re: HDFS encryption confusion

Re: Is it possible to use trash in HDFS encryption...

Re: HDFS file and block size