[Deployment] miss messages when deploy OpenIM on two CVM

[jamky]

OpenIM Server Version

3.7.1

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Source Code Deployment

Issue Description and Steps to Reproduce

deploy OpenIM on two CVM, sharing MongoDB, Redis, Kafka, Mini, but miss messages when user chat, and users see the different chat messages when call jssdk method getAdvancedHistoryMessageList ,sometimes see the right chat message for today,sometimes see the wrong chat message for yesterday, we cannot find the problem.

deploy steps:

1. deploy the openim-im-server v3.7.1, chat 1.7.1,oimws v3.5.1-beta.1 on two CVM

2. openim-im-server kafka.yml:
   `username: '****'

password: '****'
producerAck: ""
compressType: "none"
address: [ 172.16.0.4:9092 ]
toRedisTopic: "toRedis"
toMongoTopic: "toMongo"
toPushTopic: "toPush"
toRedisGroupID: redis
toMongoGroupID: mongo
toPushGroupID: push
tls:
enableTLS: false
caCrt: ""
clientCrt: ""
clientKey: ""
clientKeyPwd: ""
insecureSkipVerify: false`

3. openim-im-server and chat mongodb.yml:
   `uri: ''

address: [ 172.16.0.11:27017, 172.16.0.7:27017 ]
database: user_openim_v3
username: openim_v3
password: ****
maxPoolSize: 100
maxRetry: 10`

4.openim-im-server and chat redis.yml
`address: [ 172.16.0.2:6379 ]

username: ''
password: ****
enablePipeline: false
clusterMode: false
db: 1
maxRetry: 10`

5.openim-im-server webhooks.yml:
`url: "https://xx.yy.com/api/robot/v1/im/callback"

afterSendSingleMsg:
enable: true
timeout: 5
`

Some log：
openim-service-log.2024-09-01.01.txt

Screenshots Link

No response

[OpenIM-Robot]

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

[skiffer-git]

We'll be testing it soon. Thanks for bringing this up.

[icey-yu]

After our testing, we were unable to reproduce the issue. You can try updating the code and testing again. If the issue persists, please provide more detailed configuration information, such as the number of components, how they are deployed, and the specific scenario in which the issue occurs.