hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-hadoop Wiki] Update of "Hbase/HbaseArchitecture" by JimKellerman
Date Mon, 12 Feb 2007 19:41:58 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-hadoop Wiki" for change notification.

The following page has been changed by JimKellerman:
http://wiki.apache.org/lucene-hadoop/Hbase/HbaseArchitecture

The comment on the change is:
Start documenting inter-process interactions

------------------------------------------------------------------------------
   * [#tabletserver Tablet Server]
   * [#sstable SSTable]
   * [#metadata METADATA Table]
+  * [#ipc Inter-process Communication Messages]
+   * [#wireformat IPC Message Wire Format]
+   * [#ipcclientmaster Client to Master Messages]
+   * [#ipcclienttablet Client to Tablet Server Messages]
+   * [#ipcmastertablet Master to Tablet Server Messages]
   * [#clientlib Client Library]
-  * [#api API]
+   * [#api API]
   * [#other Other]
   * [#comments Comments]
  
@@ -204, +209 @@

  [[Anchor(chubby)]]
  = Distributed Lock Server - a ''Chubby'' clone =
  
-  * [:DistributedLockServer:see also Hadoop Distributed Lock Server]
+ [:DistributedLockServer:See the Hadoop Distributed Lock Server Project Page]
   * Uses
    1. To ensure that there is at most one active master at any time
    1. To store bootstrap location of Bigtable data
@@ -380, +385 @@

   * Each row stores approximately 1KB of data in memory
   * All events pertaining to each tablet are logged here (such as when a tablet server starts
serving a tablet)
  
+ [[Anchor(ipc)]]
+ = Inter-process Communication Messages =
+ 
+ Interactions betwen the client and master, the client and the tablet
+ server and between the master and tablet servers occur as messages
+ transferred over a socket connection. The following sections document
+ the general format of the messages, and the specific messages for each
+ interaction. 
+ 
+ [[Anchor(wireformat)]]
+ == IPC Message Wire Format ==
+ 
+ All IPC messages have the same basic format but differ in the details
+ of the operation being performed and the parameters that are
+ passed. The basic format of a message is:
+ 
+ ||<:> '''Size''' ||<(> '''Description''' ||
+ ||<:> byte ||<(> protocol version number ||
+ ||<:> int ||<(> message type (op code) ||
+ ||<:> int ||<(> number of parameters ||
+ ||||<:> ''repeat the following for each parameter'' ||
+ ||<:> int ||<(> parameter identifier ||
+ ||<:> int ||<(> length of parameter value ||
+ ||<:> byte[length] ||<(> parameter value ||
+ 
+ [[Anchor(ipcclientmaster)]]
+ == Client to Master Messages ==
+ 
+ [[Anchor(ipcclienttablet)]]
+ == Client to TabletServer Messages ==
+ 
+ [[Anchor(ipcmastertablet)]]
+ == Master to Tablet Server Messages ==
  
  [[Anchor(clientlib)]]
  = Client Library =
@@ -391, +429 @@

  
  
  [[Anchor(api)]]
- = API =
+ == API ==
  
  {{{
  CreateTable()

Mime
View raw message