Comments (8)
ptupitsyn
commented on June 13, 2024
Do those multiple applications use the same Ignite work directory?
…On Thu, 2 Nov 2023, 00:09 James P, ***@***.***> wrote:
We run Apache Ignite from several .Net 6 applications and have recently
upgrade from version 2.11 to 2.15. Post the upgrade we’ve noticed we
regularly get the following error in our logs:
[2023-10-30 09:58:17.859 +00:00 ERR 16] Failed to write class name to file [platformId=1, id=-480146029, clsName=System.Collections.Generic.List`1[[<OneOfMyDomainModels>]], file=D:\Software\Ignite\apache-ignite-slim-2.15.0-bin\work\db\marshaller\-480146029.classname1] { nativeErrorInfo: "java.nio.file.AccessDeniedException: D:\Software\Ignite\apache-ignite-slim-2.15.0-bin\work\db\marshaller\-480146029.classname1-621646209.tmp -> D:\Software\Ignite\apache-ignite-slim-2.15.0-bin\work\db\marshaller\-480146029.classname1
at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83)
at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at sun.nio.fs.WindowsFileCopy.move(WindowsFileCopy.java:301)
at sun.nio.fs.WindowsFileSystemProvider.move(WindowsFileSystemProvider.java:291)
at java.nio.file.Files.move(Files.java:1395)
at org.apache.ignite.internal.MarshallerMappingFileStore.writeMapping(MarshallerMappingFileStore.java:103)
at org.apache.ignite.internal.MappingStoreTask.run(MappingStoreTask.java:57)
at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7487)
at org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:649)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
We have the appropriate permissions to the folder it’s trying to write to.
I see an issue was raised and fixed (
https://issues.apache.org/jira/browse/IGNITE-3239) back in 2016 so I
wonder if it’s a regression related to that?
—
Reply to this email directly, view it on GitHub
<#11025>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACTKXDFVI6VVWQMIJOHCEWLYCLCBPAVCNFSM6AAAAAA6Z6NUN2VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3TGMJYGMZDCOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
from ignite.
JamesPDev
commented on June 13, 2024
Each project has a package reference for Ignite but the IGNITE_HOME environment variable specifying where to find Ignite is the same for all apps. Is that an invalid setup? Should each app that needs to talk to our distributed cache have its own work directory configured? (We're not using native persistence but we are writing to our own DB via CacheStores)
from ignite.
ptupitsyn
commented on June 13, 2024
- If you have a package reference, you don't need a separate binary distribution (
apache-ignite-slim-2.15.0-bin). - Yes, every Ignite node (in your case - app) should have it's own work directory. That is achieved naturally with a package reference and without an explicit
IGNITE_HOME.
from ignite.
JamesPDev
commented on June 13, 2024
The reason for having a separate installation rather than just relying on the nuget package reference is mainly historic as we originally ran into issues with jar files not being copied (fixed in #6954 I believe). We also needed to access the REST API. Can you confirm the REST API is accessible when using the nuget packages?
Also, out of interest, can you explain why the error we see has only started to occur with the new version of Ignite?
from ignite.
ptupitsyn
commented on June 13, 2024
Can you confirm the REST API is accessible when using the nuget packages?
Kind of. You'll have to get ignite-rest-http module separately (from Maven or from the full binary distribution), put it somewhere, and provide the path to it in IgniteConfiguration.JvmClasspath.
why the error we see has only started to occur with the new version of Ignite
It may be a coincidence. The error is caused by multiple instances of Ignite trying to access the same file at the same time.
from ignite.
JamesPDev
commented on June 13, 2024
Ok, one last thing, are there any plans to progress https://issues.apache.org/jira/plugins/servlet/mobile#issue/IGNITE-3275 as we still have the webconsole running. Thanks.
from ignite.
ptupitsyn
commented on June 13, 2024
Unfortunately, there are no plans for that ticket.
from ignite.
JamesPDev
commented on June 13, 2024
Thanks for your help.
from ignite.
Related Issues (20)
- Issues with listening on Events as a client node HOT 1
- Remove polyfill packages
- In ignite2.13.0, the number of cache hit times and the number of cache miss times are incorrectly calculated.
- Ignite Thin client Index Query is not working with Ignite Server and client version : 2.16.0 HOT 13
- Continuous query using NodeJS client HOT 2
- we need go client sdk HOT 11
- Is there any plan to support window aggregation in Calcite Query Engine
- Is Ignite 2.16.0 impacted by CVE-2024-22243 ? HOT 1
- IBinarizable : Mapping complex objects HOT 9
- I am running a 3-node external cluster, but I find that the memory is growing slowly. By checking the top, I can see that the buffer/cache has been growing slowly and has not been released. What is the reason for this
- Ignite 2.16 is incompatible with recent h2database, h2 must be shaded HOT 2
- Ignite Getting started guide for Java missing something (gives errors) HOT 2
- Question: Ignite client instance HOT 8
- Support Apache Arrow serialization transfer
- How do I reset the expiration time after ignite sets the expiration time
- In ignite2.16.0 and jdk21, run task with lambda expression, it can not run.
- CPU goes crazy in ignite server
- Spring boot 3 support for Ignite
- Question: CacheStore Configuration using DDL HOT 3
- Question: Apache ignite on kubernetes with Proxy HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ignite.