You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2019/03/08 12:37:19 UTC

[GitHub] [incubator-skywalking] peng-yongsheng opened a new pull request #2335: Separation the remote gRPC server from the receiver gRPC server.

peng-yongsheng opened a new pull request #2335: Separation the remote gRPC server from the receiver gRPC server.
URL: https://github.com/apache/incubator-skywalking/pull/2335
 
 
   Please answer these questions before submitting pull request
   
   - Why submit this pull request?
   - [ ] Bug fix
   - [ ] New feature provided
   - [X] Improve performance
   
   - Related issues
   #2327 
   
   Receiver gRPC server is used to receive trace message from the agent. The remote gRPC server is used to receive L1 aggregated metric. But now they are mixed up. We don't known how high their respective loads are and whether they will interfere with each other.
   
   ## Module: receiver-share-server
   ### Default setting
   To be the bridge of the server hander in core module. The handlers in receiver module will add into the core server. The receiver and remote will share the same server.
   
   ### User-Defined
   Setting the config in application.yml. 
   
   #### If you want to make the jetty server in receiver module separate from the remote server, please turn on those config items, make sure of the port is different from the core
   restHost: ${SW_CORE_REST_HOST:0.0.0.0}
   restPort: ${SW_CORE_REST_PORT:22800}
   restContextPath: ${SW_CORE_REST_CONTEXT_PATH:/}
   
   #### If you want to make the gRPC server in receiver module separate from the remote server, please turn on those config items, make sure of the port is different from the core
   gRPCHost: ${SW_CORE_GRPC_HOST:0.0.0.0}
   gRPCPort: ${SW_CORE_GRPC_PORT:21800}

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services