Github user WeichenXu123 commented on the pull request:
https://github.com/apache/spark/pull/12978#issuecomment-220021066
In order to check this potential problem more carefully, We can add the
following test code like this:
`
echo "$newpid" > "$pid"
**for i in {1..30};do
echo "check daemon stage $i" `ps -p "$newpid" -o comm=`
sleep 0.1
done**
sleep 2
# Check if the process has died; in that case we'll tail the log so the
user can see
if [[ ! $(ps -p "$newpid" -o comm=) =~ "java" ]]; then
echo "failed to launch $command:"
tail -2 "$log" | sed 's/^/ /'
echo "full log in $log"
fi
`
then run the start daemon script it will print such as:
sbin/start-master.sh
starting org.apache.spark.deploy.master.Master, logging to
/diskext/mySpark/spark/logs/spark-root-org.apache.spark.deploy.master.Master-1-n131.out
check daemon stage 1 bash
check daemon stage 2 bash
check daemon stage 3 bash
check daemon stage 4 bash
check daemon stage 5 java
check daemon stage 6 java
check daemon stage 7 java
check daemon stage 8 java
....
The running result show that the bash status daemon will exist for sometime.
Especially when the machine just startup and OS cache is clean, the time
may exceed 2s.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
