Out of disk space? The directory /tmp/temp_ignite_libs doesn’t exist?
> On 3 Nov 2021, at 11:26, Ibrahim Altun <ibrahim.al...@segmentify.com> wrote:
>
> Hi,
>
> We've been using urideploy extension for a long time without any problems,
> but today all of a sudden we seeing following logs on cluster logs;
>
> [2021-11-03T10:46:20,972][ERROR][grid-uri-scanner-#2-#42][UriDeploymentScannerManager]
> Error saving file: cacheentryprocessor-0.0.1-SNAPSHOT.jar
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> ~[?:1.8.0_281]
> at java.io.File.createTempFile(File.java:2024) ~[?:1.8.0_281]
> at
> org.apache.ignite.spi.deployment.uri.scanners.UriDeploymentScannerManager.createTempFile(UriDeploymentScannerManager.java:189)
> ~[ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.file.UriDeploymentFileScanner$URIContext.handleFile(UriDeploymentFileScanner.java:249)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.file.UriDeploymentFileScanner$URIContext.access$200(UriDeploymentFileScanner.java:135)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.file.UriDeploymentFileScanner$URIContext$1.handle(UriDeploymentFileScanner.java:178)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.GridDeploymentFolderScannerHelper.scanFolder(GridDeploymentFolderScannerHelper.java:49)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.GridDeploymentFolderScannerHelper.scanFolder(GridDeploymentFolderScannerHelper.java:52)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.file.UriDeploymentFileScanner$URIContext.scan(UriDeploymentFileScanner.java:183)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.file.UriDeploymentFileScanner$URIContext.access$000(UriDeploymentFileScanner.java:135)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.file.UriDeploymentFileScanner.scan(UriDeploymentFileScanner.java:73)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at
> org.apache.ignite.spi.deployment.uri.scanners.UriDeploymentScannerManager$1.body(UriDeploymentScannerManager.java:115)
> [ignite-urideploy-2.10.0.jar:2.10.0]
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58)
> [ignite-core-2.10.0.jar:2.10.0]
>
>
> here is the configuration we use;
> <!-- Enable deploymentSpi, /usr/share/apache-ignite/libs/segmentify
> directory will be checked every 5 seconds for changed files-->
> <property name="deploymentSpi">
> <bean
> class="org.apache.ignite.spi.deployment.uri.UriDeploymentSpi">
> <property name="temporaryDirectoryPath"
> value="/tmp/temp_ignite_libs"/>
> <property name="uriList">
> <list>
>
> <value>file://freq=5000@localhost/usr/share/apache-ignite/libs/segmentify/</value>
> </list>
> </property>
> </bean>
> </property>
>
>
> The same configuration is used in the development environment and no problems
> there so far.
>
> Any thoughts?
>
>
> --
> <https://www.segmentify.com/>
> İbrahim Halil Altun
> Senior Software Engineer
>
> +90 536 3327510 • segmentify.com → <https://www.segmentify.com/>
> UK • Germany • Turkey
>
> <https://www.segmentify.com/ecommerce-growth-show>
> <https://www.g2.com/products/segmentify/reviews>
