# Become unable to execute mutation suddenly in write-heavy workload **URL:** \ **Category:** Users\ **Created:** [June 21, 2018, 5:29am UTC](https://discuss.dgraph.io/t/become-unable-to-execute-mutation-suddenly-in-write-heavy-workload/2781 "2018-06-21T05:29:45Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![munisystem](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/munisystem/32/1179_2.png) [@munisystem](https://discuss.dgraph.io/u/munisystem)\ **Post date:** [June 21, 2018, 5:29am UTC](https://discuss.dgraph.io/t/become-unable-to-execute-mutation-suddenly-in-write-heavy-workload/2781/1 "2018-06-21T05:29:45Z")
Hi, I ran into an issue which can’t execute mutation while inserting a lot of data into Dgraph. Each operation contains 5,000 triples, and the request is sent serially. Also, Dgraph already stored 0.4 billion RDFs. The result of an investigation, I found below. - A query is executable and performance isn’t decrease - I tried to restart zero and server but didn’t recover - zero and server don’t be output logs anything Now I try to create a small example to reproduce this issue. I use Dgraph in production so can you help me to resolve it. ### my environment - version: v1.0.5 (commit SHA-1 82787414) - OS: CoreOS beta 1632.1.0 - host: AWS EC2 r4.4xlarge ### How do I run Dgraph Use official docker image and serve zero and server in the same instance. ```auto $ docker run -d \ --name dgraph-zero \ --net host \ -v /home/core/dgraph:/dgraph \ dgraph/dgraph:v1.0.5 \ dgraph zero --my 10.1.3.106:5080 --idx 1 $ docker run -d \ --name dgraph-server \ --net host \ -v /home/core/dgraph:/dgraph \ dgraph/dgraph:v1.0.5 \ dgraph server --my 10.1.3.106:7080 --zero 10.1.3.106:5080 --posting_tables memorymap --lru_mb 40960 ``` ### logs **server** ```auto 2018/06/08 09:50:11 oracle.go:75: purging below ts:1295243, len(o.commits):310, len(o.aborts):6, len(o.rowCommit):4 2018/06/08 09:51:11 oracle.go:75: purging below ts:1295250, len(o.commits):309, len(o.aborts):5, len(o.rowCommit):4 2018/06/08 09:52:01 oracle.go:75: purging below ts:1295257, len(o.commits):308, len(o.aborts):4, len(o.rowCommit):4 2018/06/08 09:53:11 oracle.go:75: purging below ts:1295264, len(o.commits):307, len(o.aborts):3, len(o.rowCommit):4 2018/06/08 09:54:21 oracle.go:75: purging below ts:1295271, len(o.commits):306, len(o.aborts):2, len(o.rowCommit):4 ``` **zero** ```auto 2018/06/08 09:50:11 oracle.go:75: purging below ts:1295243, len(o.commits):310, len(o.aborts):6, len(o.rowCommit):4 2018/06/08 09:51:11 oracle.go:75: purging below ts:1295250, len(o.commits):309, len(o.aborts):5, len(o.rowCommit):4 2018/06/08 09:52:01 oracle.go:75: purging below ts:1295257, len(o.commits):308, len(o.aborts):4, len(o.rowCommit):4 2018/06/08 09:53:11 oracle.go:75: purging below ts:1295264, len(o.commits):307, len(o.aborts):3, len(o.rowCommit):4 2018/06/08 09:54:21 oracle.go:75: purging below ts:1295271, len(o.commits):306, len(o.aborts):2, len(o.rowCommit):4 ``` ---
**Author:** ![shanghai-Jerry](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/shanghai-jerry/32/863_2.png) [@shanghai-Jerry](https://discuss.dgraph.io/u/shanghai-Jerry)\ **Post date:** [June 21, 2018, 6:37am UTC](https://discuss.dgraph.io/t/become-unable-to-execute-mutation-suddenly-in-write-heavy-workload/2781/2 "2018-06-21T06:37:46Z")
i can not figure out what happened to dgraph, maybe i need more details about drgraph ---
**Author:** ![munisystem](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/munisystem/32/1179_2.png) [@munisystem](https://discuss.dgraph.io/u/munisystem)\ **Post date:** [June 21, 2018, 8:05am UTC](https://discuss.dgraph.io/t/become-unable-to-execute-mutation-suddenly-in-write-heavy-workload/2781/3 "2018-06-21T08:05:01Z")
What exactly is it that you want to know? ---
**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\ **Post date:** [June 21, 2018, 4:00pm UTC](https://discuss.dgraph.io/t/become-unable-to-execute-mutation-suddenly-in-write-heavy-workload/2781/4 "2018-06-21T16:00:51Z")
Version 1.0.6 will be out soon, so can you test with it? as soon as the binaries come out. It would be interesting to reproduce this with public RDF. So that we can imitate the process. > **[GitHub - dgraph-io/benchmarks: Run benchmarks with RDF data](https://github.com/dgraph-io/benchmarks)** > > Run benchmarks with RDF data. Contribute to dgraph-io/benchmarks development by creating an account on GitHub. ---
**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\ **Post date:** [June 21, 2018, 5:40pm UTC](https://discuss.dgraph.io/t/become-unable-to-execute-mutation-suddenly-in-write-heavy-workload/2781/5 "2018-06-21T17:40:00Z")
What’s the issue here? It’s not clear. ---
**Author:** ![shanghai-Jerry](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/shanghai-jerry/32/863_2.png) [@shanghai-Jerry](https://discuss.dgraph.io/u/shanghai-Jerry)\ **Post date:** [June 22, 2018, 3:55am UTC](https://discuss.dgraph.io/t/become-unable-to-execute-mutation-suddenly-in-write-heavy-workload/2781/6 "2018-06-22T03:55:05Z")
i need your help @mrjn > [@Uid: \[24387\] cannot be greater than lease: \[0\]](http://discuss.hypermode.com/t/uid-24387-cannot-be-greater-than-lease-0/2784): > > hi, i want to know how bulk loader api do to avoid this exception, cause i want to write another api to load the exported rdf data. any ideas? the data are like this: \<:uid35b3869\> “777000636”^^xs:int . \<:uid35b38ef\> “777002156”^^xs:int . … it’s obvious that we have already had uid, but when i mutate this data, it causes the above exception. how to let the dgraph to accept the uid ? ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/2/2b38fdece2abe5814f2e51bee69d1e67fc304b0a.png) [@system](https://discuss.dgraph.io/u/system)\ **Post date:** [July 22, 2018, 3:55am UTC](https://discuss.dgraph.io/t/become-unable-to-execute-mutation-suddenly-in-write-heavy-workload/2781/7 "2018-07-22T03:55:21Z")
Closed on July 22, 2018, 3:55am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.