TableManager start to support query for indexletInfo
Add indexlet list into Tablets.proto. Current Coordinator can send indexlet information to RecoveryMaster
RecoveryMaster can create corresponding Indexlet, and will fillin serverid, locator info to returning protobuf
add functionality for recovery failure case
draft version of index recovery completed. Current code can pass unitests
1. Fixed several bugs in TableManager.cc and Recovery.cc
2. Add a test case for index recovery. The test case has been passed.
To make it pass:
  make tests
  make check
Several changes to ClusterPerf:
  1. Use loopupindexkeys to test index recovery
  2. Add a BTree construction function which can pass highestBTreeId
  3. Fix several bugs in ClusterPerf and IndexletManager
implement highestusedID mechanism that would add new node to be added into recovered indexletTable
fix conflicts in IndexletManager.cc and TableManager.cc
can compile at this point, start to change Tablets.proto => ReocveryMsg.proto
Implement new protocol buffer for recovery messages
address code review comments[901001]
add unit test for recovery.cc
make highestBTreeIdMap a local variable in MasterService
1. Address code review comments in http://rccodereview.appspot.com/901001/show.
2. Add unit tests code to check functionalities of index recovery.
3. Add runtime tests to check workability.
Add new Protocol Buffer message RecoveryPartition into repo.

The purpose of RecoveryPartition is to provide communication
protocol between coordinator and recoveryMaster during crash
recovery. RecoveryPartition goes both directions during a
recovery, which means coordinator sends it to recoveryMaster,
and recoveryMaster will send it back to coordinator.
move highestUsedId setting into IndexletManager
finish indexlookup class
1) Fixes formatting and readability of test results from
previous commit.
2) Removed extensive measurements and printing from indexing
benchmarks. Currently, only the median values are printed.