First Production Level Parallel Programming Output [Code Accepted]

We get the first time for everything. This is the first time of production level parallel programming. This is a simple setup: a parent and a thread. Child thread has a timeout limit, though the parent is willing to wait indefinitely. So, it becomes the responsibility of the child to inform the parent to move on when it's done/cannot be done.

21-01-29 11:24:20,007:: pace.neapi.operations:504: DcoLogHandler: resumption will take max 900 seconds 2021-01-29 11:24:25,021:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:24:28,968:: pace.neapi.operations:446: DcoLogHandler: resume signal received from parent-thread 2021-01-29 11:24:28,968:: pace.neapi.operations:452: DcoLogHandler: attempt 1 to re-establish ssh connection to 10.100.58.178 2021-01-29 11:24:30,028:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:24:35,038:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:24:40,039:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:24:45,054:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:24:50,060:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:24:55,069:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:24:58,982:: pace.neapi.operations:258: DcoLogHandler: ssh connection to 10.100.58.178 is not alive 2021-01-29 11:24:58,983:: pace.neapi.operations:258: DcoLogHandler: ssh connection to 10.100.58.178 is not alive 2021-01-29 11:25:00,082:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:25:00,938:: pace.neapi.operations:212: DcoLogHandler: ssh connection established to 10.100.58.178, port = 63854 2021-01-29 11:25:02,328:: pace.neapi.operations:236: DcoLogHandler: interactive SSH session to 10.100.58.178 established 2021-01-29 11:25:02,329:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:04,346:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:05,088:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:25:06,348:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:08,358:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:10,088:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:25:10,363:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:12,367:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:14,369:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:15,091:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:25:16,382:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:18,387:: pace.neapi.operations:155: DcoLogHandler: waiting for channel to be receive ready 2021-01-29 11:25:20,099:: pace.neapi.operations:512: DcoLogHandler: main thread waiting 5 seconds for DcoLogHandler to resume completion 2021-01-29 11:25:25,107:: pace.neapi.operations:515: DcoLogHandler is resumed. Parent thread continues.

Comments

Post a Comment

Popular posts from this blog

First time interviewer

 Today, I got an invitation to interview a candidate. This is the first time, I will really be interviewing someone. The candidate has applied via a recruitment agency. Along with his resume, there was a package of his recommendations as well, and I made the grave mistake of looking at the references too quickly. These recommendations are not negative but neither are they positive. I have been there. I decided to focus on his work. I must say, it could have been honest. The issue is that his resume was repetitive, it could have been written on a single page. With all humility, all of us have lots of tasks and we could not read through the whole content. Besides, I could not find any specific domain knowledge. But, I have been there too. I will judge his skill based on what he knows, instead. That's how I will mostly interview. Advice for interviewees: 1. KISS - Keep it short and simple. 2. Use keywords. 3. Know whom to ask for a reference. 4. If you work every day with the same ded...
Read more

Backstory of Software {LOL} Engineer

I am also one of the typical software engineers that you see churning out of engineering colleges in India. I am also one of them, very average yet not complaining about it. We are fine. Took a gap of three years after higher secondary, and then did computer science in some private engineering college. No, I didn't get a job in the campus, I was not even eligible for any company in the campus- they wanted first division throughout, and I have a second division in higher secondary. Anyway, going forward, went to Hyderabad after the bachelor and after 6 months, I got a job. Those six months were one of the worst periods of life, I was tired of running after every interview. Imagine, traveling in the general coaches of Indian Railway for full one-two journeys just for one single interview in another state thousand miles away. This was mostly very frustrating because I used to clear all rounds of technical rounds and then get rejected in the HR round. The second division came back haun...
Read more