WAN replication issue in cloud native environments

[Alberto Bustamante Reyes]

Hi all,

We have a problem with Geode WAN replication when GW receivers are configured 
with the same hostname-for-senders and port on all servers.

The reason for such a setup is deploying Geode cluster on a Kubernetes cluster 
where all GW receivers are reachable from the outside world on the same VIP and 
port.

Other kinds of configuration (different hostname and/or different port for each 
GW receiver) are not cheap from OAM and resources perspective in cloud native 
environments and also limit some important use-cases (like scaling).

The problem experienced is that shutting down one server is stopping 
replication to this cluster until the server is up again. We suspect this is 
because Geode incorrectly assumes there are no more alive servers when just one 
of them is down (since they share hostname-for-senders and port).

Has anyone experienced a similar problem configuring Geode WAN replication in 
cloud native environments?

Thinking about possible solutions in Geode code, our proposal would be to 
expand internal data in locators with enough information to distinguish servers 
in the beforementioned use case. The same intervention is likely needed in the 
client pools and possibly elsewhere in the source code. Any comments about this 
proposal is welcome.

Thanks in advance!

Alberto B.

Reviewers wanted for GEODE-7509: Fix memory leaks in C++ client

[Alberto Gomez]

Hi,

Could I get some reviewers for https://github.com/apache/geode-native/pull/556?
[https://avatars3.githubusercontent.com/u/47359?s=400&v=4]
GEODE-7509: Fix memory leaks in C++ client by albertogpz · Pull Request #556 · 
apache/geode-native
This commit solves some more memory leaks and uninitialized memory accesses 
found in the C++ client when running the integration tests that were not solved 
by GEODE-7476
github.com


Thanks in advance,

/Alberto G.

Re: WAN replication issue in cloud native environments

[Jacob Barrett]

> On Nov 29, 2019, at 3:14 AM, Alberto Bustamante Reyes 
>  wrote:
> 
> The reason for such a setup is deploying Geode cluster on a Kubernetes 
> cluster where all GW receivers are reachable from the outside world on the 
> same VIP and port.

Are you using LoadBalancer Service type?

> Other kinds of configuration (different hostname and/or different port for 
> each GW receiver) are not cheap from OAM and resources perspective in cloud 
> native environments and also limit some important use-cases (like scaling).

If you could somehow configure host and port for sender (code modification 
required) would exposing each port through the LoadBalancer be too expensive 
too?

> The problem experienced is that shutting down one server is stopping 
> replication to this cluster until the server is up again. We suspect this is 
> because Geode incorrectly assumes there are no more alive servers when just 
> one of them is down (since they share hostname-for-senders and port).

Sees like at the worst case when it tries to reconnect the LB should give it a 
live server and it think the single server is back up.

-Jake

IndexType deprecation question

[Joris Melchior]

Hi All,

I notice that the ENUM

org.apache.geode.cache.query.IndexType has been deprecated but can't
find what to use instead of this ENUM if I wanted to use a
non-deprecated alternative.

I understand that HASH indexes are no longer recommended but the other
types (PRIMARY_KEY, FUNCTIONAL) are still valid and I believe we
should be able to use them without using deprecated code.

Can anyone tell me how this is accomplished?

Thanks, Joris.


-- 
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427

“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*

Re: IndexType deprecation question

[John Blum]

FYI... if you are using *Spring Data for Apache Geode* (SDG;
spring-data-geode), then there is an SDG Index enum type

[1]
wrapping the deprecated Apache Geode Index enum type

 [2].



[1]
https://docs.spring.io/spring-data/geode/docs/current/api/org/springframework/data/gemfire/IndexType.html
[2]
https://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/query/IndexType.html


On Fri, Nov 29, 2019 at 8:17 AM Joris Melchior  wrote:

> Hi All,
>
> I notice that the ENUM
>
> org.apache.geode.cache.query.IndexType has been deprecated but can't
> find what to use instead of this ENUM if I wanted to use a
> non-deprecated alternative.
>
> I understand that HASH indexes are no longer recommended but the other
> types (PRIMARY_KEY, FUNCTIONAL) are still valid and I believe we
> should be able to use them without using deprecated code.
>
> Can anyone tell me how this is accomplished?
>
> Thanks, Joris.
>
>
> --
> *Joris Melchior *
> CF Engineering
> Pivotal Toronto
> 416 877 5427
>
> “Programs must be written for people to read, and only incidentally for
> machines to execute.” – *Hal Abelson*
> 
>


-- 
-John
john.blum10101 (skype)

Re: IndexType deprecation question

[Joris Melchior]

Thanks John.

I'm trying to use it on the server side for the management API so
unfortunately the Spring wrapper is not an option. Hopefully someone can
provide some insight into the deprecation background once all the turkey
and stuffing has been digested.

On Fri, Nov 29, 2019 at 2:16 PM John Blum  wrote:

> FYI... if you are using *Spring Data for Apache Geode* (SDG;
> spring-data-geode), then there is an SDG Index enum type
> <
> https://docs.spring.io/spring-data/geode/docs/current/api/org/springframework/data/gemfire/IndexType.html
> >
> [1]
> wrapping the deprecated Apache Geode Index enum type
> <
> https://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/query/IndexType.html
> >
>  [2].
>
>
>
> [1]
>
> https://docs.spring.io/spring-data/geode/docs/current/api/org/springframework/data/gemfire/IndexType.html
> [2]
>
> https://geode.apache.org/releases/latest/javadoc/org/apache/geode/cache/query/IndexType.html
>
>
> On Fri, Nov 29, 2019 at 8:17 AM Joris Melchior 
> wrote:
>
> > Hi All,
> >
> > I notice that the ENUM
> >
> > org.apache.geode.cache.query.IndexType has been deprecated but can't
> > find what to use instead of this ENUM if I wanted to use a
> > non-deprecated alternative.
> >
> > I understand that HASH indexes are no longer recommended but the other
> > types (PRIMARY_KEY, FUNCTIONAL) are still valid and I believe we
> > should be able to use them without using deprecated code.
> >
> > Can anyone tell me how this is accomplished?
> >
> > Thanks, Joris.
> >
> >
> > --
> > *Joris Melchior *
> > CF Engineering
> > Pivotal Toronto
> > 416 877 5427
> >
> > “Programs must be written for people to read, and only incidentally for
> > machines to execute.” – *Hal Abelson*
> > 
> >
>
>
> --
> -John
> john.blum10101 (skype)
>


-- 
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427

“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*