group). Therefore, this can't read my job event logs as shown above.
>>>
>>>
>>> Thanks,
>>> Michael
>>>
>>>
>>> -Original Message-
>>> From: Marcelo Vanzin [mailto:van...@cloudera.com]
>>> Se
this can't read my job event logs as shown above.
>>>
>>>
>>> Thanks,
>>> Michael
>>>
>>>
>>> -Original Message-
>>> From: Marcelo Vanzin [mailto:van...@cloudera.com]
>>> Sent: 07 January 2015 18:10
mapr
>> group). Therefore, this can't read my job event logs as shown above.
>>
>>
>> Thanks,
>> Michael
>>
>>
>> -Original Message-
>> From: Marcelo Vanzin [mailto:van...@cloudera.com]
>> Sent: 07 January 2015 18:10
>>
udera.com]
> Sent: 07 January 2015 18:10
> To: England, Michael (IT/UK)
> Cc: user@spark.apache.org
> Subject: Re: Spark History Server can't read event logs
>
> The Spark code generates the log directory with "770" permissions. On top of
> that you need to make sure of t
IT/UK)
Cc: user@spark.apache.org
Subject: Re: Spark History Server can't read event logs
The Spark code generates the log directory with "770" permissions. On top of
that you need to make sure of two things:
- all directories up to /apps/spark/historyserver/logs/ are readable by t
The Spark code generates the log directory with "770" permissions. On
top of that you need to make sure of two things:
- all directories up to /apps/spark/historyserver/logs/ are readable
by the user running the history server
- the user running the history server belongs to the group that owns
/a
