Updating the SharLib Worked! =D I did have to bounce oozie before it fixed it but this solution works. ... View more

Hi,   Your reply does help. Thanks.   But I still have doubts regarding passing parameters via Hue UI. 1.If I pass the parameter value using the Properties field, then will it be updated in the workflow under <agr> tag or <property> tag? 2. What is the use of Parameter field under Workflow Settings.   Also could you please give some insight regarding my use-case: I want to run the java mapreduce program using mapreduce action. I have a jar with multiple Mapper and Reducer Class defined and I want to use Oozie as driver for my Mapper and Reducer programs. And at the same time passing argument values through Oozie to my Mappers and Reducers.   How can I achieve this using Hue UI to create and workflow? ... View more

Thanks for the explanation. And thanks for tolerating me extending the original question.  This issue can be closed. ... View more

You can use the CM -> HBase -> Configuration -> RegionServer Safety Valve (for hbase-site.xml) to make the HFile V3 property setting change, since there's no direct UI field for it. CM does separate client configs from server ones, to isolate and configure server specific items independently. This is better explained in the architecture docs at http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_intro_primer.html ... View more

Glad to hear - thanks for closing the loop! ... View more

You (or your used software) appear to be using appends on files that are being modified in parallel by other concurrent jobs/workflows/etc.. HDFS uses a single-writer model for its files, so observing this error is normal if your software does not have logic handling it and waiting for a proper writer lease to perform its work. Without audit logs of the filenames involved, there's little more we can tell. We also advise against using appends unless you absolutely require it for your use-cases. ... View more

Had similar issue got resolved Error ------ I had like this in workflow.xml <job-tracker>localhost:8032</job-tracker> <name-node>localhost:8020</name-node> Changed it to the following <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> ... View more

Lowering the params didn't work for me. Is there any other information I can verify?   -Shankar ... View more