Nimbus service goes into infinite loop when requesting a VM that has needs more memory than available on any node #26

Closed
priteau opened this Issue Jan 29, 2011 · 3 comments

Comments

Projects
None yet
2 participants
Owner

priteau commented Jan 29, 2011

Nimbus service goes into infinite loop when requesting a VM that has needs more memory than available on any node... but only for some host/guest memory values.

I can repeat the bug with these values: nodes have 3072 MB of memory, and the VM is requested with 3584 MB.
This happens both with the cloud client and the EC2 API.

Excerpt from the logs:

2011-01-29 23:04:38,610 DEBUG defaults.DefaultSlotManagement [ServiceThread-26,reserveSpace:402] request for 1 space(s) with mem = 3584
2011-01-29 23:04:38,613 ERROR defaults.ResourcepoolUtil [ServiceThread-26,getAvailableEntries:267] No resource is available for this request (based on memory).
2011-01-29 23:04:38,614 INFO async.AsyncRequestManagerImpl [ServiceThread-26,releaseSpace:325] 3584MB RAM have to be freed to give space to higher priority requests

(repeated many times)

interlaced with this:

2011-01-29 23:04:38,676 WARN async.AsyncRequestManagerImpl [ServiceThread-26,releaseSpace:331] [NIMBUS-EVENT]: Asynchronous requests are consuming 0MB RAM , but AsyncRequestManager was requested to free 3584MB RAM. Freeing 0MB RAM.

Member

timf commented Feb 3, 2011

Closed by 31c22be, problem was expectation of fixed size instance types clashed with arbitrary sized memory requests from the alternate protocol

Member

timf commented Feb 3, 2011

Thankyou for finding/reporting this and especially for making it easy to reproduce, that made it easy to write a test and figure it out.

Owner

priteau commented Feb 3, 2011

Thanks for fixing it!

timf added a commit that referenced this issue Jun 13, 2011

Add a separate condition that checks for a completely infeasible memo…
…ry request. This greatly reduces the number of corner cases related to GH-26

timf added a commit to pdmars/nimbus that referenced this issue Oct 13, 2011

Closes GH-26, problem was expectation of fixed size instance types c…
…lashed with arbitrary sized memory requests from the alternate protocol

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment