You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@eventmesh.apache.org by "karsonto (via GitHub)" <gi...@apache.org> on 2024/04/16 09:34:04 UTC
[I] [Enhancement] Using Nacos NamingService to save meta data. (eventmesh)
karsonto opened a new issue, #4843:
URL: https://github.com/apache/eventmesh/issues/4843
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Enhancement Request
When using Nacos as a meta service should use naming service to save meta data.
### Describe the solution you'd like
When using nacos as meta storage, it uses configservice to save client info curenly.
<img width="1204" alt="image" src="https://github.com/apache/eventmesh/assets/31433550/76906404-7eb4-4c9c-9b17-93b41996d916">
<img width="1196" alt="image" src="https://github.com/apache/eventmesh/assets/31433550/1b8517ba-b5c6-466b-aeda-bf2cb6c57fee">
But I think this usage is inappropriate, because when nacos uses a cluster, config data will be persisted to the database, TPS is very low, and these service-related information should be saved to the metadata of the registration center
<img width="1286" alt="image" src="https://github.com/apache/eventmesh/assets/31433550/7c7294a6-2244-4986-88fb-7a223652ea9c">
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) *
--
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: issues-unsubscribe@eventmesh.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: issues-help@eventmesh.apache.org
Re: [I] [Enhancement] Use Nacos NamingService to save meta data (eventmesh)
Posted by "xwm1992 (via GitHub)" <gi...@apache.org>.
xwm1992 commented on issue #4843:
URL: https://github.com/apache/eventmesh/issues/4843#issuecomment-2068352173
> I have found that subscriber information is stored on meta storage, which is frequently updated and not suitable for persistent storage.
But if you use name service, if one eventmesh goes down, how can you ensure that the subscription information on this eventmesh is loaded to other meshes?
--
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: issues-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: issues-help@eventmesh.apache.org
Re: [I] [Enhancement] Use Nacos NamingService to save meta data (eventmesh)
Posted by "karsonto (via GitHub)" <gi...@apache.org>.
karsonto commented on issue #4843:
URL: https://github.com/apache/eventmesh/issues/4843#issuecomment-2074316299
You can consider using a permanent instance to save the mata data when registering, and the information should not be lost when the server goes down.
--
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: issues-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: issues-help@eventmesh.apache.org
Re: [I] [Enhancement] Use Nacos NamingService to save meta data (eventmesh)
Posted by "xwm1992 (via GitHub)" <gi...@apache.org>.
xwm1992 commented on issue #4843:
URL: https://github.com/apache/eventmesh/issues/4843#issuecomment-2065601025
As far as I know, nacos name service has no way to persist the meta data to be stored, why do you want to use name service instead of config service?
--
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: issues-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: issues-help@eventmesh.apache.org
Re: [I] [Enhancement] Use Nacos NamingService to save meta data (eventmesh)
Posted by "karsonto (via GitHub)" <gi...@apache.org>.
karsonto commented on issue #4843:
URL: https://github.com/apache/eventmesh/issues/4843#issuecomment-2065773816
I have found that subscriber information is stored on meta storage, which is frequently updated and not suitable for persistent storage.
--
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: issues-unsubscribe@eventmesh.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: issues-help@eventmesh.apache.org