About jagadeesan

jagadeesan · ‎12-25-2018

Please can you attach full error logs to debug further, if issue persist..

jagadeesan · ‎12-25-2018

As mentioned in the article, did you modified KMS URL in Ambari and removed tailing "/' ? which resolved your issue or still facing same..?

jagadeesan · ‎12-24-2018

@Sundara Palanki Please can you check below article, seems you are facing similar issue. https://community.hortonworks.com/content/supportkb/150691/yarn-failed-to-renew-token-kind-timeline-delegatio.html

jagadeesan · ‎12-06-2018

@Junfeng Chen That's true, above property for local filesystem. For hdfs could you try to use Append instead of Overwrite ? But problem in this, we need to delete files manually from the temp directory.

jagadeesan · ‎12-06-2018

@Junfeng Chen You can change the path to the temp folder for each Spark application by spark.local.dir property like below SparkConf conf = new SparkConf().setMaster("local”).setAppName("test”).set("spark.local.dir", "/tmp/spark-temp"); Reference Please accept the answer you found most useful

jagadeesan · ‎12-04-2018

Please can you try to run below command, hdp-select sets a given version to be the current version, by creating appropriate symlinks to the folder with appropriate version number. hdp-select status | grep -i hdfs

jagadeesan · ‎12-04-2018

I can suggest, for 20 kafka machines you can go with 3 zookeeper servers

jagadeesan · ‎12-04-2018

@Michael Bronson Zookeeper servers are tolerates the servers down. But yes it's always recommendable if you are in the planning for scaling the cluster go with more resources and robust hardwares. It’s completely perfect to move the Zookeeper servers from VM machines to physical machines with more resources.

jagadeesan · ‎12-04-2018

@Michael Bronson In normal small deployment using 3 zookeeper servers is acceptable, but keep in mind that you will only be able to tolerate 1 server down in this case. If you have a ZooKeeper ensemble has 5 or 7 servers, which tolerates 2 and 3 servers down, respectively. I hope this answers your question. Reference: https://kafka.apache.org/documentation/#zk

jagadeesan · ‎12-04-2018

@Michael Bronson This is the harmless message you can ignore it. which will be addressed in 2.3.0 version of ambari. Please see:https://issues.apache.org/jira/browse/AMBARI-12420 The DataNode code has been changed in 2.3.0 Ambari so that it would stop logging the EOFException if a client connected to the data transfer port and immediately closed before sending any data. Link

Online	Offline
Last Visited	‎10-03-2025 07:58 AM

Member Since	‎11-12-2018 10:00 AM
Last Visited	‎10-03-2025 07:58 AM
Posts	218
Kudos received	179

Cloudera Community

Re: Migrating workloads from Spark 2 to Spark 3

Re: Looking for a supported version of Spark 3 for...

Re: Spark 3 Parcel Compatibility with CDP Private ...

Re: Apache Storm support in Cloudera

Re: Complete example for using spark MLlib for twi...

Re: distcp Job fails with delegation token renewal...

Re: distcp Job fails with delegation token renewal...

Re: distcp Job fails with delegation token renewal...

Re: How to change Spark _temporary directory when ...

Re: How to change Spark _temporary directory when ...

Re: ERROR datanode.DataNode + error processing WRI...

Re: datanode machine + how many datanode we can ad...

Re: datanode machine + how many datanode we can ad...

Re: datanode machine + how many datanode we can ad...

Re: ERROR datanode.DataNode + error processing WRI...