[Feature] At present, the metadata pushed by the metadata center does not have an expiration date. When using Nacos as the metadata center, there is still a quantity limit. After switching to Redis as the metadata center, it was found that there is no expiration TTL setting

[JavaLionLi]

Pre-check

• I am sure that all the content I provide is in English.

Search before asking

• I had searched in the issues and found no similar feature requirement.

Apache Dubbo Component

Java SDK (apache/dubbo)

Descriptions

At present, the metadata pushed by the metadata center does not have an expiration date. When using Nacos as the metadata center, there is still a quantity limit. After switching to Redis as the metadata center, it was found that there is no expiration TTL setting

Also, the Jedis version is too low. Spring defaults to Jedis version 5.0.x, but it's still 3.x. Can we upgrade it

Related issues

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[AlbumenJ]

1. We can set TTL for it. But we need a mechanism to refresh it.
2. You can upgrade it in 3.3.x

[JavaLionLi]

1. We can set TTL for it. But we need a mechanism to refresh it.
2. You can upgrade it in 3.3.x

Currently, the Redis metadata center implementation class of 3.3.0 is being used, but there is no TTL code available. We will continue to monitor future updates

[AlbumenJ]

1. We can set TTL for it. But we need a mechanism to refresh it.
2. You can upgrade it in 3.3.x

Currently, the Redis metadata center implementation class of 3.3.0 is being used, but there is no TTL code available. We will continue to monitor future updates

Would you like to contribute for it:)

[qyi71]

1. We can set TTL for it. But we need a mechanism to refresh it.我们可以为它设置TTL。但是我们需要一种机制来刷新它。
2. You can upgrade it in 3.3.x您可以在 3.3.x 中升级它

Currently, the Redis metadata center implementation class of 3.3.0 is being used, but there is no TTL code available. We will continue to monitor future updates目前，正在使用 Redis 元数据中心实现类 3.3.0，但没有可用的 TTL 代码。我们将继续关注未来的更新

Would you like to contribute for it:)你愿意为它做出贡献吗：）

hello，I think I can solve it, can it be assigned to me, thanks

[AlbumenJ]

1. We can set TTL for it. But we need a mechanism to refresh it.我们可以为它设置TTL。但是我们需要一种机制来刷新它。
2. You can upgrade it in 3.3.x您可以在 3.3.x 中升级它

Currently, the Redis metadata center implementation class of 3.3.0 is being used, but there is no TTL code available. We will continue to monitor future updates目前，正在使用 Redis 元数据中心实现类 3.3.0，但没有可用的 TTL 代码。我们将继续关注未来的更新

Would you like to contribute for it:)你愿意为它做出贡献吗：）

hello，I think I can solve it, can it be assigned to me, thanks

Please go ahead

[qyi71]

1. 我们可以为其设置TTL。但我们需要一个机制来刷新它。
2. 您可以在3.3.x中升级它

目前正在使用3.3.0的Redis元数据中心实现类，但没有可用的TTL代码。我们将继续关注未来的更新

hello when would you need to use metadata expiration?

[qyi71]

1. 我们可以为其设置TTL。但我们需要一个机制来刷新它。
2. 您可以在3.3.x中升级它

目前正在使用3.3.0的Redis元数据中心实现类，但没有可用的TTL代码。我们将继续关注未来的更新

hello when would you need to use metadata expiration?

I want to know the specific scenario😊

[JavaLionLi]

1. 我们可以为其设置TTL。但我们需要一个机制来刷新它。
2. 您可以在3.3.x中升级它

目前正在使用3.3.0的Redis元数据中心实现类，但没有可用的TTL代码。我们将继续关注未来的更新

hello when would you need to use metadata expiration?

I want to know the specific scenario😊

I don't know what the logic is now.
After long-term use, the data will be more and more, and many data have expired.
I hope that unnecessary data can be automatically eliminated.