Re: How to shutdown cluster in non-interactive mode using gfsh
Hello Avinash,
What Geode version are you referring to?.
I've just tried a simple scenario with Geode 1.12.0 and the command works
just fine, even when using non-interactive mode.
You can see the output from in the image below, when I try to shutdown the
cluster within the interactive mode gfsh asks for confirmation but, right
afterwards when I execute the command in non-interactive mode ("-e"), no
confirmation is displayed and the cluster correctly shuts down.
[image: Screenshot 2020-08-31 at 09.24.22.jpg]
Hope this helps.
Best regards.
On Mon, 31 Aug 2020 at 05:15, Avinash Dongre wrote:
> When I try using gfsh I get following
>
> gfsh>shutdown --include-locators=yes --time-out=5
> As a lot of data in memory will be lost, including possibly events in
> queues, do you really want to shutdown the entire distributed system?
> (Y/n): n
>
> And command line version hangs, probably waiting for input
>
> bin/gfsh -e "connect" -e "shutdown --include-locators=yes"
>
> Any clue how I can bypass this
>
> Thanks
> Avinash
>
--
Ju@N
Proposal to bring GEODE-8456 (shiro upgrade) to support branches
Recently shiro-1.5.3.jar is getting flagged for ‘high’ security vulnerability CVE-2020-13933. Analysis shows that Geode does not use Shiro in a manner that would expose this vulnerability. The risk of bringing GEODE-8456 is low (difference between Shiro 1.5.3 and 1.6.0 is bugfix and dependency bump only). GEODE-8456 has been on develop for 6 days and passed all tests. This fix is critical to avoid false positives in automated vulnerability scans. It would be nice to bring to support branches before 1.13.0 is released. Please vote “+1” to approve including this in 1.13.0. If there are any -1 votes, I’ll wait until after 1.13.0 is done to propose this again.
Re: Proposal to bring GEODE-8456 (shiro upgrade) to support branches
+1 We still have outstanding release blockers for 1.13, so getting this fix in now just prevents extra work in the future without slowing us down now. From: Owen Nichols Sent: Monday, August 31, 2020 4:19 PM To: dev@geode.apache.org Subject: Proposal to bring GEODE-8456 (shiro upgrade) to support branches Recently shiro-1.5.3.jar is getting flagged for ‘high’ security vulnerability CVE-2020-13933. Analysis shows that Geode does not use Shiro in a manner that would expose this vulnerability. The risk of bringing GEODE-8456 is low (difference between Shiro 1.5.3 and 1.6.0 is bugfix and dependency bump only). GEODE-8456 has been on develop for 6 days and passed all tests. This fix is critical to avoid false positives in automated vulnerability scans. It would be nice to bring to support branches before 1.13.0 is released. Please vote “+1” to approve including this in 1.13.0. If there are any -1 votes, I’ll wait until after 1.13.0 is done to propose this again.
