Details
-
Bug
-
Resolution: Fixed
-
Critical
-
2.1.0
-
Security Level: Public
-
None
-
5
-
CB Bucket - 22/Jul/13
Description
Under the current design, ep engine stops warmup (therefore data loading) and enable data traffic immediately after the data loading phase based on access log is complete.
This may not be an optimal way of completing warmup because the access log may not have enough key-value entries to fill up the memory upto the low-watermark. We should allow warmup continues in the background to fill up the memory even after the data loading based on access log is complete. However, enable data traffic immediately after the data loading though.
Attachments
Issue Links
- duplicates
-
MB-7818 Warmup to continue if the initial access log is quite small or all expired
- Closed
For Gerrit Dashboard: MB-8581 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
27653,1 | MB-8581 1. Fixed a bug that prevent warmup to load access log 2. Added a loadingData step after loadingAccessLog to meet warmup watermarks. In the loadingAccessLog phase we save the keys of the items that loaded to hashtable and pass it to the loadingData phase. We then use it to only load items that are not already loaded earlier. | 2.1.1 | ep-engine | Status: ABANDONED | -1 | 0 |
27953,1 | MB-8581 | 2.1.1 | ep-engine | Status: ABANDONED | -1 | 0 |
28038,3 | MB-8581 Continue warmup after loading access_log. | 2.1.1 | ep-engine | Status: MERGED | +2 | +1 |
28141,2 | Revert "MB-8581 Continue warmup after loading access_log." | 2.1.1 | ep-engine | Status: MERGED | +2 | +1 |
28152,2 | Revert "Revert "MB-8581 Continue warmup after loading access_log."" | 2.1.1 | ep-engine | Status: MERGED | +2 | +1 |
28276,2 | Merge branch '2.1.1' | master | ep-engine | Status: MERGED | +2 | +1 |