-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG : neo4j looses triples, running partial commits leads to errors #297
Comments
Reference : neo4j/neo4j#13039 |
can someone please help with this issue thanks |
hi @AnkurArohi apologies for the late reply. Thanks. |
@jbarrasa
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After the neo4j starts properly and the inital CYPHER queries are worked upon there is a partial transaction rolled back issue and the tuples are getting lost.
This leads to the exception and the task which the neo4j was configured to do is incomplete.
With the version 4.4.4 we didnt face this issue
Steps to reproduce
Start the docker container with the correct settings for the neo4j DB and the following plugins
Neo4j-Apoc: 5.3.1-extended,
apoc-5.3.0-core.jar,
neosemantics-5.1.0.0.jar
and the following environment vars
server.directories.data=/dbdata
server.jvm.additional=-Dlog4j2.formatMsgNoLookups=true
server.jvm.additional=-Dlog4j2.disable.jmx=true
server.jvm.additional=-XX:+ExitOnOutOfMemoryError
server.directories.plugins=/plugins
server.config.strict_validation.enabled=false
server.bolt.advertised_address=:7687
server.bolt.listen_address=:7687
dbms.security.procedures.unrestricted=algo.,apoc.
db.tx_log.rotation.retention_policy=false
server.memory.heap.initial_size=10g
server.memory.heap.max_size=10g
server.memory.pagecache.size=4g
Expected behavior
Actual behavior
Tuples are being lost and exception is being raised
Additionally, include (as appropriate) log-files, stacktraces, and other debug output.
2023-02-09 08:30:54.523+0000 ERROR Problems when running partial commit. Partial transaction rolled back. 3887 triples lost. │
│ org.neo4j.kernel.DeadlockDetectedException: ForsetiClient[transactionId=676, clientId=20] can't acquire UpdateLock{owners=ForsetiClient[transactionId=676, clientId=20], ForsetiClient[transactionId=650, clien │
│ Wait list:SharedLock[ │
│ Client[676] waits for [ForsetiClient[transactionId=650, clientId=22]], │
│ Client[650] waits for [ForsetiClient[transactionId=676, clientId=20]]] │
│ at org.neo4j.kernel.impl.locking.forseti.ForsetiClient.waitFor(ForsetiClient.java:839) ~[neo4j-lock-5.3.0.jar:5.3.0] │
│ at org.neo4j.kernel.impl.locking.forseti.ForsetiClient.tryUpgradeToExclusiveWithShareLockHeld(ForsetiClient.java:787) ~[neo4j-lock-5.3.0.jar:5.3.0] │
│ at org.neo4j.kernel.impl.locking.forseti.ForsetiClient.tryUpgradeSharedToExclusive(ForsetiClient.java:750) ~[neo4j-lock-5.3.0.jar:5.3.0] │
│ at org.neo4j.kernel.impl.locking.forseti.ForsetiClient.acquireExclusive(ForsetiClient.java:339) ~[neo4j-lock-5.3.0.jar:5.3.0] │
│ at org.neo4j.kernel.impl.api.parallel.ParallelAccessCheck$1.acquireExclusive(ParallelAccessCheck.java:62) ~[neo4j-kernel-5.3.0.jar:5.3.0] │
│ at org.neo4j.internal.recordstorage.RecordStorageLocks.acquireNodeLabelChangeLock(RecordStorageLocks.java:174) ~[neo4j-record-storage-engine-5.3.0.jar:5.3.0] │
│ at org.neo4j.kernel.impl.newapi.Operations.nodeAddLabel(Operations.java:382) ~[neo4j-kernel-5.3.0.jar:5.3.0] │
│ at org.neo4j.kernel.impl.core.NodeEntity.addLabel(NodeEntity.java:317) ~[neo4j-kernel-5.3.0.jar:5.3.0] │
│ at n10s.rdf.load.DirectStatementLoader.lambda$runPartialTx$1(DirectStatementLoader.java:63) ~[neosemantics-5.1.0.0.jar:5.1.0.0] │
│ at java.lang.Iterable.forEach(Iterable.java:75) ~[?:?] │
│ at
The text was updated successfully, but these errors were encountered: