| commit | 5c7d47d34c2b8a53874ec6f53e66c2290fd0427c | [log] [tgz] |
|---|---|---|
| author | Alberto Gomez <alberto.gomez@est.tech> | Fri Nov 06 22:52:10 2020 +0100 |
| committer | GitHub <noreply@github.com> | Fri Nov 06 13:52:10 2020 -0800 |
| tree | 4d657714c8bd31c6720a51501437b7ce23cdfaac | |
| parent | 07910325960691ab6774bedbf6e1a96f693e85d1 [diff] |
GEODE-8688: Fix flaky C++ native client integration tests (#686) * GEODE-8688: Fix flaky C++ native client integration tests The following integration test cases under integration/test (new integration tests) ar flaky (do not fail normally when run locally but fail very often when run in CI). - PartitionRegionOpsTest.getPartitionedRegionWithRedundancyServerGoesDownSingleHop - PartitionRegionOpsTest.putPartitionedRegionWithRedundancyServerGoesDownSingleHop There were two reasons that can make them fail. One of them is that sometimes the connections to the server have expired before the server is restarted and therefore, when traffic is sent to the restarted server, no errors are found. To fix this, the pool configuration for the test client has been changed so that connections do not expire. The other reason is that sometimes the error in the connection is found by the ping thread that is invoking the ThinClientPoolDM::sendRequestToEP() method and in this method, when the IO error or TIMEOUT error are encountered, the endpoint is not removed from the metadata (by means of the removeBucketServerLocation method). The code has been updated to remove the metadata also in this case. With these two changes, the test cases are not flaky anymore.
Overview
Building from Source
Application Development
Native Client is a client implementation for Apache Geode that does not require the Java server JARs.
Directions to build Native Client from source can be found in the source distribution in BUILDING.md.
Native Client applications can be written in these client technologies:
This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information.
The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.
The following provides more details on the included cryptographic software: