>From what I understand, now there is a new interface Configurable that exposes >the config parameters. In this case if you look at the >CapacityManagerImpl.java, there is a method getCongigKeys() that return the >config parameters. During MS startup all these are automatically populated in >the db. Looks like pool.storage.capacity.disablethreshold was missed out from >the list. Add it in the list and it should be available.
On 08-Nov-2013, at 4:14 AM, Alena Prokharchyk <alena.prokharc...@citrix.com> wrote: > I've run into the problem in master where I can't deploy the VM due to > insufficient capacity: > > 2013-11-07 14:21:20,439 DEBUG [c.c.s.StorageManagerImpl] > (Job-Executor-27:ctx-e5d8814d ctx-e5375ad7) Insufficient space on pool: 1 > since its usage percentage: 4.875950712239125 has crossed the > pool.storage.capacity.disablethreshold: 0.85 > > But there is no way to change "pool.storage.capacity.disablethreshold" as > this parameter is hardcoded in CapacityManager, and you can't change its > value. > > Alex, seems you were the last person who modified it. Before we used to keep > all capacity thresholds in global config table, can you explain how it works > now? > > commit 6e8ca994660afc468530944542e232596e8f1176 > Author: Alex Huang <alex.hu...@citrix.com> > Date: Tue Aug 27 17:33:24 2013 -0700 > > Got all of the config stuff out of the way > > -alena.
