and placing it in the same folder as the deployed
clcgridworker script, that is, within the folder specified in the Path to CLC Grid Worker field of the grid preset. Each grid preset can have its own
Options that may be of particular use for grid workers include:
-Djava.io.tmpdir=<path>Set the location where temporary files should be put.
-Dskip_lazytmp_cleanup=<boolean>When set to true,
-Dskip_lazytmp_cleanup=true, the grid worker will not attempt to clean up temporary data from previous analyses that, for whatever reason, were not cleared up previously. This option is intended for systems where temp areas for grid nodes are not local and the specified shared temp location is on a file system that does not support global file locking. As we highly recommend that temporary data areas are local, this option should rarely be of use.
For example, if a
clcgridworker.vmoptions was created, containing the following line, it would, for the CLC Grid Worker specified in a given preset, set a temporary directory for the grid nodes, overriding the default that would otherwise apply:
Understanding memory settings, need to be overridden, then we recommend this be done using the CLC Grid Worker memory limit field of the grid preset configuration, as described in Configure grid presets. In earlier versions of CLC Server, a line of the form
-Xmx<value>may have been added to a
clcgridworker.vmoptionsfile to specify this limit. If setting limits in a grid preset, any
clcgridworker.vmoptionsfiles, should be removed, as values in these files will override those in a grid preset.