4 ms·

TL;DR - Moved from HBase to MyRocks engine on MySQL sitting on top of NVMe storage via their Lightning Server [1], which is a JBOF (just a bunch of flash) setup

TL;DR - Moved from HBase to MyRocks engine on MySQL sitting on top of NVMe storage via their Lightning Server [1], which is a JBOF (just a bunch of flash) setup using x16 PCIe. [1] https://code.facebook.com/posts/989638804458007/introducing-lightning-a-flexible-nvme-jbof/ https://code.facebook.com/posts/989638804458007/introducing-...

godelmachine 8y ago
Have they published a paper on this on Facebook Research?
- midom 8y ago
  doesn't really qualify much as research - just lots of engineering to cover all corners
- jensvdh 8y ago
  Social media apps have "Research" now?
  - tomnipotent 8y ago
    You are aware that Facebook is the largest website on the planet?
  - alexbeloi 8y ago
    Yes they do/have research. Facebook had 12 papers at the last computer vision conference I attended (CVPR '17) and won the awards for best paper and best student paper.
  - wenc 8y ago
    They have a very strong research arm covering a significant number of research areas. https://research.fb.com/ https://research.fb.com/
midom 8y ago
+ app server / schema rework
wenc 8y ago
Anyone know why Facebook moved off HBase? (article doesn't address this) I get that MyRocks is truly amazing, but I'm wondering what issues they were facing with HBase. I heard HBase was picked over Cassandra (developed at FB) because it was strongly consistent vs Cassandra's eventual consistency.
- tomnipotent 8y ago
  My guess is operational experience, though the article mentions it was necessary to take advantage of Lightning. I can't think of another business on the planet that has pushed MySQL (and RDBMS' in general) further than FB.
- ryanobjc 8y ago
  at the time they picked HBase because it was easier to repair missing replicas. Hdfs namenode juat schedules block replication. Cassandra (at least the version they were considering) had to work a lot harder at replacing a missing replica. Remember they had a version that didn’t have workable merkel trees. I also heard they had an issue with network flaps causing unrepairable inconsistency. I never got the full scoop on this. I had worked with the engineers directly responsible for the HBase choice back when. All water under the bridge now it seems.

godelmachine 8y ago

Have they published a paper on this on Facebook Research?

midom 8y ago
doesn't really qualify much as research - just lots of engineering to cover all corners
jensvdh 8y ago
Social media apps have "Research" now?
- tomnipotent 8y ago
  You are aware that Facebook is the largest website on the planet?
- alexbeloi 8y ago
  Yes they do/have research. Facebook had 12 papers at the last computer vision conference I attended (CVPR '17) and won the awards for best paper and best student paper.
- wenc 8y ago
  They have a very strong research arm covering a significant number of research areas. https://research.fb.com/ https://research.fb.com/

midom 8y ago

+ app server / schema rework

wenc 8y ago

Anyone know why Facebook moved off HBase? (article doesn't address this) I get that MyRocks is truly amazing, but I'm wondering what issues they were facing with HBase. I heard HBase was picked over Cassandra (developed at FB) because it was strongly consistent vs Cassandra's eventual consistency.

tomnipotent 8y ago
My guess is operational experience, though the article mentions it was necessary to take advantage of Lightning. I can't think of another business on the planet that has pushed MySQL (and RDBMS' in general) further than FB.
ryanobjc 8y ago
at the time they picked HBase because it was easier to repair missing replicas. Hdfs namenode juat schedules block replication. Cassandra (at least the version they were considering) had to work a lot harder at replacing a missing replica. Remember they had a version that didn’t have workable merkel trees. I also heard they had an issue with network flaps causing unrepairable inconsistency. I never got the full scoop on this. I had worked with the engineers directly responsible for the HBase choice back when. All water under the bridge now it seems.