The UI code is the same in both, but one possibility is that your executors were given less memory on YARN. Can you check that? Or otherwise, how do you know that some RDDs were cached?
Matei On Jul 12, 2014, at 4:12 PM, Koert Kuipers <ko...@tresata.com> wrote: > hey shuo, > so far all stage links work fine for me. > > i did some more testing, and it seems kind of random what shows up on the gui > and what does not. some partially cached RDDs make it to the GUI, while some > fully cached ones do not. I have not been able to detect a pattern. > > is the codebase for the gui different in standalone than in yarn-client mode? > > > On Sat, Jul 12, 2014 at 3:34 AM, Shuo Xiang <shuoxiang...@gmail.com> wrote: > Hi Koert, > Just curious did you find any information like "CANNOT FIND ADDRESS" after > clicking into some stage? I've seen similar problems due to lost of executors. > > Best, > > > > On Fri, Jul 11, 2014 at 4:42 PM, Koert Kuipers <ko...@tresata.com> wrote: > I just tested a long lived application (that we normally run in standalone > mode) on yarn in client mode. > > it looks to me like cached rdds are missing in the storage tap of the ui. > > accessing the rdd storage information via the spark context shows rdds as > fully cached but they are missing on storage page. > > spark 1.0.0 > > >
