Live data from Hacker News

Viewing profile — free-ekanayaka

free-ekanayaka

HN member
Joined
Fri, Apr 06, 2018, 6:09 AM UTC
HN karma
92
Public activity
19 items

About free-ekanayaka

No profile information was provided.

Recent public activity

  1. comment
    Comment #20839413

    It's not a buzz term. It's really fully async disk I/O. Dqlite does not use SQLite's stock vfs implementation for writing to disk, as it's an entirely different model (based on raf…

  2. comment
    Comment #20839400

    Everything you said is very accurate (dqlite author here).

  3. comment
    Comment #20839388

    Give us time, we'll get there :)

  4. comment
    Comment #20839383

    Depends on how fast is your disk, what file system and kernel you use, and how low is your network latency. Difficult to predict. But it's basically as fast as it can get given 1) …

  5. comment
    Comment #20839354

    Not that I know, but it's on my todo list (dqlite author here).

  6. comment
    Comment #20839341

    The support of async disk I/O in Linux differs depending on kernel version and file system type. But it is possible to get 100% async I/O with the is_submit(), and dqlite will leve…

  7. comment
    Comment #20837002

    https://github.com/canonical/dqlite/blob/master/doc/faq.md#w...

  8. comment
    Comment #20836996

    It has been around for 2 years and half, but we released v1.0.0 just yesterday. I added answers to your other questions to the FAQ: https://github.com/canonical/dqlite/blob/master/…

  9. comment
    Comment #20836895

    Oh I had no idea somebody was using it in the wild! It has been unstable until now, we just released v1.0.0 yesterday. So no more public API breakage from now on.

  10. comment
    Comment #16776942

    Yes, dqlite is currently used for clustering support in LXD 3.0: https://github.com/lxc/lxd

  11. comment
    Comment #16773573

    If you read the raft paper, or just watch presentations of it, you'll see that all the issues you mentioned are covered: - faulty node replacement: you can take any node off (or an…

  12. comment
    Comment #16772248

    "slower" means this: when you perform a SQLite write, SQLite writes a new page on disk to the its write-ahead log. dqlite needs to replicate that page write across all nodes. A pag…

  13. comment
    Comment #16772013

    Unit and fuzzy-based test coverage that includes all possible edge cases is being put in place. I'd like to write a Jepsen test suite too. Hardware does not matter that much, since…

  14. comment
    Comment #16771990

    If you require SQL, sharding and concurrent writes, yes do use CockroachDB or other equivalent solution. If you don't have those requirements, dqlite or rqlite might get the job do…

  15. comment
    Comment #16771343

    I'm working towards a 1.0 release. At that point documentation will be more complete and the plumbing needed to use it in an app should be also reduced. I think the best explanatio…

  16. comment
    Comment #16771316

    BedrockDB requires to operate a separate process, whereas you can embed dqlite in your Go application (pretty much in the SQLite philosophy). Also, afaik BedrockDB patches upstream…

  17. comment
    Comment #16771302

    If your application is: 1) Distributed (e.g. n equal processes running on n machines) 2) Needs some shared state across nodes 3) Would like that state to have SQL semantics (relati…

  18. comment
    Comment #16771279

    I implemented dqlite in Go for convenience (a production-ready raft library was available, github.com/hashicorp/raft). It'd be interesting to implement something similar in C or ev…

  19. comment
    Comment #16771263

    Hello, author of dqlite here. Things are still in flux, but yes, I plan to publish benchmarks before making a 1.0 release, as well as improving documentations and introduce some mo…