aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cody Gibb (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-1900) Add RPC for rolling restarts
Date Fri, 17 Mar 2017 22:01:41 GMT

     [ https://issues.apache.org/jira/browse/AURORA-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cody Gibb updated AURORA-1900:
------------------------------
    Description: 
Currently, there are two options to execute a rolling restart, however both are undesirable
— either use the restartShards endpoint and implement batching client-side, or use startJobUpdate
with slightly modified task config so that a non-empty job diff forces an update. I propose
adding a new thrift RPC for launching a rolling restart, which is an interface around the
existing upgrade logic. Instead of requiring a TaskConfig and instanceCount, this restart
endpoint will only accept JobUpdateSettings and will simply launch an update with the currently
used task configuration. All of the existing job update RPCs will still be able to access
updates which were launched from this restart endpoint. This ensures restarts are available
in the UI and no additional storage changes are required.

Design doc here: https://docs.google.com/document/d/13xm23SfIRy5zMro82Ok8dRCsr7lKcC0_UUO_tJX21wQ/edit?usp=sharing

  was:Currently, there are two options to execute a rolling restart, however both are undesirable
— either use the restartShards endpoint and implement batching client-side, or use startJobUpdate
with slightly modified task config so that a non-empty job diff forces an update. I propose
adding a new thrift RPC for launching a rolling restart, which is an interface around the
existing upgrade logic. Instead of requiring a TaskConfig and instanceCount, this restart
endpoint will only accept JobUpdateSettings and will simply launch an update with the currently
used task configuration. All of the existing job update RPCs will still be able to access
updates which were launched from this restart endpoint. This ensures restarts are available
in the UI and no additional storage changes are required.


> Add RPC for rolling restarts
> ----------------------------
>
>                 Key: AURORA-1900
>                 URL: https://issues.apache.org/jira/browse/AURORA-1900
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Cody Gibb
>            Assignee: Cody Gibb
>
> Currently, there are two options to execute a rolling restart, however both are undesirable
— either use the restartShards endpoint and implement batching client-side, or use startJobUpdate
with slightly modified task config so that a non-empty job diff forces an update. I propose
adding a new thrift RPC for launching a rolling restart, which is an interface around the
existing upgrade logic. Instead of requiring a TaskConfig and instanceCount, this restart
endpoint will only accept JobUpdateSettings and will simply launch an update with the currently
used task configuration. All of the existing job update RPCs will still be able to access
updates which were launched from this restart endpoint. This ensures restarts are available
in the UI and no additional storage changes are required.
> Design doc here: https://docs.google.com/document/d/13xm23SfIRy5zMro82Ok8dRCsr7lKcC0_UUO_tJX21wQ/edit?usp=sharing



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message