The Apache Geode dedication to software quality

2021-09-03 Thread Kirk Lund
The Apache Geode project has built up a development process and community
standards since its initial start as an Apache podling in 2014 with the
purpose of releasing software of the highest quality developed by engineers
who believe in the project and its future. Our DOD (Definition of Done) may
be sparse and loose, but it captures some of the most important points that
have been discussed on the dev-list and agreed upon by this community. Its
essence is a focus on quality, both for users of Geode and developers who
will contribute and maintain the code base.

Our DOD [1] includes the following on developing code to be released:

CONTINUOUS DEVELOPMENT ACTIVITIES
+ Design reviewed on Wiki, especially for larger features
+ Implemented according to specification in the ticket
+ Unit tested
+ Integration tested
+ Public/ Peer-reviewed
+ Merged into 'develop'
+ JIRA Ticket marked 'resolved'

All committers must understand and follow our "development process and
community standards" [2] as discussed on the dev-list or captured on the
Apache Geode Wiki. Contributors who hope to actively contribute must learn
and follow this process. It's the responsibility of all committers to help
educate and guide these contributors in both our process and Code of
Conduct [3].

Everyone should be encouraged to ask questions and discuss how we can best
deliver high-quality software that will be easy to maintain by all Apache
Geode developers in the years to come.

Quality impassioned,
Kirk Lund

[1] https://cwiki.apache.org/confluence/display/GEODE/Definition+of+Done
[2] https://cwiki.apache.org/confluence/display/GEODE/Becoming+a+committer
[3] https://cwiki.apache.org/confluence/display/GEODE/Code+of+Conduct


[ANNOUNCE] Apache Geode 1.14.0

2021-09-03 Thread nabarun nag
The Apache Geode community is pleased to announce the availability of
Apache Geode 1.14.0

Apache Geode is a data management platform that provides a database-like
consistency model, reliable transaction processing and a shared-nothing
architecture to maintain very low latency performance with high concurrency
processing.

This release includes a significant number of bug fixes, improvements
in current behavior along with the addition of a few statistics to
monitor the cluster health.

Few notable changes are:

1. The creation of OQL indexes now works on sub-regions.
2. Proper exceptions are thrown when a region is destroyed during
function execution.
3. Daemon threads are now used while rebalancing regions.
4. Gateway receivers can be configured with the same
hostname-for-senders and port. The reason for such a setup is
deploying a Geode cluster on a Kubernetes cluster where all GW
receivers are reachable from the outside world on the same IP and
port.
5. Disk stores are recovered in parallel during cluster restarts.
6. New option in GFSH command "start gateway sender" to control
clearing of existing queues.
7. New member field added in OQL query GFSH command to point to the
member on which the query will be executed.
8. No more ConcurrentModificationException when using JTA transactions.
9. Setting SNI server name is now not needed if endpoint verification
is disabled.
10. A new REST interface for disk-store creation has been introduced.
11. GFSH command to create defined indexes now works if connected to a
new locator which joined the cluster after indexes were defined.
12. Session state modules dependencies were cleaned up and made more efficient.
13. Limited retries while trying to create Lucene indexes to prevent
stack overflow issues.
14. A new statistic was added to get the heap memory occupied by the
gateway sender's queue.
15. maximum-time-between-pings set when creating a gateway receiver is
now honored instead of being ignored.
16. Deadlocks are prevented when java garbage collection and tombstone
collection occur simultaneously.
17. 'conserve-sockets' default value is now set to false when the
members are started.
18. Slower receivers with async-distribution-timeout greater than 0
are now not allowed with cluster TLS/SSL.
19. Clients trying to register interest in an older version server
will now receive a ServerRefusedConnectionException.
20. The speed of registering interest during rolling upgrades has been improved.
21. A new feature was added to print out the tenured heap in the log
files after garbage collection.
22. Bucket statistics were fixed.

For the full list of changes please review the release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.0

The release artifacts can be downloaded from the project website:
https://geode.apache.org/releases/

The release documentation is available at:
https://geode.apache.org/docs/guide/114/about_geode.html

We would like to thank all the contributors that made the release possible.
Regards,
Nabarun Nag on behalf of the Apache Geode team


Re: [ANNOUNCE] Apache Geode 1.14.0

2021-09-03 Thread Anilkumar Gingade
Great work team. Thanks Naba and others who helped in getting the release out.

Anil.


On 9/3/21, 11:58 AM, "nabarun nag"  wrote:

The Apache Geode community is pleased to announce the availability of
Apache Geode 1.14.0

Apache Geode is a data management platform that provides a database-like
consistency model, reliable transaction processing and a shared-nothing
architecture to maintain very low latency performance with high concurrency
processing.

This release includes a significant number of bug fixes, improvements
in current behavior along with the addition of a few statistics to
monitor the cluster health.

Few notable changes are:

1. The creation of OQL indexes now works on sub-regions.
2. Proper exceptions are thrown when a region is destroyed during
function execution.
3. Daemon threads are now used while rebalancing regions.
4. Gateway receivers can be configured with the same
hostname-for-senders and port. The reason for such a setup is
deploying a Geode cluster on a Kubernetes cluster where all GW
receivers are reachable from the outside world on the same IP and
port.
5. Disk stores are recovered in parallel during cluster restarts.
6. New option in GFSH command "start gateway sender" to control
clearing of existing queues.
7. New member field added in OQL query GFSH command to point to the
member on which the query will be executed.
8. No more ConcurrentModificationException when using JTA transactions.
9. Setting SNI server name is now not needed if endpoint verification
is disabled.
10. A new REST interface for disk-store creation has been introduced.
11. GFSH command to create defined indexes now works if connected to a
new locator which joined the cluster after indexes were defined.
12. Session state modules dependencies were cleaned up and made more 
efficient.
13. Limited retries while trying to create Lucene indexes to prevent
stack overflow issues.
14. A new statistic was added to get the heap memory occupied by the
gateway sender's queue.
15. maximum-time-between-pings set when creating a gateway receiver is
now honored instead of being ignored.
16. Deadlocks are prevented when java garbage collection and tombstone
collection occur simultaneously.
17. 'conserve-sockets' default value is now set to false when the
members are started.
18. Slower receivers with async-distribution-timeout greater than 0
are now not allowed with cluster TLS/SSL.
19. Clients trying to register interest in an older version server
will now receive a ServerRefusedConnectionException.
20. The speed of registering interest during rolling upgrades has been 
improved.
21. A new feature was added to print out the tenured heap in the log
files after garbage collection.
22. Bucket statistics were fixed.

For the full list of changes please review the release notes:

https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.14.0

The release artifacts can be downloaded from the project website:
https://geode.apache.org/releases/

The release documentation is available at:
https://geode.apache.org/docs/guide/114/about_geode.html

We would like to thank all the contributors that made the release possible.
Regards,
Nabarun Nag on behalf of the Apache Geode team