The attached image just has thread states, and WAITING threads need not be the issue. We need to take thread stack traces and identify at which area of code, threads are spending lot of time.
Use jstack -l <pid> or kill -3 <pid>, where pid is the process id of the executor process. Take jstack stack trace for every 2 seconds and total 1 minute. This will help to identify the code where threads are spending lot of time and then try to tune. Thanks, Prabhu Joseph On Sat, Jan 2, 2016 at 1:28 PM, Umesh Kacha <[email protected]> wrote: > Hi thanks I did that and I have attached thread dump images. That was the > intention of my question asking for help to identify which waiting thread > is culprit. > > Regards, > Umesh > > On Sat, Jan 2, 2016 at 8:38 AM, Prabhu Joseph <[email protected]> > wrote: > >> Take thread dump of Executor process several times in a short time period >> and check what each threads are doing at different times which will help to >> identify the expensive sections in user code. >> >> Thanks, >> Prabhu Joseph >> >> On Sat, Jan 2, 2016 at 3:28 AM, unk1102 <[email protected]> wrote: >> >>> Sorry please see attached waiting thread log >>> >>> < >>> http://apache-spark-user-list.1001560.n3.nabble.com/file/n25851/Screen_Shot_2016-01-02_at_2.jpg >>> > >>> < >>> http://apache-spark-user-list.1001560.n3.nabble.com/file/n25851/Screen_Shot_2016-01-02_at_2.jpg >>> > >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-spark-user-list.1001560.n3.nabble.com/How-to-find-cause-waiting-threads-etc-of-hanging-job-for-7-hours-tp25850p25851.html >>> Sent from the Apache Spark User List mailing list archive at Nabble.com. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >
