Add active detection in sentinel mode,Reconstruct sentinel mode Listener

[chenshi5012]

sentinel mode， lost "+switch-master" message, should client add watchdog thread #3525
please check this, JedisSentinelPool / SentineledConnectionProvider provider monitor master-slave failover by subscribe the message from “+switch-master”。

this pr modify master-slave failover monitor，Two listening mechanisms are provided, one is the default subscription mechanism and the other is the active detection mechanism;
When due to network reasons, the client loses the subscription message and the main node connection of the jedis factory is still not switched, it will cause the connection to be unavailable.

1. SentinelMasterSubscribeListener the default listener
2. SentinelMasterActiveDetectListener the active detect listener

you can specify which listener to use; or open both. default is SubscribeListener,
`

SentinelPoolConfig config = new SentinelPoolConfig();
config.setEnableActiveDetectListener(true);  // default off 
config.setEnableDefaultSubscribeListener(true); // default on 
config.setActiveDetectIntervalTimeMillis(5*1000); // default 5s 
config.setSubscribeRetryWaitTimeMillis(5*1000); // default  5s 

JedisSentinelPool pool = new JedisSentinelPool(MASTER_NAME, sentinels, config, 1000,
        "foobared", 2);

`

i am working on the test case.

SentinelMasterListenerTest.zip

when Simulate the scenario of switching between active and standby， this will Affects other test cases. can you offer some help to Execute these use cases separately

[chenshi5012]

@sazzad16 , hi ,Hoque

can you help me to Run Test Case Separately，
SentinelMasterListenerTest.zip

these case will Affects test case in JedisSentinelPoolTest SentineledConnectionProviderTest .

[chenshi5012]

@yangbodong22011 你好，请问怎么 隔离运行 测试用例，有帮助文档吗？ 关于workflow

@sazzad16 hello，May I ask how to isolate and run test cases? Is there any helpful documentation? About workflow

[sazzad16]

In your machine, you can do:

mvn -Dtest=TestClassName#testMethodName test

You may also consider:

mvn -Dtest=*Sentinel* test

Here in GitHub PR, you should run all the tests.
This is not ideal, but during ongoing work you can put @Ignore annotation before all other (Sentinel) tests except the one you are working on.

[chenshi5012]

In your machine, you can do:

mvn -Dtest=TestClassName#testMethodName test

You may also consider:

mvn -Dtest=*Sentinel* test

Here in GitHub PR, you should run all the tests. This is not ideal, but during ongoing work you can put @Ignore annotation before all other (Sentinel) tests except the one you are working on.

thanks, i will working on it as soon as possible