Page History

...

There is no need to do additional configuration of plugin. It is sufficient to add ignite-direct-io.jar and Java Native Access (JNA) library jar (jna-xxx.jar) to classpath.

Plugin jar is available under optional libs folder:

apache-ignite-fabric-x.x.x-bin\libs\optional\ignite-direct-io\ignite-direct-io-x.x.x.jarHowever, disabling plugin’s function is possible through system Property.

When plugin is applied following messages will be produced

Configured plugins:
^-- Ignite Native I/O Plugin [Direct I/O]
^-- Copyright(C) Apache Software Foundation

 
Following message will be produced for successful setup:

Page size configuration for storage path [/work/db/node00-3a1415b8-aa54-4a63-a40a-c75ad48dd6b8]: 4096; Linux memory page size: 4096; Selected FS block size : 4096.
Selected FS block size : 4096
Direct IO is enabled for block IO operations on aligned memory structures. [block size = 4096, durable memory page size = 4096]

However, disabling plugin’s function is possible through system Property.

Enabled direct input-output mode allows Ignite to bypass the system cache pages Linux is fully conveys the Enabled direct input-output mode allows Ignite to bypass the system cache pages Linux is fully conveys the management of pages to Ignite.

WAL

 Direct I/O mode can't be enabled for Write Ahead Log files. However, when working with plugin, WAL manager applies advising Linux systems do not store the data of the file in page cache as they are not required.

...