cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Tutkowski <mike.tutkow...@solidfire.com>
Subject Re: How is this working?
Date Mon, 05 May 2014 15:42:27 GMT
My storage plug-in actually uses a custom host listener, so I have not
encountered this issue.

I don't remember off hand if it was in 4.2 or 4.3, but at some point
someone changed the storage_pool table's available_bytes column to be
used_bytes.

It looks like this code you reference was missed.


On Mon, May 5, 2014 at 4:35 AM, Koushik Das <koushik.das@citrix.com> wrote:

> I came across this code snippet in hostConnect() method in
> DefaultHostListener.java. Look at the line where the used bytes is set on
> the poolVO. This looks like a serious bug. Looking at the history this code
> has been there since a year. Has anyone encountered any issues with primary
> storage capacity?
>
> ModifyStoragePoolAnswer mspAnswer = (ModifyStoragePoolAnswer)answer;
> …..
> StoragePoolVO poolVO = this.primaryStoreDao.findById(poolId);
> poolVO.setUsedBytes(mspAnswer.getPoolInfo().getAvailableBytes());
> poolVO.setCapacityBytes(mspAnswer.getPoolInfo().getCapacityBytes());
> primaryStoreDao.update(pool.getId(), poolVO);
>
>
> -Koushik
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message