Re: Bizarre UI Behavior after migration

Was checking mails I sent, and wanted to get back to this one in case someone gets the same question. We found out that the reason why we saw stages being complete without all tasks complete is related to issues in the ListenerBus We had to tune the event queue size, see this

Re: Bizarre UI Behavior after migration

Well, what's happening here is that jobs become "un-finished" - they complete, and then later on pop back into the "Active" section showing a small number of complete/inprogress tasks. In my screenshot, Job #1 completed as normal, and then later on switched back to active with only 92 tasks... it

Re: Bizarre UI Behavior after migration

I believe it shows only the tasks that have actually being executed, if there were tasks with no data, they don't get reported. I might be mistaken, if somebody has a good explanation, would also like to hear. On Fri, May 19, 2017 at 5:45 PM, Miles Crawford wrote: > Hey

Bizarre UI Behavior after migration

Hey ya'll, Trying to migrate from Spark 1.6.1 to 2.1.0. I use EMR, and launched a new cluster using EMR 5.5, which runs spark 2.1.0. I updated my dependencies, and fixed a few API changes related to accumulators, and presto! my application was running on the new cluster. But the application UI