[DISCUSS] `status locator` command fail when locator's ssl is turned on

[Jinmei Liao]

"status locator" command is broken on ssl enabled locators ever since we
fixed a bug that leaked the connection properties from one tcp socket
connection to another. Before that it would just magically work if we have
previously made a successfully tcp connection to that same locator, now we
are either required to find a way to specify the ssl properties when
running the `status locator` command or change what we want to report back
to the user.

Here is what's happening now when we issue the command:

   1. it needs to retrieve two sets of info from locator: general info like
   (pid, working dir, status, jvm args etc) and whether cluster configuration
   service is running or not.
   2. when locator’s ssl is on, the retrieval of the cluster configuration
   info will always fail since it’s using a tcp connection to get that info
   and we currently don’t have the ssl security properties to connect.
   3. when locator’s ssl is on, the retrieval of the general info will
   mostly succeed except when user is only providing a host and port, there we
   would also need the ssl security properties in order to create an ssl
   socket.


So we wither need to add an option for user to specify a
`--security-properties-file` option to include all the ssl connection
properties or change the behavior not to report cluster config status or
not allowing host/port combination. (I am not here long enough to
understand what users would use this command for, so this is just a random
suggestions).

Comments/thoughts?

-- 
Cheers

Jinmei

Inclusion of GEODE-7531 and GEODE-7159 into 1.11

[Udo Kohlmeyer]

Hi there Release manager for the 1.11 release.

Please could you include

GEODE-7531, SHA: f5b59350cc1b4580154df047f409a6c7a4095f0b

and

GEODE-7159, SHA: 0f05e9ccd94c04a205ace82de6616e9bffa92fa7

into 1.11.

Regards

Udo

Re: Review for #4387

[Aaron Lindsey]

I added a review, but mostly from a code cleanliness and testing perspective. I 
hope someone with more knowledge of the use case and WAN can provide their 
feedback.

- Aaron

> On Dec 16, 2019, at 1:14 AM, Mario Ivanac  wrote:
> 
> Hi all,
> 
> please could someone review https://issues.apache.org/jira/browse/GEODE-7458
> [GEODE-7458] Adding additional option in gfsh command "start gateway sender" 
> to control clearing of existing queues - ASF 
> JIRA
> This Jira has been LDAP enabled, if you are an ASF Committer, please use your 
> LDAP Credentials to login. Any problems email us...@infra.apache.org
> issues.apache.org
> PR https://github.com/apache/geode/pull/4387
> 
> 
> Thanks,
> Mario

[DISCUSS] Support for clear operation on partitioned region

[Xiaojian Zhou]

Hi,

We wrote up a proposal for clear operation on Partitioned Region.
Please review and comment on the below proposal.

https://cwiki.apache.org/confluence/display/GEODE/Support+for+clear+operation+on+partitioned+region

Customers have been looking for this feature for a long time. So far we
only support clear on Distributed Region. But most of the customers are
using Partitioned Region nowadays.

Please put your comments in RFC directly instead of on the email thread.
Thank you.

Regards
Xiaojian Zhou (Gester)