> On Oct. 5, 2018, 2:34 a.m., Velmurugan Periasamy wrote:
> > tagsync/scripts/ranger-tagsync-services.sh
> > Lines 124 (patched)
> > <https://reviews.apache.org/r/68908/diff/1/?file=2094015#file2094015line124>
> >
> >     Can you please make sure this is merged in ranger-1 line branches?

Yes Vel, patch is applying on ranger-1 line branches.


- bhavik


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


On Oct. 3, 2018, 6:43 a.m., bhavik patel wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/68908/
> -----------------------------------------------------------
> 
> (Updated Oct. 3, 2018, 6:43 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan 
> Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2229
>     https://issues.apache.org/jira/browse/RANGER-2229
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> In ranger usersync and tagsync scripts, stop of the process is done 
> forcefully using kill -9.
> Suggestion is to do a graceful shutdown with retries and do a force kill only 
> if graceful shutdown is not successful.
> 
> Stop section from ranger-tagsync-services.sh and ranger-tusersync-services.sh
> 
> 
> Diffs
> -----
> 
>   tagsync/scripts/ranger-tagsync-services.sh 5686390 
>   unixauthservice/scripts/ranger-usersync-services.sh 028ad08 
> 
> 
> Diff: https://reviews.apache.org/r/68908/diff/1/
> 
> 
> Testing
> -------
> 
> Tested ranger usersync & ranger tagsync are getting shutdown gracefully, also 
> verified if graceful shutdown is not successful(after 15 retries) than it 
> used kill -9 to stopped the proccess forcefully.
> 
> 
> Thanks,
> 
> bhavik patel
> 
>

Reply via email to