aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Cohen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1195) Replicate dangerous update warning for scheduler driven updates
Date Thu, 12 Mar 2015 21:08:38 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359418#comment-14359418
] 

Joshua Cohen commented on AURORA-1195:
--------------------------------------

This seems like it should be part of the scheduler, but what would the behavior be if we implemented
this within the scheduler? Would the update fail requiring the user to re-run the client command,
passing some sort of force/acknowledgement arg to confirm the dangerous behavior?

> Replicate dangerous update warning for scheduler driven updates
> ---------------------------------------------------------------
>
>                 Key: AURORA-1195
>                 URL: https://issues.apache.org/jira/browse/AURORA-1195
>             Project: Aurora
>          Issue Type: Task
>          Components: Client, Scheduler
>            Reporter: Joshua Cohen
>
> The current client driven updates provide a warning if an update will impact a significant
number of shards. The scheduler driven updates do not provide a similar warning. We should
figure out the best way to offer the same safety for scheduler driven updates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message