At the individual ZFS level, you can control what data is cached in the ARC
and L2ARC via the primarycache and secondarycache settigns:
primarycache=all|none|metadata
Controls what is cached in the primary cache (ARC). If this property
is set to all, then both user data and metadata is cached. If this
property is set to none, then neither user data nor metadata is
cached.
If this property is set to metadata, then only metadata is cached.
The
default value is all.
secondarycache=all|none|metadata
Controls what is cached in the secondary cache (L2ARC). If this
property is set to all, then both user data and metadata is cached.
If
this property is set to none, then neither user data nor metadata is
cached. If this property is set to metadata, then only metadata is
cached. The default value is all.
So, if you don't want data from a given ZFS 'polluting' the L2ARC, you can
change it's secondarycache setting to metadata or none depending on your
preferences.
Josh C
Joshua Coombs
GWI
*office* 207-494-2140
www.gwi.net
On Tue, May 30, 2017 at 7:11 AM, Alexander Pyhalov <[email protected]> wrote:
> Hello.
> I have a question on l2arc supporting algorithms. Precisely, if I have
> some data in l2arc and now large sequential read comes, does it mean that
> l2arc will be rewritten? For example, if I have 200GB L2ARC and one reads
> 1TB of data, does it mean that after this L2ARC is filled with this
> (perhaps, rarely used) data? Is there any way to protect from this
> (perhaps, somehow marc some data to avoid its eviction from cache)?
> --
> Best regards,
> Alexander Pyhalov,
> system administrator of Southern Federal University IT department
------------------------------------------
illumos-discuss
Archives:
https://illumos.topicbox.com/groups/discuss/discussions/T24178558a3ef35b5-Md93a7a4ad3464f35a33a0277
Powered by Topicbox: https://topicbox.com
