0

i launched a pig process over a folder of 71 GB in putty . after 45 minutes,the putty session gives "software connection abort" and then on job tracker the pig job status is "killed".

I tried increasing the session timeout of putty(Seconds between keppalives:1800),but no help.

Please suggest if i am going in right direction and that my concern regarding session timeout affecting pig job is correct or not.

also is there any other way to launch pig job apart from putty. I have cloudera on a 8 node cluster.

aurelius
  • 3,946
  • 7
  • 40
  • 73
user3548020
  • 1
  • 3
  • Try using nohup as described at http://stackoverflow.com/questions/15595374/whats-the-difference-between-nohup-and-ampersand – mc110 May 29 '14 at 11:54
  • This problem is not specific to Pig, so I am removing the tag. This affects any process which is terminated when the parent shell is killed. Pig is one such process. – reo katoa May 29 '14 at 16:41

1 Answers1

0

You should use the Shell command "screen". So you could now even shutdown your computer then reconnect to the distant computer and use screen -r in order to find the id of the screen in which you started your pig :)

Samoht-Sann
  • 256
  • 1
  • 8