Hmmm... could you try to set the log dir to "file:/home/hduser/spark/spark-events"?
I checked the code and it might be the case that the behaviour changed between 1.2 and 1.3... On Mon, Mar 30, 2015 at 6:44 PM, Tom Hubregtsen <thubregt...@gmail.com> wrote: > The stack trace for the first scenario and your suggested improvement is > similar, with as only difference the first line (Sorry for not including > this): > "Log directory /home/hduser/spark/spark-events does not exist." > > To verify your premises, I cd'ed into the directory by copy pasting the path > listed in the error message (i, ii), created a text file, closed it an > viewed it, and deleted it (iii). My findings were reconfirmed by my > colleague. Any other ideas? > > Thanks, > > Tom > > > On 30 March 2015 at 19:19, Marcelo Vanzin <van...@cloudera.com> wrote: >> >> So, the error below is still showing the invalid configuration. >> >> You mentioned in the other e-mails that you also changed the >> configuration, and that the directory really, really exists. Given the >> exception below, the only ways you'd get the error with a valid >> configuration would be if (i) the directory didn't exist, (ii) it >> existed but the user could not navigate to it or (iii) it existed but >> was not actually a directory. >> >> So please double-check all that. >> >> On Mon, Mar 30, 2015 at 5:11 PM, Tom Hubregtsen <thubregt...@gmail.com> >> wrote: >> > Stack trace: >> > 15/03/30 17:37:30 INFO storage.BlockManagerMaster: Registered >> > BlockManager >> > Exception in thread "main" java.lang.IllegalArgumentException: Log >> > directory >> > ~/spark/spark-events does not exist. >> >> >> -- >> Marcelo > > -- Marcelo --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
