Remove deprecated ShardManagerSnapshot The original ShardManagerSnapshot was deprecated in Boron and thus should be safe to remove now. Change-Id: I643dcf6e06ad4842b69bf1ab1992b028786c83f8 Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
BUG-2138: Create DistributedShardFrontend Use the abstract shard implementations from md-sal to create a frontend implementation of a cds shard that forwards requests to backend shards via DistributedDatastoreClient. Change-Id: I7a3485f414368728e71ab2746c84d7a0f83f1436 Signed-off-by: Tomas Cere <tcere@cisco.com>
Bug 7521: Convert byte[] to ShardManagerSnapshot in DatastoreSnapshot Created a new ShardManagerSnapshot class in the persisted package which is now stored in the DatastoreSnapshot in lieu of a serialized byte[]. The previous ShardManagerSnapshot class was deprecated and readResolves to the new class. Change-Id: I1ae363e9711cf3bef6b6dd6257fa56bd41465bf3 Signed-off-by: Tom Pantelis <tpanteli@brocade.com>
Fix warnings/javadocs in sal-distributed-datastore First off, I apologize for the size of this patch. There's a ton of classes in this project and I didn't even get to all of them (will follow-up). While a lot of files were touched, the changes were mostly small. Fixed a lot of checkstyle warnings and cleaned up javadocs. Most of the warnings/changes were for: - white space before if/for/while/catch - white space before beginning brace - line too long - illegal catching of Exception (suppressed) - variable name too short - indentation - missing period after first sentence in javadoc - missing first sentence in javadoc - missing <p/> in javadoc Change-Id: Id56d874a8fbcbbc9285279a71c0a5aba393653a9 Signed-off-by: Tom Pantelis <tpanteli@brocade.com>
Move ShardManagerSnapshot to new package This creates a copy of the ShardManagerSnapshot in the new package and uses readResolve() to perform migration. Change-Id: I976adbaafd74de64a90d3970e17ce4ea52bdbe40 Signed-off-by: Robert Varga <rovarga@cisco.com>
BUG 2187 - Persisting shard list in ShardManager In ShardManager, the local shard list is persisted as a snapshot. On recovery, persisted shard list is used to create the shards. During recovery, obtained persisted information is updated to the configuration so that it is uniformly available to the DatastoreContext. Incorporated the comments Also, as localShards are now created after RecoveryCompletion, the shardManager mbean is associated with the shardManager immediately after creation. On creating the localShards, the shards addition is notified to the mbean object. In the shardManagerTests involving verification of the syncStatus and CountDownLatch objects, the testcases are made to wait for localShard creation by waiting for recoveryCompletion message. Change-Id: I523ed9b14af4b1b6e272f05faac1cf37abfef336 Signed-off-by: kalaiselvik <Kalaiselvi_K@Dell.com>