load_balancer allows you to send operations to one of a number of endpoints(Members).
More...
#include <load_balancer.h>
|
template<typename Handler , typename = util::enable_if_rvalue_ref_t<Handler &&>> |
load_balancer & | init (Handler &&h) & |
| Sets the function to be called when load balancer is initialized. More...
|
|
template<typename Handler , typename = util::enable_if_rvalue_ref_t<Handler &&>> |
load_balancer && | init (Handler &&h) && |
|
template<typename Handler , typename = util::enable_if_rvalue_ref_t<Handler &&>> |
load_balancer & | next (Handler &&h) & |
| The function returns the next member to route to. More...
|
|
template<typename Handler , typename = util::enable_if_rvalue_ref_t<Handler &&>> |
load_balancer && | next (Handler &&h) && |
|
|
class | connection::ClientConnectionManagerImpl |
|
load_balancer allows you to send operations to one of a number of endpoints(Members).
It is up to the implementation to use different load balancing policies. If Client is configured as smart, only the operations that are not key based will be router to the endpoint returned by the Load Balancer. If it is not smart, load_balancer will not be used. Note: Client is smart by default.
◆ init()
template<typename Handler , typename = util::enable_if_rvalue_ref_t<Handler &&>>
load_balancer& hazelcast::client::load_balancer::init |
( |
Handler && |
h | ) |
& |
|
inline |
Sets the function to be called when load balancer is initialized.
- Parameters
-
cluster | Cluster contains current membership information for initialization. And one can add membership through this class for future notifications. |
◆ next()
template<typename Handler , typename = util::enable_if_rvalue_ref_t<Handler &&>>
load_balancer& hazelcast::client::load_balancer::next |
( |
Handler && |
h | ) |
& |
|
inline |
The function returns the next member to route to.
- Parameters
-
h | The function to be used for finding the next member. |
The documentation for this class was generated from the following file: