5 ms·
> One fun bit of trivia about Bigtable is that they had these internal control-plane entities (as part of the implementation) called tablet servers, which had l
by bickeringyokel 6y ago
> One fun bit of trivia about Bigtable is that they had these internal control-plane entities (as part of the implementation) called tablet servers, which had large indexes, and at some point they became a scaling bottleneck.
Anyone understand the technical jargon here? I'm a bit lost.
- bobbiechen 6y agoThe BigTable paper is available here: https://research.google/pubs/pub27898/ https://research.google/pubs/pub27898/ > Bigtable maintains data in lexicographic order by row key. The row range for a table is dynamically partitioned. Each row range is called a tablet, which is the unit of dis- tribution and load balancing. And later... >The master is responsible for assigning tablets to tablet servers, detecting the addition and expiration of tablet servers, balancing tablet-server load, and garbage col- lection of files in GFS. In addition, it handles schema changes such as table and column family creations. Each tablet server manages a set of tablets (typically we have somewhere between ten to a thousand tablets per tablet server). The tablet server handles read and write requests to the tablets that it has loaded, and also splits tablets that have grown too large.
- dilyevsky 6y agoCheck out the original bigtable paper and it’ll make more sense. I think the author maybe misremembering some technical details here though.
- jeffbee 6y agoMaybe he's talking about the way that bigtable metadata1 is itself hosted on bigtable? The statements don't make much sense.