Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

19,000 writes enter, one write leaves #4601

Closed
aphyr opened this issue Jan 16, 2020 · 1 comment
Closed

19,000 writes enter, one write leaves #4601

aphyr opened this issue Jan 16, 2020 · 1 comment
Assignees
Labels
area/testing/jepsen kind/bug status/accepted

Comments

@aphyr
Copy link

@aphyr aphyr commented Jan 16, 2020

What version of Dgraph are you using?

1.1.1

Have you tried reproducing the issue with the latest release?

I'm working on that now; I haven't seen it in 1.1.1-65-g2851e2d9a yet, but it's been difficult to reproduce, so it's hard to tell.

What is the hardware spec (RAM, OS)?

5-node LXC Jepsen cluster, 128GB ECC RAM, 48-way Xeon.

Steps to reproduce the issue (command/config used to run Dgraph).

With Jepsen 3932955ce71dc7a731e9510fd197b2b600d828d4, try

lein run test --workload uid-set --time-limit 600 --concurrency 2n --test-count 20

Expected behaviour and actual result.

In the UID-set test, Jepsen creates a schema like value: [int] ., and inserts a whole bunch of unique triples; each with the same UID, same predicate, and unique values. At the end of the test, it tries to read those triples back by querying for every value associated with the chosen UID. In this test run, we inserted 19,030 distinct values. However, when we tried to read those values at the end of the test, we observed:

{:q [{:uid 0x1, :value 24333}]}

rather than the expected

:q [{:uid 0x3, :value [7758 1675 3419 ... <19,000 more elements>]}]

24333 was the most recent successfully inserted value. It appears as if Dgraph has... perhaps lost the schema for the value predicate entirely, or somehow overwritten every previous record with a single one?

@danielmai suggests this could be due to a bug in posting lists, which may have been fixed in #4574.

@aphyr aphyr changed the title Many writes enter, one write leaves 19,000 writes enter, one write leaves Jan 16, 2020
@sleto-it sleto-it added kind/bug status/accepted labels Jan 17, 2020
@martinmr
Copy link
Contributor

@martinmr martinmr commented Jul 8, 2020

This issue is fixed in the latest releases and marked as fixed in the Jepsen report.

@martinmr martinmr closed this as completed Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing/jepsen kind/bug status/accepted
Projects
None yet
Development

No branches or pull requests

5 participants