All notable changes to this project will be documented in this file.
Server to server replication implemented
- Remove WaitStrategy in the Retryer used to check if ServiceRegistry is refreshed during ServiceRegistryUpdater startup
- Execute updateRegistry operation in async inside ServiceFinderHub so that main thread reaches till waitTillHubIsReady instead of waiting for lock release and hubStartTimeoutMs is honoured as expected
- Setting the read timeout and write timeout in OkHttpClient same as operation timeout given in HttpClientConfig
- Added waitStrategy in waitTillServiceIsReady in ServiceFinderHub to save come cpu cycles in Retryer
- Add feature to exclude services from service data source
- Create one single
RangerHealthCheck
for all curatorFrameworks when giving multiple zookeeper connection strings - Update
lastUpdatedTimeStamp
for service nodes in service registry for zk / http communication failures from any kind of node data source - zk/http/drove - Pertaining to PR : #22, building of a ServiceFinderHub and a ServiceFinder are bounded.
- Version bump to release lexicographically higher version than 1.0-dw3-RC17
- Domain specific collision checker in id generator
- Fixed hierarchical environment aware shard selector : If a service is deployed with environment : env.x.y.z then it should be able to discover other services present in environment - [env , env.x , env.x.y, env.x.y.z ]
- Moved discovery bundle from https://github.com/appform-io/dropwizard-service-discovery.
- Updated to dropwizard version 2.1.10 : BOM update.
- Upgraded to java version 17 with release in 11
- Removed com.fasterxml and introduced dropwizard-jackson for the jackson bindings.
- Upgraded to junit 5 and fixed the necessary tests including wiremock versions and tests.
- Upgraded the curator framework version
- Done sonar fixes after the java version upgrade
- When the Collection of Services is empty the monitor should gracefully return PR
- Handling NodeDataSource refresh failures gracefully
- Dynamic service registration
- Introduced a portScheme on ServiceNode, so multiple types of protocols could be supported. Was assumed to be HTTP instead.