You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@linkis.apache.org by "peacewong (via GitHub)" <gi...@apache.org> on 2023/03/06 12:11:23 UTC

[GitHub] [linkis] peacewong opened a new issue, #4325: [Feature][LinkisManager] Add task fixed engine label

peacewong opened a new issue, #4325:
URL: https://github.com/apache/linkis/issues/4325

### Search before asking

- [X] I had searched in the [issues](https://github.com/apache/linkis/issues) and found no similar feature requirement.

### Problem Description

Now when Linksi tasks are submitted, EngineConn is created or reused based on tags, and EngineConn among multiple tasks is random. However, for the existence of multi-tasks that need to be able to meet the dependencies of the tasks, execution on the same EngineConn (hereinafter referred to as EC) cannot be well supported.

### Description

1. Overview
The purpose of this request: Add a new FixedEngineConnLabel in multiple personal tasks to meet the purpose of fixing the same EC for multiple tasks.
2. Overall Design
The overall design idea of multi-task fixed EC is as follows:
The task carries a unique id (FixedEngineConnLabel), which is generated by the caller and is used to mark the corresponding instance of Linkis with this unique identifier.
If there is no session available to submit the task, create it. If it exists and is available, the EC instance with the corresponding id will be reused. Generated sessions will not be reused by other task sessions
Provide an EC query interface to obtain the mapping relationship between all current ECs and ids. The caller can choose a suitable EC instance, modify or add FixedEngineConnLabel
After the task is submitted to the EC for execution, it will face the EC instance information with the task in the task information, and you can use this to query the mapping relationship
Abnormal situation: The fixed instance does not exist or is in a busy state. The task will be executed normally, but a new EC instance mapping will be generated. The caller can judge whether the EC instance information has been switched through the instance information of the task information.
If you do not want to reuse any EC, you can use ReuseExclusionLabel to exclude labels, you can add multiple instances, or can add * to exclude all EC instances.

### Use case

_No response_

### Solutions

_No response_

### Anything else

_No response_

### Are you willing to submit a PR?

- [X] 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: notifications-unsubscribe@linkis.apache.org.apache.org

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

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@linkis.apache.org
For additional commands, e-mail: notifications-help@linkis.apache.org

[GitHub] [linkis] casionone closed issue #4325: [Feature][LinkisManager] Add task fixed engine label

Posted by "casionone (via GitHub)" <gi...@apache.org>.

casionone closed issue #4325: [Feature][LinkisManager] Add task fixed engine label
URL: https://github.com/apache/linkis/issues/4325


-- 
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: notifications-unsubscribe@linkis.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@linkis.apache.org
For additional commands, e-mail: notifications-help@linkis.apache.org

[GitHub] [linkis] github-actions[bot] commented on issue #4325: [Feature][LinkisManager] Add task fixed engine label

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.

github-actions[bot] commented on issue #4325:
URL: https://github.com/apache/linkis/issues/4325#issuecomment-1456022368

   ## :blush:  Welcome to the Apache Linkis community!!
   We are glad that you are contributing by opening this issue.
   
   Please make sure to include all the relevant context.
   We will be here shortly.
   
   If you are interested in contributing to our website project, please let us know!
   You can check out our contributing guide on
    :point_right:  [How to Participate in Project Contribution](https://linkis.apache.org/community/how-to-contribute).
   
   
   ### Community
   
   |WeChat Assistant|WeChat Public Account|
   |-|-|
   |<img src="https://linkis.apache.org/Images/wedatasphere_contact_01.png" width="128"/>|<img src="https://linkis.apache.org/Images/gzh_01.png" width="128"/>|
   
   
   ### Mailing Lists
   |Name|Description|Subscribe|Unsubscribe|Archive|
   |:-----|:--------|:------|:-------|:-----|
   | [dev@linkis.apache.org](mailto:dev@linkis.apache.org) | community activity information | [subscribe](mailto:dev-subscribe@linkis.apache.org) | [unsubscribe](mailto:dev-unsubscribe@linkis.apache.org) | [archive](http://mail-archives.apache.org/mod_mbox/linkis-dev) |


-- 
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: notifications-unsubscribe@linkis.apache.org

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


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@linkis.apache.org
For additional commands, e-mail: notifications-help@linkis.apache.org