You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eventmesh.apache.org by GitBox <gi...@apache.org> on 2021/08/03 12:47:27 UTC

[GitHub] [incubator-eventmesh] ruanwenjun opened a new issue #481: Use YAML file to store configuration

ruanwenjun opened a new issue #481:
URL: https://github.com/apache/incubator-eventmesh/issues/481


   ## Enhancement Request
   Currently, there are a lot of configuration fields in EventMesh, and it will increase in the future, you can look up at `eventmesh.properties`.
   Such as:
   ```properties
   eventMesh.server.idc=DEFAULT
   eventMesh.server.env=PRD
   eventMesh.server.cluster=COMMON
   eventMesh.server.name=EVENTMESH-runtime
   eventMesh.sysid=0000
   eventMesh.server.http.port=10105
   ########################## eventMesh tcp configuration ############################
   eventMesh.server.tcp.enabled=true
   eventMesh.server.tcp.port=10000
   eventMesh.server.tcp.readerIdleSeconds=120
   eventMesh.server.tcp.writerIdleSeconds=120
   eventMesh.server.tcp.allIdleSeconds=120
   eventMesh.server.tcp.clientMaxNum=10000
   # client isolation time if the message send failure
   eventMesh.server.tcp.pushFailIsolateTimeInMills=30000
   ```
   It is difficult to find out which is your want since most of them has the same prefix.
   It is better to store them at yaml file, the advantage is that you can merge the common prefixes like below:
   ```yml
   eventMesh:
     server:
       idc: DEFAULT
       env: PRD
       cluster: COMMON
       name: EVENTMESH-runtime
       http:
         port: 10105
       tcp:
         enabled: true
         port: 10000
         readerIdleSeconds: 120
         writerIdleSeconds: 120
         allIdleSeconds: 120
         clientMaxNum: 10000
         pushFailIsolateTimeInMills: 30000 # client isolation time if the message send failure
     sysid: 0000
   
   ```
   
   


-- 
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: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org


[GitHub] [incubator-eventmesh] Jackzeng1224 commented on issue #481: Use YAML file to store configuration

Posted by GitBox <gi...@apache.org>.
Jackzeng1224 commented on issue #481:
URL: https://github.com/apache/incubator-eventmesh/issues/481#issuecomment-892301381


   It can be revised and submitted to pr


-- 
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: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org


[GitHub] [incubator-eventmesh] qqeasonchen commented on issue #481: Use YAML file to store configuration

Posted by GitBox <gi...@apache.org>.
qqeasonchen commented on issue #481:
URL: https://github.com/apache/incubator-eventmesh/issues/481#issuecomment-891842483


   good suggestion


-- 
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: dev-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: dev-help@eventmesh.apache.org