Skip to content

/ hazelcast-nodejs-client

Hazelcast Node.js Client 4.1

@puzpuzpuz puzpuzpuz released this Jan 25, 2021 · 3 commits to master since this release

This document includes the new features, enhancements, and fixed issues for Hazelcast Node.js Client 4.1 release.

New Features

  • Blue/Green Failover Config: Client now supports blue/green deployment and disaster recovery (IMDG EE feature). #713
  • External Smart Client Discovery via Load Balancer: Adds a new discovery mechanism that allows smart client to decide whether it needs to use public addresses for communication with members. As a result, Node.js client does not need a dedicated plugin to communicate with a cluster running on a cloud environment where members are exposed via a load balancer. #703
    • Note: this feature requires Hazelcast IMDG 4.2 or higher version.

Enhancements

  • Client now supports IMap.setTtl() operation. #741
  • Client now supports IAtomicLong.getAndDecrement() operation. #640
  • Map operations that insert and modify map entries now support maxIdle parameter. #742
  • Client is now capable of reporting statistics to Hazelcast Management Center 4.2020.08 and newer. #751
  • Client now avoids random connection delay when port not specified. In prior versions, the client was randomly trying 5701, 5702, and 5703 ports in any order when connecting to members, unless the port is specified in configuration. Now it starts with 5701 port to avoid extra delays in the most common deployment scenario. #735
  • Default cluster connect timeout is increased from 20 seconds to 2 minutes in order to provider more reliable behavior in Kubernetes and similar environments where IP resolution or system restart can take around a minute. #744
  • Default automated pipelining threshold is increased from 8KB to 64KB. #729
  • Primitive number type is now used instead of Long for correlation ids. #624

Fixes

  • Prevent client ending up with two addresses to same node when node is behind a private network. #713
  • Client connection and underlying socket could leak in case of connection timeout. #739
  • Client could handle membership changes incorrectly on split brain. #734
  • Connection could not be closed immediately on socket error. #709
  • Failed client start could lead to resource leaks. #689
  • Map query and Reliable Topic code samples were incorrect. #708
  • Fix TS typings for network config. #700

Breaking Changes

  • None.

Known Issues

  • None.

Contributors

We would like to thank the contributors from our open source community who worked on this release:

Assets 2