When do we meet? Every first Thursday at 8:00 Pacific (16:00 UTC)
Where do we meet?
Participation via MS Teams: Click here to join the meeting
Or call in (audio only) +1 323-776-6788,,80712819# United States, Los Angeles Phone Conference ID: 807 128 19# Find a local number
Host Instructions
- Record meeting and afterwards make available to the community. (we'll need to iterate on how to best do this from MS Teams)
- Lead discussion through meeting agenda
- After meeting add a new header in this doc for the next meeting. Carry topics forward
Agenda
April 7th 2022
Reflections on the conserve-sockets setting in Geode.
The idea is to first briefly present what the conserve-sockets parameter in Geode offers and what the Geode documentation includes and recommends about it. Secondly, share our experience with this parameter. And finally have a discussion about the challenges of setting a value for this parameter and possible improvements in terms of documentation and/or code.
February 17th 2022
Igor Gizdic presented on thread and server health monitoring: how to kick out slow/sick members and the like
November 4th 2021
Evaristo Jose Camarero presented on challenges that he and his team encountered around resource consumption of OQL queries. He showed us how he was able to address these issue using function execution and how we might improve that area of Apache Geode going forward.
October 14th 2021
Jacob Barrett lead a discussion on making our code base more modular and new functionality pluggable.
September 9th
Patrick Johnson on ClassLoader isolation
June 2nd 2021
- Presentation and discussion over the following issue:
Title: "Servers waiting indefinitely for a reply"
Summary: If a packet is lost between servers, multiple threads get stuck and servers wait indefinitely for a reply, without any retry mechanism or timeout.
Context: https://markmail.org/search/?q=list%3Aorg.apache.geode.dev+order%3Adate-backward#query:list%3Aorg.apache.geode.dev%20order%3Adate-backward+page:1+mid:l6uw5vs62vmtcxo4+state:results
Petar Tomic presented the above topic. The primary issue is lack of any retry when the TCP connection between two servers gets disrupted (in this case because a proxy is down), but the UDP connection persists. The rest of the meeting was spent discussing potential approaches to solving this problem. Petar will follow up on the mailing list with a proposal for a solution.
May 5th 2021
- RFC "Geode Command to replicate region data from one site to another connected via WAN" way forward (Geode Command to replicate region data from one site to another connected via WAN)
27 community members attended and discussed the above RFC. After Alberto Gomez presented a summary of the RFC, much of the discussion focused avoiding duplication and minimizing impact on cluster stability due to increased resource consumption.
Alberto will update the RFC with additional details and share his current work in form of a draft PR. During the discussion the article Routing Events Directly to a Parallel Apache Geode AsyncEventQueue by Barry Oglesby was referenced.