accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From e..@apache.org
Subject svn commit: r1469078 - in /accumulo/branches/1.5/docs/src/user_manual/chapters: design.tex table_configuration.tex
Date Wed, 17 Apr 2013 21:50:39 GMT
Author: ecn
Date: Wed Apr 17 21:50:39 2013
New Revision: 1469078

URL: http://svn.apache.org/r1469078
Log:
ACCUMULO-1187 update constraint info, remove reference to Loggers

Modified:
    accumulo/branches/1.5/docs/src/user_manual/chapters/design.tex
    accumulo/branches/1.5/docs/src/user_manual/chapters/table_configuration.tex

Modified: accumulo/branches/1.5/docs/src/user_manual/chapters/design.tex
URL: http://svn.apache.org/viewvc/accumulo/branches/1.5/docs/src/user_manual/chapters/design.tex?rev=1469078&r1=1469077&r2=1469078&view=diff
==============================================================================
--- accumulo/branches/1.5/docs/src/user_manual/chapters/design.tex (original)
+++ accumulo/branches/1.5/docs/src/user_manual/chapters/design.tex Wed Apr 17 21:50:39 2013
@@ -46,8 +46,8 @@ machines.
 
 \section{Components}
 
-An instance of Accumulo includes many TabletServers, write-ahead Logger
-servers, one Garbage Collector process, one Master server and many Clients.
+An instance of Accumulo includes many TabletServers, one Garbage Collector process, 
+one Master server and many Clients.
 
 \subsection{Tablet Server}
 
@@ -72,11 +72,14 @@ delete them.
 
 The Accumulo Master is responsible for detecting and responding to TabletServer
 failure. It tries to balance the load across TabletServer by assigning tablets carefully
-and instructing TabletServers to migrate tablets when necessary. The Master ensures all
+and instructing TabletServers to unload tablets when necessary. The Master ensures all
 tablets are assigned to one TabletServer each, and handles table creation, alteration,
 and deletion requests from clients. The Master also coordinates startup, graceful
 shutdown and recovery of changes in write-ahead logs when Tablet servers fail.
 
+Multiple masters may be run.  The masters will choose among themselves a single master,
+and the others will become backups if the master should fail.
+
 \subsection{Client}
 
 Accumulo includes a client library that is linked to every application. The client
@@ -149,8 +152,7 @@ Log to prevent any loss of data.
 
 The Master will coordinate the copying of write-ahead logs to HDFS so the logs
 are available to all tablet servers. To make recovery efficient, the updates
-within a log are grouped by tablet.  The sorting process can be performed by
-Hadoops MapReduce or the Logger server. TabletServers can quickly apply the
+within a log are grouped by tablet.  TabletServers can quickly apply the
 mutations from the sorted logs that are destined for the tablets they have now
 been assigned.
 

Modified: accumulo/branches/1.5/docs/src/user_manual/chapters/table_configuration.tex
URL: http://svn.apache.org/viewvc/accumulo/branches/1.5/docs/src/user_manual/chapters/table_configuration.tex?rev=1469078&r1=1469077&r2=1469078&view=diff
==============================================================================
--- accumulo/branches/1.5/docs/src/user_manual/chapters/table_configuration.tex (original)
+++ accumulo/branches/1.5/docs/src/user_manual/chapters/table_configuration.tex Wed Apr 17
21:50:39 2013
@@ -40,7 +40,7 @@ fam>}} [-?] -t <table>
 
 user@myinstance mytable> setgroups group_one=colf1,colf2 -t mytable
 
-user@myinstance mytable> getgroups group_one=colf1,colf2 -t mytable
+user@myinstance mytable> getgroups -t mytable
 \end{verbatim}
 \normalsize
 
@@ -94,15 +94,10 @@ Constraints can be enabled by setting a 
 
 \small
 \begin{verbatim}
-user@myinstance mytable> config -t mytable -s table.constraint.1=com.test.ExampleConstraint
-user@myinstance mytable> config -t mytable -s table.constraint.2=com.test.AnotherConstraint
-user@myinstance mytable> config -t mytable -f constraint
----------+--------------------------------+----------------------------
-SCOPE    | NAME                           | VALUE
----------+--------------------------------+----------------------------
-table    | table.constraint.1............ | com.test.ExampleConstraint
-table    | table.constraint.2............ | com.test.AnotherConstraint
----------+--------------------------------+----------------------------
+user@myinstance mytable> constraint -t mytable -a com.test.ExampleConstraint com.test.AnotherConstraint
+user@myinstance mytable> constraint -l
+com.test.ExampleConstraint=1
+com.test.AnotherConstraint=2
 \end{verbatim}
 \normalsize
 
@@ -219,14 +214,11 @@ table as follows:
 
 \small
 \begin{verbatim}
-user@myinstance mytable> config -t mytable -s
-table.iterator.scan.vers.opt.maxVersions=3
+user@myinstance mytable> config -t mytable -s table.iterator.scan.vers.opt.maxVersions=3
 
-user@myinstance mytable> config -t mytable -s
-table.iterator.minc.vers.opt.maxVersions=3
+user@myinstance mytable> config -t mytable -s table.iterator.minc.vers.opt.maxVersions=3
 
-user@myinstance mytable> config -t mytable -s
-table.iterator.majc.vers.opt.maxVersions=3
+user@myinstance mytable> config -t mytable -s table.iterator.majc.vers.opt.maxVersions=3
 \end{verbatim}
 \normalsize
 



Mime
View raw message