Permalink
Browse files

Prepare to release (special) version 1.1.4 based off of version 0.96.…

…li7.
  • Loading branch information...
1 parent 82072ac commit 76c6c48c06f44aaecf70bd9753774e4983906669 Chinmay Soman committed Nov 27, 2012
View
2 build.properties
@@ -37,4 +37,4 @@ tomcat.manager.password=tomcat
tomcat.context=/voldemort
## Release
-curr.release=0.96
+curr.release=1.1.4
View
BIN lib/google-collect-1.0-rc2.jar
Binary file not shown.
View
BIN lib/google-collect-1.0.jar
Binary file not shown.
View
93 release_notes.txt
@@ -1,3 +1,96 @@
+Release 1.1.4 on 11/28/2012
+
+This is a special release based off of release 0.96.li7. Its purpose is to
+isolate the client-registry branch from the other changes made since 0.96.li7
+and to make the same available to all the Voldemort clients within LinkedIn.
+
+Changes made since 0.96.li7
+* Made DefaultStoreClient as default
+* Removed logging stack trace in LazyStoreClient
+
+Release 0.96.li7 (LinkedIn release) on 09/21/2012
+
+Changes made since 0.96.li6
+* Added server side system stores for managing metadata
+* Added system store client for interacting with System Stores
+* Added a new routing strategy to route to all with local preference
+* Added a auto-bootstrap mechanism triggered by metadata changes
+* Added a client-registry for publishing client info and config values
+* Added a new Voldemort client : ZenStoreClient to work with the system stores
+* Enhanced Admin tool to work with the new system stores
+* Updated LazyClientStore to try to bootstrap during Init
+* Modified Failure Detector to work on a shared cluster object reference
+* New tests for testing the auto-bootstrap and system store functionality
+
+Release 0.96.li6 (LinkedIn release) on 09/19/2012
+
+Changes made since 0.96.li5
+* Changed getall return behavior to comply with javadoc
+
+Release 0.96.li5 (LinkedIn release) on 09/06/2012
+
+Changes made since 0.96.li2
+* Added server config to control socket backlog
+* Added "--query-keys" option to query multiple keys of multiple stores from
+* specific node
+* Added control to DataCleanupJob Frequency
+* Improved messages in request tracing
+* Cleaned up help/usage messages within the client shell
+* Unified jmxid as the factory across the board
+* Fixed a bug that caused unnecessary serial requests in getall
+* Fixed a bug that prevented "--fetch-keys" and "--fetch-entries" in admin
+* tool from showing multiple store results
+* Fixed problem in sample config that prevented the server from starting
+* Fixed random rebalance test failures
+
+Release 0.96.li2 (LinkedIn release) on 08/01/2012
+
+Changes made since 0.96.li1
+* HFTP performance issue bug fix (fix in byte buffer and copy process)
+* Added mechanism to isolate BDB cache usage among stores
+* Enhanced debug logging (for traffic analysis).
+* Python client bug fixes (from pull request)
+* Tooling improvement (generate_cluster_xml.py)
+
+Release 0.96.li1 (LinkedIn release) on 07/12/2012
+
+Changes made since 0.95.li9
+* Reuploaded the jar
+
+Changes made since 0.95.li4
+* Added configurable option to interrupt service being unscheduled
+* Added rollback capability to the Admin tool
+* Added tracking functionality for scan permit owner
+* Added zoned option for restore from replicas
+* Enabled NIO connector by default
+* Added client side MBeans for multiple socket pool metrics
+* Shortened some long tests and created new target called "junit-long" that
+* includes them
+* Finer timeouts and partial getalls
+* Refactored to share VodemortOpCode between classes
+* Fixed a donor-based rebalancing bug and added a unit test
+* Fixed a bug that will return null during concurrent read and writes
+* Added jmxId to Mbean name for failureDetector and storefactory
+* Prevent preferred reads from crossing zones
+* Added additional debug messages
+
+Release 0.95.li4 (LinkedIn release) on 04/13/2012
+
+Changes made since 0.95.li3
+* Added error count Mbeans
+* Concurrency bug fix in Donor based rebalancing
+
+Release 0.95.li3 (LinkedIn release) on 03/22/2012
+
+Changes made since 0.95.li2
+ * HOTFIX - DDS-2536: Fixed FailureDetector to handle host swap
+
+Release 0.95.li2 (LinkedIn release) on 03/21/2012
+
+Changes made since 0.95.li1
+ * Hot fix for SNA-10109. Replaced exception by log message in Histogram
+ * Replaced int by long to avoid overflow in Histogram and RequestCounter
+
Release 0.90.1 on 10/10/2011
Changes made since 0.90
View
4 src/java/voldemort/client/ClientConfig.java
@@ -68,8 +68,8 @@
private volatile boolean enablePipelineRoutedStore = true;
private volatile int clientZoneId = Zone.DEFAULT_ZONE_ID;
- // Flag to control which store client to use. Default = Enhanced
- private volatile boolean useDefaultClient = false;
+ // Flag to control which store client to use. Default = old client
+ private volatile boolean useDefaultClient = true;
private volatile String failureDetectorImplementation = FailureDetectorConfig.DEFAULT_IMPLEMENTATION_CLASS_NAME;
private volatile long failureDetectorBannagePeriod = FailureDetectorConfig.DEFAULT_BANNAGE_PERIOD;
View
1 src/java/voldemort/client/LazyStoreClient.java
@@ -61,7 +61,6 @@ public LazyStoreClient(Callable<StoreClient<K, V>> storeClientThunk, boolean ins
storeClient = initStoreClient();
} catch(Exception e) {
storeClient = null;
- e.printStackTrace();
logger.info("Could not bootstrap right away. Trying on the next call ... ");
}
}

0 comments on commit 76c6c48

Please sign in to comment.