Maintaining fault domains in a distributed database

Abstract

In at least some examples, a system includes a distributed database and control logic to enable updates and queries to the distributed database. The control logic applies a plurality of identifiers to the updates and queries to maintain distinct fault domains in the distributed database.

What is claimed is: 
     
         1 . A system, comprising:
 a distributed database; and   control logic to enable updates and queries to the distributed database,   wherein the control logic applies a plurality of identifiers to the updates and queries to maintain distinct fault domains in the distributed database.   
     
     
         2 . The system of  claim 1 , wherein the distributed database comprises a pipelined database. 
     
     
         3 . The system of  claim 1 , wherein the plurality of identifiers comprise metadata identifiers attached to batches of updates. 
     
     
         4 . The system of  claim 1 , wherein different fault domains are assigned to different customers or applications. 
     
     
         5 . The system of  claim 1 , wherein the control logic enables distinct fault domains to be joined. 
     
     
         6 . The system of  claim 1 , wherein the control logic limits visibility of different fault domains according to a customizable visibility scheme. 
     
     
         7 . The system of  claim 1 , wherein the distributed database is associated with a distributed file system and wherein each of the distinct fault domains is associated with a logical file system within the distributed file system. 
     
     
         8 . The system of  claim 7 , wherein the plurality of identifiers correspond to a plurality of logical file systems within the distributed file system. 
     
     
         9 . The system of  claim 1 , wherein the distributed database is associated with a distributed file system, wherein the distinct fault domains correspond to individual nodes running the distributed file system, and wherein updates are partitioned based on a location of data referred to in the update. 
     
     
         10 . The system of  claim 1 , wherein the control logic ensures that metadata originating in a logical file system that is part of a distributed file system is stored back into that logical file system to enable origin-based data partitioning. 
     
     
         11 . The system of  claim 1 , wherein the control logic applies separate migration and backup operations to an origin file system based on its expected fault behavior and wherein a fault domain has the same reliability semantics as the origin file system. 
     
     
         12 . A method, comprising:
 receiving, by a processor, updates to a distributed database; and   applying, by the processor, identifiers to the updates to maintain distinct fault domains across the distributed database.   
     
     
         13 . The method of  claim 12 , further comprising limiting visibility of different fault domains according to a predetermined visibility scheme. 
     
     
         14 . The method of  claim 12 , further comprising collecting metadata from a distributed file system and storing the metadata in a logical file system and the distributed file system to enable origin-based data partitioning. 
     
     
         15 . The method of  claim 12 , further comprising applying separate migration and backup operations to an origin file system based on its expected fault behavior so that a fault domain has the same reliability semantics as the origin file system. 
     
     
         16 . A pipelined database system, comprising:
 a plurality of data update processing stages to enable trading off between query response time and data freshness;   control logic in communication with the plurality of data update processing stages to maintain distinct fault domains for the pipelined database system.   
     
     
         17 . The pipelined database system of  claim 16 , wherein the plurality of data update processing stages comprises an ingest stage to output batched updates, and wherein the control logic applies at least one logical identifier to each batch to maintain the distinct fault domains for the pipelined database system. 
     
     
         18 . The pipelined database system of  claim 16 , wherein the plurality of data update processing stages comprises an identifier (ID) remapping stage to output remapped update batches, and wherein the control logic applies at least one logical identifier to each remapped batch to maintain the distinct fault domains for the pipelined database system. 
     
     
         19 . The pipelined database system of  claim 16 , wherein the plurality of data update processing stages comprises a sorting stage to output sorted update batches, and wherein the control logic applies at least one logical identifier to each sorted batch to maintain the distinct fault domains for the pipelined database system. 
     
     
         20 . The pipelined database system of  claim 16 , wherein the plurality of data update processing stages comprises a merging stage to output merged update batches, and wherein the control logic applies at least one logical identifier to each merged batch to maintain the distinct fault domains for the pipelined database system.