-
Notifications
You must be signed in to change notification settings - Fork 150
MC-13864: Consumer always read config from memory #91
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e04c2b1
MC-13864: Consumer always read config from memory
vzabaznov 69e1a53
Update poison-pill.md
vzabaznov 1e7ee95
Update poison-pill.md
vzabaznov b05689a
Update poison-pill.md
vzabaznov 31062a6
MC-13864: Consumer always read config from memory
vzabaznov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| ## Glossary | ||
|
|
||
| poison pill | ||
| : message in Data Storage that signals that consumer should die | ||
vzabaznov marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ### Overview | ||
|
|
||
| Right now our consumer depends on config/objects in-memory state. After application was bootstrapped it initialize a lot of object that are always kept in memory after first load - config, websites, etc.., since our consumers are long-living and their live time limited only by message count it leads to wrong im-memory config/objects states and we need to introduce the way to reinit them. | ||
vzabaznov marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ### Design | ||
|
|
||
| Before process new message consumer should ask Data Storage if there are poison pill for him. If yes, consumer dies and next cron:run will start new instance of consumer. | ||
vzabaznov marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
vzabaznov marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| #### Acceptance Criteria Fulfillment | ||
|
|
||
| 1. If consumer takes message to process after poison pill was placed, consumer must be reinited | ||
|
|
||
| #### Extension Points and Scenarios | ||
|
|
||
| We will put poison pill into Data Storage based on common Magento extension points | ||
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.
Uh oh!
There was an error while loading. Please reload this page.