> On Jan. 19, 2017, 4:59 a.m., Bikas Saha wrote:
> > Should the URL for recovery be something like 
> > /apps/{livy|spark}/livy-recovery? Having /livy-recovery as a top level HDFS 
> > dir seems distracting.
> 
> Saisai Shao wrote:
>     It will not be in the top level HDFS dirs. It will be in User livy's 
> current home directory, which is "/user/livy/livy-recovery".
> 
> Bikas Saha wrote:
>     My suggestion would be to change that to /apps/spark where such system 
> data tends to go for other apps. That would be the convention. What do the 
> Ambari folks think? Of course my understanding of existing convention might 
> be wrong :) In which case /user/livy/ is also ok.

Bikas, there's no /apps/spark, and it actually is 
"/hdp/apps/2.6.0.0-389/spark", which is hdp version specific. So I will follow 
what spark history did "/spark-history", to create "/livy-recovery" and 
"/livy2-recovery".


- Saisai


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/55609/#review162240
-----------------------------------------------------------


On Jan. 18, 2017, 2:25 a.m., Saisai Shao wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55609/
> -----------------------------------------------------------
> 
> (Updated Jan. 18, 2017, 2:25 a.m.)
> 
> 
> Review request for Ambari, Jayush Luniya and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-19577
>     https://issues.apache.org/jira/browse/AMBARI-19577
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> Add Livy session recovery configurations in Ambari
> 
> 
> Diffs
> -----
> 
>   
> ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK/configuration/livy-conf.xml
>  b7bfa73 
>   
> ambari-server/src/main/resources/stacks/HDP/2.6/services/SPARK2/configuration/livy2-conf.xml
>  457869d 
> 
> Diff: https://reviews.apache.org/r/55609/diff/
> 
> 
> Testing
> -------
> 
> Manual verification.
> 
> 
> Thanks,
> 
> Saisai Shao
> 
>

Reply via email to