Similarly, I am seeing tasks moved to the completed section which
apparently haven't finished all elements... (succeeded/total 1)... is this
related?
--
View this message in context:
Seems like it is related. Possibly those PRs that Andrew mentioned are
going to fix this issue.
On Fri, Jul 11, 2014 at 5:51 AM, Haopu Wang hw...@qilinsoft.com wrote:
I saw some exceptions like this in driver log. Can you shed some
lights? Is it related with the behaviour?
14/07/11
I saw some exceptions like this in driver log. Can you shed some lights? Is it
related with the behaviour?
14/07/11 20:40:09 ERROR LiveListenerBus: Listener JobProgressListener threw an
exception
java.util.NoSuchElementException: key not found: 64019
at
Do you see any errors in the logs of the driver?
On Thu, Jul 10, 2014 at 1:21 AM, Haopu Wang hw...@qilinsoft.com wrote:
I'm running an App for hours in a standalone cluster. From the data
injector and Streaming tab of web ui, it's running well.
However, I see quite a lot of Active stages in
History Server is also very helpful.
On Thu, Jul 10, 2014 at 7:37 AM, Haopu Wang hw...@qilinsoft.com wrote:
I didn't keep the driver's log. It's a lesson.
I will try to run it again to see if it happens again.
--
*From:* Tathagata Das
One thing to keep in mind is that the progress bar doesn't take into
account tasks which are rerun. If you see 4/4 but the stage is still
active, click the stage name and look at the task list. That will show you
if any are actually running. When rerun tasks complete, it can result in
the number
Yes, there are a few bugs in the UI in the event of a node failure.
The duplicated stages in both the active and completed tables should be
fixed by this PR: https://github.com/apache/spark/pull/1262
The fact that the progress bar on the stages page displays an overflow
(e.g. 5/4) is still an
