> Memory usage is still quite high here even with a large onode cache!
> Are you using erasure coding? I recently was able to reproduce a bug in
> bluestore causing excessive memory usage during large writes with EC,
> but have not tracked down exactly what's going on yet.
>
> Mark
No, this is
On Wed, 18 Oct 2017, Wido den Hollander wrote:
> > Op 18 oktober 2017 om 13:48 schreef Hans van den Bogert
> > :
> >
> >
> > Indeed it shows ssd in the OSD's metadata.
> >
> > "bluestore_bdev_type": "ssd",
> >
> >
> > Then I misunderstood the role of the device class in CRUSH, I expected
> Op 18 oktober 2017 om 13:48 schreef Hans van den Bogert
> :
>
>
> Indeed it shows ssd in the OSD's metadata.
>
> "bluestore_bdev_type": "ssd",
>
>
> Then I misunderstood the role of the device class in CRUSH, I expected the
> OSD would actually set its settings according to the CRUSH d
Memory usage is still quite high here even with a large onode cache!
Are you using erasure coding? I recently was able to reproduce a bug in
bluestore causing excessive memory usage during large writes with EC,
but have not tracked down exactly what's going on yet.
Mark
On 10/18/2017 06:48 A
Indeed it shows ssd in the OSD's metadata.
"bluestore_bdev_type": "ssd",
Then I misunderstood the role of the device class in CRUSH, I expected the
OSD would actually set its settings according to the CRUSH device class.
I'll try to force the OSDs to behave like HDDs and monitor the memory
> Op 18 oktober 2017 om 11:41 schreef Hans van den Bogert
> :
>
>
> Hi All,
>
> I've converted 2 nodes with 4 HDD/OSDs each from Filestore to Bluestore. I
> expected somewhat higher memory usage/RSS values, however I see, imo, a
> huge memory usage for all OSDs on both nodes.
>
> Small snippe
