vertx / io.vertx.rxjava.redis.sentinel / RedisSentinel

# RedisSentinel

`open class RedisSentinel`

Interface for sentinel commands NOTE: This class has been automatically generated from the io.vertx.redis.sentinel.RedisSentinel non RX-ified interface using Vert.x codegen.

### Constructors

<init> | `RedisSentinel(delegate: RedisSentinel)`

### Properties

__TYPE_ARG | `static val __TYPE_ARG: TypeArg<RedisSentinel>`

### Functions

ckquorum | `open fun ckquorum(name: String, handler: Handler<AsyncResult<String>>): RedisSentinel` Check if the current Sentinel configuration is able to reach the quorum needed to failover a master, and the majority needed to authorize the failover. This command should be used in monitoring systems to check if a Sentinel deployment is ok.
close | `open fun close(handler: Handler<AsyncResult<Void>>): Unit` Close the client - when it is fully closed the handler will be called.
create | `open static fun create(vertx: Vertx, config: RedisOptions): RedisSentinel`
equals | `open fun equals(other: Any?): Boolean`
failover | `open fun failover(name: String, handler: Handler<AsyncResult<String>>): RedisSentinel` Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels (however a new version of the configuration will be published so that the other Sentinels will update their configurations)
flushConfig | `open fun flushConfig(handler: Handler<AsyncResult<Void>>): RedisSentinel` Force Sentinel to rewrite its configuration on disk, including the current Sentinel state. Normally Sentinel rewrites the configuration every time something changes in its state (in the context of the subset of the state which is persisted on disk across restart). However sometimes it is possible that the configuration file is lost because of operation errors, disk failures, package upgrade scripts or configuration managers. In those cases a way to to force Sentinel to rewrite the configuration file is handy. This command works even if the previous configuration file is completely missing.
getDelegate | `open fun getDelegate(): RedisSentinel`
getMasterAddrByName | `open fun getMasterAddrByName(name: String, handler: Handler<AsyncResult<JsonArray>>): RedisSentinel` Return the ip and port number of the master with that name. If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave
hashCode | `open fun hashCode(): Int`
master | `open fun master(name: String, handler: Handler<AsyncResult<JsonArray>>): RedisSentinel` Show the state and info of the specified master
masters | `open fun masters(handler: Handler<AsyncResult<JsonArray>>): RedisSentinel` Show a list of monitored masters and their state
newInstance | `open static fun newInstance(arg: RedisSentinel): RedisSentinel`
reset | `open fun reset(pattern: String, handler: Handler<AsyncResult<Void>>): RedisSentinel` Reset all the masters with matching name. The pattern argument is a glob-style pattern. The reset process clears any previous state in a master (including a failover in pro
rxCkquorum | `open fun rxCkquorum(name: String): Single<String>` Check if the current Sentinel configuration is able to reach the quorum needed to failover a master, and the majority needed to authorize the failover. This command should be used in monitoring systems to check if a Sentinel deployment is ok.
rxClose | `open fun rxClose(): Single<Void>` Close the client - when it is fully closed the handler will be called.
rxFailover | `open fun rxFailover(name: String): Single<String>` Force a failover as if the master was not reachable, and without asking for agreement to other Sentinels (however a new version of the configuration will be published so that the other Sentinels will update their configurations)
rxFlushConfig | `open fun rxFlushConfig(): Single<Void>` Force Sentinel to rewrite its configuration on disk, including the current Sentinel state. Normally Sentinel rewrites the configuration every time something changes in its state (in the context of the subset of the state which is persisted on disk across restart). However sometimes it is possible that the configuration file is lost because of operation errors, disk failures, package upgrade scripts or configuration managers. In those cases a way to to force Sentinel to rewrite the configuration file is handy. This command works even if the previous configuration file is completely missing.
rxGetMasterAddrByName | `open fun rxGetMasterAddrByName(name: String): Single<JsonArray>` Return the ip and port number of the master with that name. If a failover is in progress or terminated successfully for this master it returns the address and port of the promoted slave
rxMaster | `open fun rxMaster(name: String): Single<JsonArray>` Show the state and info of the specified master
rxMasters | `open fun rxMasters(): Single<JsonArray>` Show a list of monitored masters and their state
rxReset | `open fun rxReset(pattern: String): Single<Void>` Reset all the masters with matching name. The pattern argument is a glob-style pattern. The reset process clears any previous state in a master (including a failover in pro
rxSentinels | `open fun rxSentinels(name: String): Single<JsonArray>` Show a list of sentinel instances for this master, and their state
rxSlaves | `open fun rxSlaves(name: String): Single<JsonArray>` Show a list of slaves for this master, and their state
sentinels | `open fun sentinels(name: String, handler: Handler<AsyncResult<JsonArray>>): RedisSentinel` Show a list of sentinel instances for this master, and their state
slaves | `open fun slaves(name: String, handler: Handler<AsyncResult<JsonArray>>): RedisSentinel` Show a list of slaves for this master, and their state
toString | `open fun toString(): String`