-
Notifications
You must be signed in to change notification settings - Fork 495
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes #2295: Add documentation to indicate that the procedures are no…
…t detected by MemoryTracker (#2296)
- Loading branch information
Showing
3 changed files
with
15 additions
and
0 deletions.
There are no files selected for viewing
Empty file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 13 additions & 0 deletions
13
docs/asciidoc/modules/ROOT/pages/general-considerations/index.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
[[general-considerations]] | ||
= General considerations | ||
:description: This chapter describes a list of information to consider using the APOC library. | ||
|
||
To use the APOC library it's necessary to consider the following issues. | ||
|
||
.Memory tracker | ||
|
||
The APOC procedures (and in general, the Neo4j procedures), currently are not detected by Neo4j Memory Tracker. | ||
This means that, for example, the xref::overview/apoc.path/apoc.path.expand.adoc[apoc.path.expand] procedure | ||
doesn't stop if `dbms.memory.transaction.database_max_size` is reached, | ||
and we cannot use the `call dbms.listTransactions() yield currentQuery, estimatedUsedHeapMemory` to monitor the memory usage of the query. | ||
Therefore, please use the procedure carefully to avoid Java Heap space errors. |