3 Commits (9a761b16c1558106800222dbc52f6ab03c40c64c)

Author	SHA1	Message	Date
Hemant Kumar	a16ee2f514	Implement LRU for AWS device allocator ... In AWS environment when attach fails on the node lets not use device from the pool. This makes sure we don't reuse recently freed devices	2017-04-19 16:52:57 -04:00
Hemant Kumar	73370239d2	Fix AWS device allocator to only use valid device names ... According to http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html we can only use /dev/xvd[b-c][a-z] as device names - so we can only allocate upto 52 ebs volumes on a node.	2017-02-14 22:33:26 -05:00
Jan Safranek	65f6bcb927	AWS: Add sequential allocator for device names. ... On AWS, we should not reuse device names as long as possible, see https://aws.amazon.com/premiumsupport/knowledge-center/ebs-stuck-attaching/ "If you specify a device name that is not in use by EC2, but is being used by the block device driver within the EC2 instance, the attachment of the EBS volume does not succeed and the EBS volume is stuck in the attaching state." This patch adds a device name allocator that tries to find a name that's next to the last used device name instead of using the first available one. This way we will loop through all device names ("xvdba" .. "xvdzz") before a device name is reused.	2016-12-15 17:22:19 +01:00