fix the config yarn.queue not take effect bug#3
Closed
velee wants to merge 1 commit intoapache:0.9.0from
Closed
Conversation
Contributor
|
can you open a JIRA for this if this is still an issue for you? Because usually we do not take care of the pull requests. Thank you. Basic step is listed here http://samza.apache.org/contribute/rules.html . Thank you! |
Contributor
|
@velee Your patch has been committed in SAMZA-767. Thanks! |
pdu-mn1
added a commit
to pdu-mn1/samza
that referenced
this pull request
Aug 6, 2018
Add static maps from tableId -> table/callback executors to share executors among tasks in the same container.
khandelwal-ayush
pushed a commit
to khandelwal-ayush/samza
that referenced
this pull request
Jun 12, 2024
…ployment while job is already running from previous deployment. (apache#3) Live deployment - reduce job downtime by spawning a new AM for new deployment while job is already running from previous deployment. This changeset introduces logic for the live deployment feature in which we spawn a new AM while the existing deployment of the job is still running. However we want to make sure that at any given time there are only one set of containers running for the job. The new AM comes up and when it is ready to spawn up the containers, it kills existing deployment of the job (which would kill existing AM and existing containers for the job), waits for it to be moved to KILLED state and then continues with requesting containers from RM. This feature is behind a flag which is based on config of the job. Other changes in this changeset include - 1: change in clientHelper code so that it returns active app ids for a job in sorted order based on start time. Earlier this method would have returned only one job always, since there is only on job in running state. However now it can return two when the job is being deployed. 2: Small refactor in SamzaYarnAppMasterService code to move “write of AM info on coordinator stream” to a new method and use that method if the live deployment feature flag is not set, which means there is no change in flow if "live deployment" flag is not set. If live deployment flag is set, then we write AM info on coordinator stream after the existing AM and all containers are killed. --------- Co-authored-by: Rahul Yadav <rahyadav@rahyadav-ld2.linkedin.biz>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.