-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[New Scheduler]Add CreationJobManager #5116
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
[New Scheduler]Add CreationJobManager #5116
Conversation
12e8fff
to
1700c8d
Compare
Codecov Report
@@ Coverage Diff @@
## master #5116 +/- ##
==========================================
- Coverage 81.86% 75.75% -6.12%
==========================================
Files 225 227 +2
Lines 11423 11528 +105
Branches 501 497 -4
==========================================
- Hits 9352 8733 -619
- Misses 2071 2795 +724
Continue to review full report at Codecov.
|
|
||
private val topicPrefix = loadConfigOrThrow[String](ConfigKeys.kafkaTopicsPrefix) | ||
private val topic = s"${topicPrefix}creationAck${schedulerInstanceId.asString}" | ||
private val maxActiveAcksPerPoll = 128 |
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.
In Scheduler.scala, this value is configurable.
Can we make it configurable as well?
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.
it seems other places are also hardcoded
dataManagementService: ActorRef)(implicit actorSystem: ActorSystem, logging: Logging) | ||
extends Actor { | ||
private implicit val ec: ExecutionContext = actorSystem.dispatcher | ||
private val baseTimeout = loadConfigOrThrow[Int](ConfigKeys.schedulerInProgressJobRetentionSecond).seconds |
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.
For time configuration, it is better to change it to loadConfigOrThrow[FiniteDuration]
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.
great catch, I will update
LGTM with some small suggestions |
732e6e2
to
219c069
Compare
Description
This module records container creation using a
CreationId
, when a new container creation request is created, one entry with an uniqueCreationId
will be created and saved in to ETCD, and will be deleted when creation is finished(or timeout waiting for creation complete ack).So that a
MemoryQueue
can query how many containers are being created from ETCD and then do containers scheduling based on this value.It can also help to trace/debug the procedure of a container creation.
Related issue and scope
My changes affect the following components
Types of changes
Checklist: