apache / geode

* GEODE-8946: User Guide - add an Upgrade section

…ogger is stopped

…6123)

* Added tests to validate synchronized modifiers.
* Enum serialization fixed, comments updated

- update documentation to show SLOWLOG as a supported command
- move SLOWLOG to supported commands list in RedisCommandTypes
- update supported commands test
- did not add any new tests because it was already very well tested.
- add footnote to readme

* GEODE-6143: remove powermock from LinuxSystemStatsTest

- make a visible for testing function that takes in file paths of
netstats and stats
- since it is an integration test anyway, just read real files from test
resources
- Clean up some warnings
- use variable name `ignore` for exceptions we catch but don't do
   anything with
- remove unneeded initialization of String
- remove empty if clause
- remove unneeded assignments
- simplify condition check
- replace explicit type with <>

Authored-by: M. Oleske <michael@oleske.engineer>

#6093)

GEODE-9022: Support Info Command

- add info command to supported list
- add unit/integration tests
- add dunit concurrency test
- remove redundant test
- declare configureMaxMemory() and getExposedPort() abstract
- remove unused boolean

Co-authored-by: Ray Ingles <ringles@vmware.com>

 - Remove PowerMock from GetClusterConfigurationFunctionTest
 - Extract InternalLocator.getLocator() static call to helper method in
 GetClusterConfigurationFunction
 - Remove uses of PowerMock from DistributedRegionSearchLoadJUnitTest
 - Extract SearchLoadAndWriteProcessor.getProcessor() static call to
 helper method in DistributedRegion
 - Clean up most warnings in DistributedRegionSearchLoadJUnitTest
 - Remove PowerMock from TableBuilderJUnitTest
 - Make TableBuilder methods not static
 - Make TableBuilderHelper methods not static
 - Move TableBuilderHelper methods into TableBuilder
 - Refactor test code to use AssertJ
 - Modify test case to not be identical to existing case
 - Move TableBuilderJUnitTest from IntegrationTest to Test
 - Clean up compiler warnings in affected classes

Authored-by: Donal Evans <doevans@vmware.com>

This ability allows for the future mapping of cluster slots to geode
buckets which is preemptive to enabling redis clustering support.

- Bucket count defaults to 128 and must be a a power of 2 and a factor
  of 16384 (the number of redis slots).
- Supports using hashtags in the key.

…CRBY command

…ion (#6129)

…ers as requested (#6126)

   * DataSerializable classes were converted in DataSerializableFixedID
   * serialVersionID were added to the unavoidable Serializable classes

…#6104)

For PutAll and RemoveAll, when removing destroy token from CQ result keys, use the keys in the individual entry events, instead of using the key in the base event.

…tible-with-redis commands

GEODE-8965: Support Redis-style OOM error message

- Allow execution of Redis commands in low-memory conditions
- Test with large key size to guarantee OOM error
- In tests use multiple key sizes to pack used memory more tightly
- force multiple GCs as memory is filled, add memory-pressure thread in tests
- Add memory pressure to del and expire tests

Co-authored-by: Ray Ingles <ringles@vmware.com>

Clean up some warnings

- specified paramaterized class instead of raw
- Use local variables
- Remove unneeded throws

Authored-by: M. Oleske <michael@oleske.engineer>

* turn off Github PR to Jira comment mirroring
* this is a development infrastructure change only

* GEODE-8972: remove shunnedMembers collection from GMSMembership

* Changes after the code review

…e reporting (#6084)

- Implement default getForceReCalculateSize in RedisData interface
- Expose dataStoreBytesInUse on GeodeRedisServer
- Expose dataStoreBytesInUse on GeodeRedisService
- Expose dataStoreBytesInUse on RedisClusterStartupRule

Authored-by: john Hutchison <hutchisonjo@vmware.com>

…nal changes (#6095)

* GEODE-8953: User Guide - re-introduce transaction details regarding non-transactional changes

…6079)

This test was closing a client socket before ensuring that a thread it
had created was finished.  If the socket is closed quickly enough it
could cause that thread to get an IOException and cause the test to
fail.

The fix is to ensure that the thread is finished before closing the
client socket.

 -add test for hscan not returning value removed from hash
 -refactor some tests to better reflect use cases
 -create HScan DunitTest
 -Fix Concurrency issue for Hscan
 -add UUID to client
 -make hscan on redisHash store/retrieve  snapshot of entryset for each client
 -add Unit tests for Redishash.HscanSnapshot

Authored-by: john Hutchison <hutchisonjo@vmware.com>

…tion version when adding new minor

…ansaction between vm invocations that modify the tx. (#6054)

This allows threads other than the originator to finish the tx

If thread monitoring is enable, the Connection class will not get a DummyExecutor
instead of null thus preventing the NPE.