You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using the flag "expand_edge" set to false, Live Load gets lots of aborts.
To Reproduce
Steps to reproduce the behavior:
./dgraph zero
./dgraph server --lru_mb 4025 --expand_edge=false
./dgraph live -c 1 -r 1million.rdf.gz -s 21million.schema -d localhost:9080 -z localhost:5080
Expected behavior
A warning that the server is using a flag that is not compatible with LiveLoad.
Or have the (flag) option available in LiveLoad.
And it would also be interesting to know if this is expected behavior.
Logs:
Dgraph Live
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m42s, Aborts: 7874
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m44s, Aborts: 7883
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m46s, Aborts: 7894
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m48s, Aborts: 7904
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m50s, Aborts: 7915
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m52s, Aborts: 7930
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m54s, Aborts: 7938
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m56s, Aborts: 7939
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 10m58s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m0s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m2s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m4s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m6s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m8s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m10s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m12s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m14s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m16s, Aborts: 7945
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m18s, Aborts: 7947
Total Txns done: 0 RDFs per second: 0 Time Elapsed: 11m20s, Aborts: 7949
Server
2018/08/16 20:09:14 mutation.go:141: Done schema update predicate:"_share_hash_" value_type:STRING directive:INDEX tokenizer:"exact"
2018/08/16 20:10:54 groups.go:358: Serving tablet for: performance.film
2018/08/16 20:10:54 groups.go:358: Serving tablet for: performance.actor
2018/08/16 20:10:54 groups.go:358: Serving tablet for: performance.character
2018/08/16 20:20:20 draft.go:773: Found 5 old transactions. Acting to abort them.
2018/08/16 20:20:20 draft.go:750: TryAbort 5 txns with start ts. Error: <nil>
2018/08/16 20:21:11 draft.go:776: abortOldTransactions for 5 txns. Error: <nil>
2018/08/16 20:21:20 draft.go:773: Found 230 old transactions. Acting to abort them.
2018/08/16 20:21:20 draft.go:750: TryAbort 230 txns with start ts. Error: <nil>
2018/08/16 20:21:22 draft.go:776: abortOldTransactions for 230 txns. Error: <nil>
Bug report
Desktop (please complete the following information):
Describe the bug
Using the flag "expand_edge" set to false, Live Load gets lots of aborts.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A warning that the server is using a flag that is not compatible with LiveLoad.
Or have the (flag) option available in LiveLoad.
And it would also be interesting to know if this is expected behavior.
Logs:
Dgraph Live
Server
Dgraph Zero
2018/08/16 20:09:12 zero.go:442: Connected: id:1 group_id:1 addr:"localhost:7080" 2018/08/16 20:09:39 oracle.go:92: Purged below ts:273, len(o.commits):20, len(o.rowCommit):0 2018/08/16 20:10:09 oracle.go:92: Purged below ts:610, len(o.commits):31, len(o.rowCommit):0 2018/08/16 20:10:39 oracle.go:92: Purged below ts:950, len(o.commits):31, len(o.rowCommit):0 2018/08/16 20:10:49 raft.go:467: Writing snapshot at index: 1065, applied mark: 1206 2018/08/16 20:11:09 oracle.go:92: Purged below ts:1307, len(o.commits):36, len(o.rowCommit):0 2018/08/16 20:11:39 oracle.go:92: Purged below ts:1952, len(o.commits):37, len(o.rowCommit):0 2018/08/16 20:11:49 raft.go:467: Writing snapshot at index: 2070, applied mark: 2311 2018/08/16 20:12:09 oracle.go:92: Purged below ts:2611, len(o.commits):51, len(o.rowCommit):0 2018/08/16 20:12:39 oracle.go:92: Purged below ts:3215, len(o.commits):56, len(o.rowCommit):0 2018/08/16 20:12:39 raft.go:467: Writing snapshot at index: 3333, applied mark: 3390 2018/08/16 20:13:09 oracle.go:92: Purged below ts:3944, len(o.commits):43, len(o.rowCommit):0 2018/08/16 20:13:39 oracle.go:92: Purged below ts:4602, len(o.commits):71, len(o.rowCommit):0 2018/08/16 20:13:49 raft.go:467: Writing snapshot at index: 4720, applied mark: 5033 2018/08/16 20:14:09 oracle.go:92: Purged below ts:5345, len(o.commits):57, len(o.rowCommit):0 2018/08/16 20:14:39 oracle.go:92: Purged below ts:5931, len(o.commits):138, len(o.rowCommit):0 2018/08/16 20:14:49 raft.go:467: Writing snapshot at index: 6062, applied mark: 6433 2018/08/16 20:15:09 oracle.go:92: Purged below ts:6552, len(o.commits):228, len(o.rowCommit):0 2018/08/16 20:15:39 oracle.go:92: Purged below ts:6754, len(o.commits):257, len(o.rowCommit):0 2018/08/16 20:16:09 oracle.go:92: Purged below ts:6804, len(o.commits):413, len(o.rowCommit):0 2018/08/16 20:17:09 oracle.go:92: Purged below ts:6844, len(o.commits):556, len(o.rowCommit):0 2018/08/16 20:18:09 oracle.go:92: Purged below ts:6889, len(o.commits):695, len(o.rowCommit):0 2018/08/16 20:19:39 oracle.go:92: Purged below ts:6893, len(o.commits):956, len(o.rowCommit):0 2018/08/16 20:21:09 oracle.go:92: Purged below ts:6939, len(o.commits):1012, len(o.rowCommit):0 2018/08/16 20:21:39 oracle.go:92: Purged below ts:7944, len(o.commits):7, len(o.rowCommit):0 2018/08/16 20:21:49 raft.go:467: Writing snapshot at index: 8071, applied mark: 8317
The text was updated successfully, but these errors were encountered: