CREATE INDEX shouldn't keep a schema lock during the duration of population of the index. Is that what you're seeing here?
Perhaps are you creating constraints? On Wednesday, January 11, 2017 at 9:07:42 PM UTC+1, Matias Burak wrote: > > Hi Michael, we might have a lot of operations running at the same time, > like CREATE, MERGE and some might write thousands of records in a single > transaction. There can be several concurrent of these but i guess not more > than 5...10 at most. And yes, they might be creating/updating nodes for > that label. > > El miércoles, 11 de enero de 2017, 15:56:57 (UTC-3), Michael Hunger > escribió: >> >> Matias, >> >> can you describe the other kinds of queries that are running (reads, >> writes, do they also touch the :User label?) how many of them and how >> concurrent? >> >> Michael >> >> On Tue, Jan 10, 2017 at 11:32 PM, Matias Burak <[email protected]> wrote: >> >>> Hi guys, >>> >>> Is there a way to create indexes safely while running an application? >>> We need to create indexes on a remote Neo4j server dinamically while the >>> system is running, so it might be doing other calls to Neo4j server. >>> Right now we create them by running a query like "CREATE INDEX ON >>> :User(name)" but that is looking the whole database, and sometimes we are >>> getting deadlocks and eventually the server stops responding. >>> >>> Is there something we can do to avoid this behavior? >>> We are running the latest 3.1 version. >>> >>> Thanks, >>> Matias. >>> >>> -- >>> 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.
