Member since
05-22-2018
40
Posts
0
Kudos Received
0
Solutions
05-07-2019
11:38 AM
please check below article: https://antnix07.blogspot.com/2017/05/normal-0-false-false-false-en-us-x-none.html
... View more
09-04-2018
05:26 AM
Also, I can see that I have over 100 connections on the port as of now.Where can I take the limit off from for the allowed number of connections?
... View more
06-11-2018
03:21 PM
Hey @Simran kaur! Could you check if you're able to connect to all zk ports? And what about your datadir property (inside /etc/zookeeper/conf/zoo.cfg), could you check your permissions there? clientPort=2181
initLimit=10
autopurge.purgeInterval=24
syncLimit=5
tickTime=3000
dataDir=/hadoop/zookeeper
autopurge.snapRetainCount=30
server.1=mynode1:2888:3888
server.2=mynode2:2888:3888
server.3=mynode3:2888:3888 Hope this helps!
... View more
06-06-2018
08:53 PM
Hey @Simran kaur AFAIK, usually 137 code represents issues with resources. It seems that Yarn wasn't able to get more resources. Could you share your yarn resources parameters? Or if you prefer, you can take a look at this link: https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.1/bk_command-line-installation/content/determine-hdp-memory-config.html Hope this helps! 🙂
... View more
03-24-2019
02:06 PM
Hi Harald, I facing the same issue with spark jobs where executors are getting killed with exit status 137. Please let me know what can be the probable cause of it. I can't find any Kill mesg in dmesg.
... View more