We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2023-08-31 09:06:28.373 2074081024] rmt_net.c:621 ERROR: socket error: Connection timed out [2023-08-31 09:06:28.374 2074081024] rmt_net.c:988 Error: can't connect to redis master [2023-08-31 09:06:28.374 2074081024] rmt_redis.c:7768 ERROR: new rmt tcp context from meta, connect to 10.13.207.97:6379 failed [2023-08-31 09:06:28.374 2074081024] rmt_redis.c:7915 ERROR: check not invalid, new tcp context failed, password:(null) addr:10.13.207.97:6379 [2023-08-31 09:06:28.374 2074081024] rmt_redis.c:8019 ERROR: check node failed: node(10.13.207.97:6379) does not belong to current cluster or connect faild, identifier:sns-note-list-v1-sh4-1 [2023-08-31 09:06:28.382 2074081024] rmt_redis.c:7541 route table check finish, fail slot count 0 [2023-08-31 09:06:28.382 2074081024] rmt_redis.c:2103 srnode->ctx->target_type: 3, srnode->rdb->received: 0 [2023-08-31 09:06:28.382 2074081024] rmt_redis.c:2110 Reconnect to node[10.14.78.106:6379] for replication [2023-08-31 09:06:28.382 2074081024] rmt_redis.c:2103 srnode->ctx->target_type: 3, srnode->rdb->received: 0 [2023-08-31 09:06:28.382 2074081024] rmt_redis.c:2110 Reconnect to node[10.14.162.91:6379] for replication [2023-08-31 09:06:28.382 2074081024] rmt_redis.c:1741 Start connecting to MASTER[10.14.78.106:6379]. [2023-08-31 09:06:28.382 2074081024] rmt_redis.c:1741 Start connecting to MASTER[10.14.162.91:6379]. [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1774 Master[10.14.78.106:6379] replied to PING, replication can continue... [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1774 Master[10.14.162.91:6379] replied to PING, replication can continue... [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1068 Trying a partial resynchronization with MASTER[10.14.162.91:6379] (request ?:9105663131). [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1896 MASTER <-> SLAVE sync: Master[10.14.162.91:6379] start synchronization. [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1068 Trying a partial resynchronization with MASTER[10.14.78.106:6379] (request ?:9071930214). [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1896 MASTER <-> SLAVE sync: Master[10.14.78.106:6379] start synchronization. [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1140 Successful partial resynchronization with MASTER[10.14.162.91:6379]. [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1437 Again online for node[10.14.162.91:6379] replication. [2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1913 MASTER <-> SLAVE sync: Master[10.14.162.91:6379] accepted a Partial Resynchronization. [2023-08-31 09:06:28.384 2074081024] rmt_redis.c:1140 Successful partial resynchronization with MASTER[10.14.78.106:6379].
The text was updated successfully, but these errors were encountered:
No branches or pull requests
[2023-08-31 09:06:28.373 2074081024] rmt_net.c:621 ERROR: socket error: Connection timed out
[2023-08-31 09:06:28.374 2074081024] rmt_net.c:988 Error: can't connect to redis master
[2023-08-31 09:06:28.374 2074081024] rmt_redis.c:7768 ERROR: new rmt tcp context from meta, connect to 10.13.207.97:6379 failed
[2023-08-31 09:06:28.374 2074081024] rmt_redis.c:7915 ERROR: check not invalid, new tcp context failed, password:(null) addr:10.13.207.97:6379
[2023-08-31 09:06:28.374 2074081024] rmt_redis.c:8019 ERROR: check node failed: node(10.13.207.97:6379) does not belong to current cluster or connect faild, identifier:sns-note-list-v1-sh4-1
[2023-08-31 09:06:28.382 2074081024] rmt_redis.c:7541 route table check finish, fail slot count 0
[2023-08-31 09:06:28.382 2074081024] rmt_redis.c:2103 srnode->ctx->target_type: 3, srnode->rdb->received: 0
[2023-08-31 09:06:28.382 2074081024] rmt_redis.c:2110 Reconnect to node[10.14.78.106:6379] for replication
[2023-08-31 09:06:28.382 2074081024] rmt_redis.c:2103 srnode->ctx->target_type: 3, srnode->rdb->received: 0
[2023-08-31 09:06:28.382 2074081024] rmt_redis.c:2110 Reconnect to node[10.14.162.91:6379] for replication
[2023-08-31 09:06:28.382 2074081024] rmt_redis.c:1741 Start connecting to MASTER[10.14.78.106:6379].
[2023-08-31 09:06:28.382 2074081024] rmt_redis.c:1741 Start connecting to MASTER[10.14.162.91:6379].
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1774 Master[10.14.78.106:6379] replied to PING, replication can continue...
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1774 Master[10.14.162.91:6379] replied to PING, replication can continue...
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1068 Trying a partial resynchronization with MASTER[10.14.162.91:6379] (request ?:9105663131).
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1896 MASTER <-> SLAVE sync: Master[10.14.162.91:6379] start synchronization.
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1068 Trying a partial resynchronization with MASTER[10.14.78.106:6379] (request ?:9071930214).
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1896 MASTER <-> SLAVE sync: Master[10.14.78.106:6379] start synchronization.
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1140 Successful partial resynchronization with MASTER[10.14.162.91:6379].
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1437 Again online for node[10.14.162.91:6379] replication.
[2023-08-31 09:06:28.383 2074081024] rmt_redis.c:1913 MASTER <-> SLAVE sync: Master[10.14.162.91:6379] accepted a Partial Resynchronization.
[2023-08-31 09:06:28.384 2074081024] rmt_redis.c:1140 Successful partial resynchronization with MASTER[10.14.78.106:6379].
The text was updated successfully, but these errors were encountered: