Member since
02-08-2016
793
Posts
669
Kudos Received
85
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3066 | 06-30-2017 05:30 PM | |
3985 | 06-30-2017 02:57 PM | |
3307 | 05-30-2017 07:00 AM | |
3884 | 01-20-2017 10:18 AM | |
8399 | 01-11-2017 02:11 PM |
08-14-2018
08:42 PM
Hi Team , Is there any way to test multiple files exist or not in single command?? like below.. pls suggest hadoop fs -test -e filename1 filename2
... View more
07-27-2016
11:23 PM
Good catch! I'm glad you took the time to write up your findings for others to learn.
... View more
07-05-2016
07:17 AM
Hi, After changing to Oregon, it worked. Thank you all for your help. Regards, Sathish G.
... View more
07-02-2016
02:32 PM
user name will be "admin" before this you need to reset the password form command line using : ambari-admin-password-reset
... View more
01-03-2017
02:50 PM
Added, thanks for the suggestion.
... View more
06-29-2016
11:46 AM
@nejm hadjmbarek, in the information you provided, it seems your oozie max concurrency has been reached for the coordinator. You therefore have a number of applications waiting AM resources. Check you max AM resource percentage in capacity scheduler and consider raising it to either .5 or .6 which states that of the total resources, RM can assign our 50 or 60 percent to AM containers.
... View more
06-27-2016
11:07 AM
3 Kudos
@Sagar Shimpi Oozie has feature to purge older jobs from database. by default it's 30 days. Actions related to long running coordinators do not purged until co-ordinator completes, ( example - if you have coordinator running for 6 months, then all the related workflows will be there in database for 6 months ) Will the purge scripts remove the running workflows and coordinators? Ans - No it will not. Below are the respective properties and their default values. Useful link - http://stackoverflow.com/questions/31946225/oozie-not-cleaning-up-old-jobs-from-oozie-database oozie.service.PurgeService.older.than 30 Completed workflow jobs older than this value, in days, will be purged by the PurgeService. oozie.service.PurgeService.coord.older.than 7 Completed coordinator jobs older than this value, in days, will be purged by the PurgeService. oozie.service.PurgeService.bundle.older.than 7 Completed bundle jobs older than this value, in days, will be purged by the PurgeService. oozie.service.PurgeService.purge.old.coord.action false Whether to purge completed workflows and their corresponding coordinator actions of long running coordinator jobs if the completed workflow jobs are older than the value specified in oozie.service.PurgeService.older.than. oozie.service.PurgeService.purge.limit 100 Completed Actions purge - limit each purge to this value oozie.service.PurgeService.purge.interval 3600 Interval at which the purge service will run, in seconds.
... View more
12-22-2017
04:55 AM
i did same thing on HDP2.5 but still showing below error 534-5.7.14 IvciS8yws8APKDFHijkrFoJ92wCiJPAO_hwu5n84JrRGIqSyumJ05MoXUq94ogjYKFwfS5
534-5.7.14 iP5EQUiY-JheLLz82D33Qp2yF8wuQkoQ6BAwjeCpThA9GoTte7WBFbZnRByREw7MnpQ3Am
534-5.7.14 qRMD4_bLAgQqiJIzCgxU1ppqCt9qc> Please log in via your web browser and
534-5.7.14 then try again.
534-5.7.14 Learn more at
534 5.7.14 https://support.google.com/mail/answer/78754 e8sm22695829pga.72 - gsmtp
at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:892)
at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:814)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:728)
at javax.mail.Service.connect(Service.java:386)
at javax.mail.Service.connect(Service.java:245)
at javax.mail.Service.connect(Service.java:194)
at javax.mail.Transport.send0(Transport.java:253)
at javax.mail.Transport.send(Transport.java:124)
at org.apache.ambari.server.notifications.dispatchers.EmailDispatcher.dispatch(EmailDispatcher.java:160)
at org.apache.ambari.server.notifications.DispatchRunnable.run(DispatchRunnable.java:58)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
... View more
06-14-2016
03:49 PM
Thanks for the update.
... View more