im_server

221 Commits 2 Branches 0 Tags

2 Commits

Author	SHA1	Message	Date
Austin	55afd976c9	fix(server): 修复群组权限缓存与解散群问题 1. 新增group事件处理逻辑，实时刷新内存中的群组权限与状态 2. 加载topic时过滤已解散的群组，防止被旧成员恢复 3. 补充群成员离开事件的用户ID字段，完善事件处理	2026-09-15 15:18:14 +08:00
Austin	5dd0a42002	fix: harden message seq allocation against stale redis replicas - use sentinel failover client for group message runtime when sentinel_master_name/sentinel_addrs are configured, so seq counter reads never hit a stale replica after failover - re-seed missing redis seq counter from DB topic seqid instead of trusting the caller in-memory baseline - on unique-key conflict during async persist, re-allocate seq from DB latest, bump redis counter and fix the idempotency record so resends with the same client mid return the final seq - add uk(topic, seqid) unique keys for im_messages in tenant DDL	2026-09-15 12:41:38 +08:00

Author

SHA1

Message

Date

Austin

55afd976c9

fix(server): 修复群组权限缓存与解散群问题

1. 新增group事件处理逻辑，实时刷新内存中的群组权限与状态
2. 加载topic时过滤已解散的群组，防止被旧成员恢复
3. 补充群成员离开事件的用户ID字段，完善事件处理

2026-09-15 15:18:14 +08:00

Austin

5dd0a42002

fix: harden message seq allocation against stale redis replicas

- use sentinel failover client for group message runtime when
  sentinel_master_name/sentinel_addrs are configured, so seq counter
  reads never hit a stale replica after failover
- re-seed missing redis seq counter from DB topic seqid instead of
  trusting the caller in-memory baseline
- on unique-key conflict during async persist, re-allocate seq from DB
  latest, bump redis counter and fix the idempotency record so resends
  with the same client mid return the final seq
- add uk(topic, seqid) unique keys for im_messages in tenant DDL

2026-09-15 12:41:38 +08:00