# CREATE INDEX ON :Label(prop) is really slow after neo4j-admin import

**URL:** <https://community.neo4j.com/t/create-index-on-label-prop-is-really-slow-after-neo4j-admin-import/5377>\
**Category:** Import / Export\
**Created:** [February 28, 2019, 5:44pm UTC](https://community.neo4j.com/t/create-index-on-label-prop-is-really-slow-after-neo4j-admin-import/5377 "2019-02-28T17:44:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sean.r.graff](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/sean.r.graff/32/3496_2.png) [@sean.r.graff](https://community.neo4j.com/u/sean.r.graff)\
**Post date:** [February 28, 2019, 5:44pm UTC](https://community.neo4j.com/t/create-index-on-label-prop-is-really-slow-after-neo4j-admin-import/5377/1 "2019-02-28T17:44:14Z")

</div>

I had this issue happen to me where after importing a database of only 10 million nodes, I couldn't create indexes! It would just get hung up and continue to load.

Well, I found a solution, and I hope it helps others!

All I had to do was restart Neo4j after it hung up, and when I went back into the cypher-shell after the restart, the index was created instantly.

I'd love to know WHY this worked! But for now, I'm happy I was able to figure this out, and I hope it helps others. I searched for quite some time for a solution.

Sean

---

<div class="post-metadata">

**Author:** ![michael.hunger](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/michael.hunger/32/27377_2.png) [@michael.hunger](https://community.neo4j.com/u/michael.hunger)\
**Post date:** [March 1, 2019, 12:59am UTC](https://community.neo4j.com/t/create-index-on-label-prop-is-really-slow-after-neo4j-admin-import/5377/2 "2019-03-01T00:59:57Z")

</div>

Glad you figured it out. I'm still not sure exactly what you did when it failed.

do neo4j-admin import  
let it finish  
start up the database  
create index

should work fine.

---

<div class="post-metadata">

**Author:** ![jherna6](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/jherna6/32/6201_2.png) [@jherna6](https://community.neo4j.com/u/jherna6)\
**Post date:** [March 3, 2020, 5:16pm UTC](https://community.neo4j.com/t/create-index-on-label-prop-is-really-slow-after-neo4j-admin-import/5377/3 "2020-03-03T17:16:55Z")

</div>

Unfortunately, this did not seem to help for my situation.

I load using neo4j-admin import, let it finish (after 4 days), and start the database (9.4TB in size, 1.7B nodes).

The index creation for a single property on a node label stalls at 14% and does not pick up where it left off, upon restarting.

Rather, it seems to start over each time.

---

<div class="post-metadata">

**Author:** ![michael.hunger](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/michael.hunger/32/27377_2.png) [@michael.hunger](https://community.neo4j.com/u/michael.hunger)\
**Post date:** [May 30, 2020, 8:42am UTC](https://community.neo4j.com/t/create-index-on-label-prop-is-really-slow-after-neo4j-admin-import/5377/4 "2020-05-30T08:42:00Z")

</div>

What are your server specs and which version? Try to use the latest there have been a lot of improvements

Also make sure to have enough page cache an heap configured. For that graph size I’d say 256 to 512g page cache and 31g heap

Also you might consider sharding with fabric

---

<div class="post-metadata">

**Author:** ![DanielGittx](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/danielgittx/32/11558_2.png) [@DanielGittx](https://community.neo4j.com/u/DanielGittx)\
**Post date:** [June 8, 2020, 10:42am UTC](https://community.neo4j.com/t/create-index-on-label-prop-is-really-slow-after-neo4j-admin-import/5377/5 "2020-06-08T10:42:30Z")

</div>

Hi @michael.hunger ,  
My issue is on creating index on relationship property. The process is very slow.

Considering:-  
- Database size is 1.2t  
Server configs:-  
- Heap - 230g  
- Page cache - 1.182t

Neo4j Version:-  
Neo4j Browser version: 4.0.3  
Neo4j Server version: [3.5.15]

It has taken 3hrs to just get to 12% (index populating)

- CALL db.index.fulltext.createRelationshipIndex("idDateRelationship",["CALLS"],["CALL\_DATE"], { analyzer: "url\_or\_email", eventually\_consistent: "true" })

Why is this and is it possible to fast track?
