neo4j-graph-algorithms
neo4j-graph-algorithms copied to clipboard
neo4j-contrib
algo can't work with scalable data
CALL algo.louvain.stream('Account','follow', {weightProperty:'propertyName', defaultValue:1.0, concurrency:4}) YIELD nodeId, community
cypher like that,you can't do that work in bigger graph which have 700000nodes and 3000000relations .
The max number of nodes/rels for heavy graph is 2bn.
In your example you have only 3 mio rels so it should work. Can you be more specific what doesn't seem to work and is there something in the debug.log?
use cypher-shell,it is always stuck on this status @tomasonjo
2018-04-16 09:19:15.464+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Log pruning complete. 2018-04-16 10:13:42.377+0000 ERROR [o.n.b.t.SocketTransportHandler] Fatal error occurred when handling a client connection: syscall:read(..) failed: Connection reset by peer syscall:read(..) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer at io.netty.channel.unix.FileDescriptor.readAddress(..)(Unknown Source) 2018-04-17 02:43:26.189+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19418]: Starting check pointing... 2018-04-17 02:43:26.205+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19418]: Starting store flush... 2018-04-17 02:43:26.632+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19418]: Store flush completed 2018-04-17 02:43:26.632+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19418]: Starting appending check point entry into the tx log... 2018-04-17 02:43:26.643+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19418]: Appending check point entry into the tx log completed 2018-04-17 02:43:26.643+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19418]: Check pointing completed 2018-04-17 02:43:26.643+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Starting log pruning. 2018-04-17 02:43:26.664+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Log pruning complete. 2018-04-17 02:43:33.366+0000 ERROR [o.n.b.t.SocketTransportHandler] Fatal error occurred when handling a client connection: syscall:read(..) failed: Connection reset by peer syscall:read(..) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer at io.netty.channel.unix.FileDescriptor.readAddress(..)(Unknown Source) 2018-04-17 02:58:26.699+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19422]: Starting check pointing... 2018-04-17 02:58:26.699+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19422]: Starting store flush... 2018-04-17 02:58:26.881+0000 INFO [o.n.k.i.s.c.CountsTracker] About to rotate counts store at transaction 19422 to [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.a], from [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.b]. 2018-04-17 02:58:26.881+0000 INFO [o.n.k.i.s.c.CountsTracker] Successfully rotated counts store at transaction 19422 to [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.a], from [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.b]. 2018-04-17 02:58:28.139+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19422]: Store flush completed 2018-04-17 02:58:28.139+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19422]: Starting appending check point entry into the tx log... 2018-04-17 02:58:28.172+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19422]: Appending check point entry into the tx log completed 2018-04-17 02:58:28.172+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19422]: Check pointing completed 2018-04-17 02:58:28.172+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Starting log pruning. 2018-04-17 02:58:28.172+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Log pruning complete. 2018-04-17 03:06:51.618+0000 WARN [o.n.k.i.c.MonitorGc] GC Monitor: Application threads blocked for 223ms. 2018-04-17 03:07:25.760+0000 WARN [o.n.k.i.c.MonitorGc] GC Monitor: Application threads blocked for 405ms. 2018-04-17 03:13:28.388+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19587]: Starting check pointing... 2018-04-17 03:13:28.388+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19587]: Starting store flush... 2018-04-17 03:13:28.493+0000 INFO [o.n.k.i.s.c.CountsTracker] About to rotate counts store at transaction 19587 to [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.b], from [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.a]. 2018-04-17 03:13:28.493+0000 INFO [o.n.k.i.s.c.CountsTracker] Successfully rotated counts store at transaction 19587 to [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.b], from [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.a]. 2018-04-17 03:13:31.840+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19587]: Store flush completed 2018-04-17 03:13:31.840+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19587]: Starting appending check point entry into the tx log... 2018-04-17 03:13:31.885+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19587]: Appending check point entry into the tx log completed 2018-04-17 03:13:31.885+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19587]: Check pointing completed 2018-04-17 03:13:31.885+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Starting log pruning. 2018-04-17 03:13:31.885+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Log pruning complete. 2018-04-17 03:14:36.562+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2003] LOADING 0% 2018-04-17 03:14:36.652+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2003] LOADING 100% 2018-04-17 03:19:36.995+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2001] LOADING 0% 2018-04-17 03:19:37.057+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2001] LOADING 100% 2018-04-17 03:40:07.092+0000 ERROR [o.n.b.t.SocketTransportHandler] Fatal error occurred when handling a client connection: syscall:read(..) failed: Connection reset by peer syscall:read(..) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer at io.netty.channel.unix.FileDescriptor.readAddress(..)(Unknown Source) 2018-04-17 04:08:53.003+0000 ERROR [o.n.b.t.SocketTransportHandler] Fatal error occurred when handling a client connection: syscall:read(..) failed: Connection reset by peer syscall:read(..) failed: Connection reset by peer io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer at io.netty.channel.unix.FileDescriptor.readAddress(..)(Unknown Source) 2018-04-17 06:35:54.649+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2008] LOADING 0% 2018-04-17 06:36:42.044+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19589]: Starting check pointing... 2018-04-17 06:36:42.044+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19589]: Starting store flush... 2018-04-17 06:36:42.228+0000 INFO [o.n.k.i.s.c.CountsTracker] About to rotate counts store at transaction 19589 to [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.a], from [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.b]. 2018-04-17 06:36:42.229+0000 INFO [o.n.k.i.s.c.CountsTracker] Successfully rotated counts store at transaction 19589 to [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.a], from [/home/neo4j/neo4j-community-3.3.0/data/databases/graph.db/neostore.counts.db.b]. 2018-04-17 06:36:42.794+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19589]: Store flush completed 2018-04-17 06:36:42.794+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19589]: Starting appending check point entry into the tx log... 2018-04-17 06:36:42.802+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19589]: Appending check point entry into the tx log completed 2018-04-17 06:36:42.802+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19589]: Check pointing completed 2018-04-17 06:36:42.802+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Starting log pruning. 2018-04-17 06:36:42.802+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Log pruning complete.
this is debug.log @tomasonjo
2018-04-17 06:51:42.996+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19590]: Store flush completed 2018-04-17 06:51:42.996+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19590]: Starting appending check point entry into the tx log... 2018-04-17 06:51:43.009+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19590]: Appending check point entry into the tx log completed 2018-04-17 06:51:43.009+0000 INFO [o.n.k.i.t.l.c.CheckPointerImpl] Check Pointing triggered by scheduler for time threshold [19590]: Check pointing completed 2018-04-17 06:51:43.009+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Starting log pruning. 2018-04-17 06:51:43.010+0000 INFO [o.n.k.i.t.l.p.LogPruningImpl] Log Rotation [15]: Log pruning complete. 2018-04-17 06:53:46.248+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2012] LOADING 0%
this is new log , this is new cypher CALL algo.louvain.stream('Account','follow', {weightProperty:'community', defaultValue:1.0, concurrency:4}) YIELD nodeId, community;
it is always stuck on LOADING 0%
CALL algo.louvain('Account', 'follow', {write:true, writeProperty:'community'});
2018-04-17 07:05:35.309+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2013] LOADING 0%
it it always stuck on the status which LOADING 0%
What is your memory config for heap and page-cache. What kind of disk are you using? Do you only have 4 CPUs ?
#*****************************************************************
Neo4j configuration
For more details and a complete list of settings, please see
https://neo4j.com/docs/operations-manual/current/reference/configuration-settings/
#*****************************************************************
The name of the database to mount
#dbms.active_database=graph.db
Paths of directories in the installation.
#dbms.directories.data=data #dbms.directories.plugins=plugins #dbms.directories.certificates=certificates #dbms.directories.logs=logs #dbms.directories.lib=lib #dbms.directories.run=run
This setting constrains all LOAD CSV import files to be under the import directory. Remove or comment it out to
allow files to be loaded from anywhere in the filesystem; this introduces possible security problems. See the
LOAD CSV section of the manual for details.
dbms.directories.import=import
Whether requests to Neo4j are authenticated.
To disable authentication, uncomment this line
dbms.security.auth_enabled=false
Enable this to be able to upgrade a store from an older version.
#dbms.allow_upgrade=true
Java Heap Size: by default the Java heap size is dynamically
calculated based on available system resources.
Uncomment these lines to set specific initial and maximum
heap size.
dbms.memory.heap.initial_size=10240m dbms.memory.heap.max_size=10240m
The amount of memory to use for mapping the store files, in bytes (or
kilobytes with the 'k' suffix, megabytes with 'm' and gigabytes with 'g').
If Neo4j is running on a dedicated server, then it is generally recommended
to leave about 2-4 gigabytes for the operating system, give the JVM enough
heap to hold all your transaction state and query context, and then leave the
rest for the page cache.
The default page cache memory assumes the machine is dedicated to running
Neo4j, and is heuristically set to 50% of RAM minus the max Java heap size.
dbms.memory.pagecache.size=10g
#*****************************************************************
Network connector configuration
#*****************************************************************
With default configuration Neo4j only accepts local connections.
To accept non-local connections, uncomment this line:
dbms.connectors.default_listen_address=0.0.0.0
You can also choose a specific network interface, and configure a non-default
port for each connector, by setting their individual listen_address.
The address at which this server can be reached by its clients. This may be the server's IP address or DNS name, or
it may be the address of a reverse proxy which sits in front of the server. This setting may be overridden for
individual connectors below.
#dbms.connectors.default_advertised_address=localhost
You can also choose a specific advertised hostname or IP address, and
configure an advertised port for each connector, by setting their
individual advertised_address.
Bolt connector
dbms.connector.bolt.enabled=true #dbms.connector.bolt.tls_level=OPTIONAL #dbms.connector.bolt.listen_address=:7687
HTTP Connector. There must be exactly one HTTP connector.
dbms.connector.http.enabled=true #dbms.connector.http.listen_address=:7474
HTTPS Connector. There can be zero or one HTTPS connectors.
dbms.connector.https.enabled=true #dbms.connector.https.listen_address=:7473
Number of Neo4j worker threads.
#dbms.threads.worker_count=
#*****************************************************************
SSL system configuration
#*****************************************************************
Names of the SSL policies to be used for the respective components.
The legacy policy is a special policy which is not defined in
the policy configuration section, but rather derives from
dbms.directories.certificates and associated files
(by default: neo4j.key and neo4j.cert). Its use will be deprecated.
The policies to be used for connectors.
N.B: Note that a connector must be configured to support/require
SSL/TLS for the policy to actually be utilized.
see: dbms.connector.*.tls_level
#bolt.ssl_policy=legacy #https.ssl_policy=legacy
#*****************************************************************
SSL policy configuration
#*****************************************************************
Each policy is configured under a separate namespace, e.g.
dbms.ssl.policy..*
The example settings below are for a new policy named 'default'.
The base directory for cryptographic objects. Each policy will by
default look for its associated objects (keys, certificates, ...)
under the base directory.
Every such setting can be overriden using a full path to
the respective object, but every policy will by default look
for cryptographic objects in its base location.
Mandatory setting
#dbms.ssl.policy.default.base_directory=certificates/default
Allows the generation of a fresh private key and a self-signed
certificate if none are found in the expected locations. It is
recommended to turn this off again after keys have been generated.
Keys should in general be generated and distributed offline
by a trusted certificate authority (CA) and not by utilizing
this mode.
#dbms.ssl.policy.default.allow_key_generation=false
Enabling this makes it so that this policy ignores the contents
of the trusted_dir and simply resorts to trusting everything.
Use of this mode is discouraged. It would offer encryption but no security.
#dbms.ssl.policy.default.trust_all=false
The private key for the default SSL policy. By default a file
named private.key is expected under the base directory of the policy.
It is mandatory that a key can be found or generated.
#dbms.ssl.policy.default.private_key=
The private key for the default SSL policy. By default a file
named public.crt is expected under the base directory of the policy.
It is mandatory that a certificate can be found or generated.
#dbms.ssl.policy.default.public_certificate=
The certificates of trusted parties. By default a directory named
'trusted' is expected under the base directory of the policy. It is
mandatory to create the directory so that it exists, because it cannot
be auto-created (for security purposes).
To enforce client authentication client_auth must be set to 'require'!
#dbms.ssl.policy.default.trusted_dir=
Client authentication setting. Values: none, optional, require
The default is to require client authentication.
Servers are always authenticated unless explicitly overridden
using the trust_all setting. In a mutual authentication setup this
should be kept at the default of require and trusted certificates
must be installed in the trusted_dir.
#dbms.ssl.policy.default.client_auth=require
A comma-separated list of allowed TLS versions.
By default TLSv1, TLSv1.1 and TLSv1.2 are allowed.
#dbms.ssl.policy.default.tls_versions=
A comma-separated list of allowed ciphers.
The default ciphers are the defaults of the JVM platform.
#dbms.ssl.policy.default.ciphers=
#*****************************************************************
Logging configuration
#*****************************************************************
To enable HTTP logging, uncomment this line
#dbms.logs.http.enabled=true
Number of HTTP logs to keep.
#dbms.logs.http.rotation.keep_number=5
Size of each HTTP log that is kept.
#dbms.logs.http.rotation.size=20m
To enable GC Logging, uncomment this line
#dbms.logs.gc.enabled=true
GC Logging Options
see http://docs.oracle.com/cd/E19957-01/819-0084-10/pt_tuningjava.html#wp57013 for more information.
#dbms.logs.gc.options=-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime -XX:+PrintPromotionFailure -XX:+PrintTenuringDistribution
Number of GC logs to keep.
#dbms.logs.gc.rotation.keep_number=5
Size of each GC log that is kept.
#dbms.logs.gc.rotation.size=20m
Size threshold for rotation of the debug log. If set to zero then no rotation will occur. Accepts a binary suffix "k",
"m" or "g".
#dbms.logs.debug.rotation.size=20m
Maximum number of history files for the internal log.
#dbms.logs.debug.rotation.keep_number=7
#*****************************************************************
Miscellaneous configuration
#*****************************************************************
Enable this to specify a parser other than the default one.
#cypher.default_language_version=3.0
Determines if Cypher will allow using file URLs when loading data using
LOAD CSV. Setting this value to false will cause Neo4j to fail LOAD CSV
clauses that load data from the file system.
#dbms.security.allow_csv_import_from_file_urls=true
Retention policy for transaction logs needed to perform recovery and backups.
dbms.tx_log.rotation.retention_policy=1 days
Enable a remote shell server which Neo4j Shell clients can log in to.
#dbms.shell.enabled=true
The network interface IP the shell will listen on (use 0.0.0.0 for all interfaces).
#dbms.shell.host=127.0.0.1
The port the shell will listen on, default is 1337.
#dbms.shell.port=1337
Only allow read operations from this Neo4j instance. This mode still requires
write access to the directory for lock purposes.
#dbms.read_only=false
Comma separated list of JAX-RS packages containing JAX-RS resources, one
package name for each mountpoint. The listed package names will be loaded
under the mountpoints specified. Uncomment this line to mount the
org.neo4j.examples.server.unmanaged.HelloWorldResource.java from
neo4j-server-examples under /examples/unmanaged, resulting in a final URL of
http://localhost:7474/examples/unmanaged/helloworld/{nodeId}
#dbms.unmanaged_extension_classes=org.neo4j.examples.server.unmanaged=/examples/unmanaged
#********************************************************************
JVM Parameters
#********************************************************************
G1GC generally strikes a good balance between throughput and tail
latency, without too much tuning.
dbms.jvm.additional=-XX:+UseG1GC
Have common exceptions keep producing stack traces, so they can be
debugged regardless of how often logs are rotated.
dbms.jvm.additional=-XX:-OmitStackTraceInFastThrow
Make sure that initmemory is not only allocated, but committed to
the process, before starting the database. This reduces memory
fragmentation, increasing the effectiveness of transparent huge
pages. It also reduces the possibility of seeing performance drop
due to heap-growing GC events, where a decrease in available page
cache leads to an increase in mean IO response time.
Try reducing the heap memory, if this flag degrades performance.
dbms.jvm.additional=-XX:+AlwaysPreTouch
Trust that non-static final fields are really final.
This allows more optimizations and improves overall performance.
NOTE: Disable this if you use embedded mode, or have extensions or dependencies that may use reflection or
serialization to change the value of final fields!
dbms.jvm.additional=-XX:+UnlockExperimentalVMOptions dbms.jvm.additional=-XX:+TrustFinalNonStaticFields
Disable explicit garbage collection, which is occasionally invoked by the JDK itself.
dbms.jvm.additional=-XX:+DisableExplicitGC
Remote JMX monitoring, uncomment and adjust the following lines as needed. Absolute paths to jmx.access and
jmx.password files are required.
Also make sure to update the jmx.access and jmx.password files with appropriate permission roles and passwords,
the shipped configuration contains only a read only role called 'monitor' with password 'Neo4j'.
For more details, see: http://download.oracle.com/javase/8/docs/technotes/guides/management/agent.html
On Unix based systems the jmx.password file needs to be owned by the user that will run the server,
and have permissions set to 0600.
For details on setting these file permissions on Windows see:
http://docs.oracle.com/javase/8/docs/technotes/guides/management/security-windows.html
#dbms.jvm.additional=-Dcom.sun.management.jmxremote.port=3637 #dbms.jvm.additional=-Dcom.sun.management.jmxremote.authenticate=true #dbms.jvm.additional=-Dcom.sun.management.jmxremote.ssl=false #dbms.jvm.additional=-Dcom.sun.management.jmxremote.password.file=/absolute/path/to/conf/jmx.password #dbms.jvm.additional=-Dcom.sun.management.jmxremote.access.file=/absolute/path/to/conf/jmx.access
Some systems cannot discover host name automatically, and need this line configured:
#dbms.jvm.additional=-Djava.rmi.server.hostname=$THE_NEO4J_SERVER_HOSTNAME
Expand Diffie Hellman (DH) key size from default 1024 to 2048 for DH-RSA cipher suites used in server TLS handshakes.
This is to protect the server from any potential passive eavesdropping.
dbms.jvm.additional=-Djdk.tls.ephemeralDHKeySize=2048
#********************************************************************
Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
WARNING - Do not modify any of these properties when an application
using this configuration file has been installed as a service.
Please uninstall the service before modifying this section. The
service can then be reinstalled.
Name of the service
dbms.windows_service_name=neo4j
#********************************************************************
Other Neo4j system properties
#******************************************************************** dbms.jvm.additional=-Dunsupported.dbms.udc.source=tarball
#defined the sysn of usesage for algo dbms.security.procedures.unrestricted=algo.,apoc. apoc.import.file.enabled=true
this is my neo4j.conf @tomasonjo @jexp
I am really confuse about this cypher ，which is like that “CALL algo.scc('Account','follow', {write:true,partitionProperty:'community'})”；
And then I get the log on debug.log is that 2018-04-17 10:08:34.814+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2024] SCC(IterativeTarjan) 0% 2018-04-17 10:08:44.864+0000 INFO [o.n.k.i.p.Procedures] [neo4j.Pooled-2024] SCC(IterativeTarjan) 67%
It is not like showed before ,which would stuck in LOADING 0%,but it is stuck in 67%. @jexp @tomasonjo
now I starting the cypher but also stuck in 65%
and I am really confuse about that the resource didn't use in full at all
like that
