-
Notifications
You must be signed in to change notification settings - Fork 187
Support a configurable delay for task shuffles. #1770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
return ( | ||
isLongRunning(task) | ||
&& !configuration.getDoNotShuffleRequests().contains(task.getRequestId()) | ||
&& (TimeUnit.MILLISECONDS.toMinutes(System.currentTimeMillis() - task.getStartedAt()) > configuration.getMinutesBeforeNewTaskEligibleForShuffle()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should go by the task running timestamp instead? Take out any delay that may have been caused by mesos/singularity that way
@@ -15,6 +15,8 @@ | |||
import java.util.concurrent.atomic.AtomicLong; | |||
import java.util.stream.Collectors; | |||
|
|||
import javax.ws.rs.HEAD; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
leftover from merge conflict? (intellij auto import stuff?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch.
🚢 |
No description provided.