You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uniffle.apache.org by "jerqi (via GitHub)" <gi...@apache.org> on 2023/03/14 15:26:27 UTC

[GitHub] [incubator-uniffle] jerqi opened a new issue, #719: [Subtask] [Netty] Optimize allocation strategy

jerqi opened a new issue, #719:
URL: https://github.com/apache/incubator-uniffle/issues/719

   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before asking
   
   - [X] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues) and found no similar issues.
   
   
   ### Describe the subtask
   
   When we use Netty servers., there are Netty servers and Grpc servers at the same time at first in our production. We should allocate different servers to client according to ClientType. We allocate Netty servers to `GrpcNetty` client. We allocate Grpc servers to `Grpc` client.
   
   ### Parent issue
   
   #133
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a 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@uniffle.apache.org.apache.org

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


[GitHub] [incubator-uniffle] jerqi closed issue #719: [Subtask] [Netty] Optimize allocation strategy

Posted by "jerqi (via GitHub)" <gi...@apache.org>.
jerqi closed issue #719: [Subtask] [Netty] Optimize allocation strategy
URL: https://github.com/apache/incubator-uniffle/issues/719


-- 
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@uniffle.apache.org

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


[GitHub] [incubator-uniffle] jerqi commented on issue #719: [Subtask] [Netty] Optimize allocation strategy

Posted by "jerqi (via GitHub)" <gi...@apache.org>.
jerqi commented on issue #719:
URL: https://github.com/apache/incubator-uniffle/issues/719#issuecomment-1468317004

   @smallzhongfeng Could you help solve this issue?


-- 
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@uniffle.apache.org

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


[GitHub] [incubator-uniffle] jerqi commented on issue #719: [Subtask] [Netty] Optimize allocation strategy

Posted by "jerqi (via GitHub)" <gi...@apache.org>.
jerqi commented on issue #719:
URL: https://github.com/apache/incubator-uniffle/issues/719#issuecomment-1469195560

   > So future servers only need to reserve one port, right ?
   
   They will reserve two ports. But if we enable Netty, we will only use Netty to transfer data. 


-- 
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@uniffle.apache.org

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


[GitHub] [incubator-uniffle] smallzhongfeng commented on issue #719: [Subtask] [Netty] Optimize allocation strategy

Posted by "smallzhongfeng (via GitHub)" <gi...@apache.org>.
smallzhongfeng commented on issue #719:
URL: https://github.com/apache/incubator-uniffle/issues/719#issuecomment-1469193778

   So future servers only need to reserve one port, right ?


-- 
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@uniffle.apache.org

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