YoWuwuuuw opened a new pull request, #7756:
URL: https://github.com/apache/incubator-seata/pull/7756
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- Please make sure you have read and understood the contributing
guidelines -->
- [ ] I have read the
[CONTRIBUTING.md](https://github.com/apache/incubator-seata/blob/2.x/CONTRIBUTING.md)
guidelines.
- [ ] I have registered the PR
[changes](https://github.com/apache/incubator-seata/tree/2.x/changes).
### Ⅰ. Describe what this PR did
Enhance the Redis registry center with metadata registration and discovery
capabilities based on branch 'gsoc-2025-meta-registry'.
**1. Storage Design**
Survival Key: `registry.redis.{cluster}_{ip:port}` (String, `SETEX` for
keep-alive, heartbeat renewal)
Metadata Key: `registry.redis.{cluster}.meta_{ip:port}` (Hash, `HSET` for
key -> value, `EXPIRE` has the same TTL as the survival key)
> Compatibility: Write two keys for instances with metadata, write one key
for instances without metadata, ensuring normal operation even with client and
server version mismatches.
**2. Registration Process**
Write the survival key first (without publishing) → Ensure its existence
Then write the metadata hash and set the TTL (set the TTL even without
metadata)
Finally, publish the `REGISTER` event to ensure consumers can read the "with
metadata" instance on the first read.
> Heartbeat: During renewal, only refresh the TTL of the two keys, do not
repeatedly write metadata.
**3. Lookup/Subscribe:**
- Initial Load: `SCAN registry.redis.{cluster}_*`, directly parse
`{ip:port}` from the key name, read the corresponding meta hash, and build...
ServiceInstance (with metadata preferred)
- Subscribe to updates: Upon receiving the REGISTER, first delete the old
instance at the same address, then add the new instance (with metadata) to
remove duplicates and avoid "coexistence of instances with/without metadata at
the same address".
### Ⅱ. Does this pull request fix one issue?
<!-- If that, add "fixes #xxx" below in the next line, for example, fixes
#97. -->
### Ⅲ. Why don't you add test cases (unit test/integration test)?
### Ⅳ. Describe how to verify it
### Ⅴ. Special notes for reviews
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
