You should be able to abort that long running query by terminating the transaction:
1. click the (x) in the neo4j browser 2. press ctrl-c if you use Neo4j shell 3. if you run the statements programmatically, create a tx (embedded or remote) and then call tx.terminate() from another thread. what was the query? you have to share more detail if you want help with query optimization (datamodel, query, existing indexes, machine config (or graph.db/messages.log) ) Michael On Mon, Apr 18, 2016 at 11:50 AM, kincheong lau <[email protected]> wrote: > we encounter problems when some of our developers run a badly optimized > query: > 1. the neo4j server will hang and no response > 2. there's no way to kill the long running query > 3. we usually have no choice but force restart neo4j > 4. we have applied indexes but seems does not help much when we have large > data volume > > we are using community version, any server configuration we could try to > avoid this performance issue? > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
