https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1405 controller <p>Currently we have 2 options. Create a shard per module and put the all the modules which do not have a configured shard into the default shard. It would be nice if we could have the data for some related modules stored together in one shard. This will help us distribute data better across a cluster without forcing us to configure one shard per module which has it's own overhead (RAFT related heartbeats and such)</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1405

Provide ability to put content of multiple modules in a single shard

Improvement Resolved Duplicate Natarajan Dhiraviam Moiz Raja Tue, 18 Aug 2015 10:44:54 +0000 Wed, 14 Nov 2018 12:21:00 +0000 Wed, 14 Nov 2018 12:20:42 +0000 Lithium clustering 0 3 <p>Moiz notes via email:</p> <p>A shard can contain,<br/> a single modules data<br/> a subset of a modules data<br/> data for multiple modules<br/> The original configuration was designed only for case 1 and 2.</p> <p>So let’s say inventory could actually be split into 2 shards we would have a configuration as follows,</p> <p>name=“inventory”<br/> shards = [<br/> </p> { name=“inventory-1”, replicas=[“member-1”, “member-2”] } <p>,</p> { name=“inventory-2”, replicas=[“member-1”, “member-3”] } <p>]</p> <p>The ShardStrategy would then be able to figure out if the data went in “inventory-1” or “inventory-2” shard.</p> <p>So based on the initial design we would need to have the configuration as follows.</p> <p>name=“inventory,topology”<br/> shards = [</p> { name=“inventory-topology”, replicas=[“member-1”, “member-2”] } <p>]</p> <p>which basically says that inventory and topology data goes into the inventory-topology shard.</p> <p>Conclusion from last discussion was : <br/> + to support data for related modules stored together in one shard (multiple modules in one shard)<br/> Example : LACP extends node from inventory &amp; it makes sense to have them <br/> both part of same shard.</p> <p> So initial configuration would like this:<br/> name=“inventory,lacp”<br/> shards = [</p> { name=“inventory-lacp”, replicas=[“member-1”, “member-2”] } <p> ]</p> <p> + Until micro-sharding strategy aspects are worked out, spanning a module across shards shall not be considered.</p> <p>For multi-module sharding, tried aggregating inventory &amp; lacp into a single shard, in a Single Node cluster setup. Was able to see inventory-lacp shard becoming Leader successfully.<br/> Below was the modification in the conf file.<br/> modules.conf:<br/> -------------</p> { name = "lacp" namespace = "urn:opendaylight:lacp:lacp-main" shard-strategy = "module" } <p>module-shards.conf:<br/> -------------------<br/> { <br/> name = "inventory,lacp"<br/> shards = [ </p> { name="inventory-lacp" replicas = [ "member-1" ] } <p> ] <br/> }</p> <p>Attached is the karaf log extract, jolokia output</p> <p>For multi-module sharding, tried aggregating inventory &amp; lacp into a single shard, in a Single Node cluster setup. Was able to see inventory-lacp shard becoming Leader successfully.<br/> Below was the modification in the conf file.<br/> modules.conf:<br/> -------------</p> { name = "lacp" namespace = "urn:opendaylight:lacp:lacp-main" shard-strategy = "module" } <p>module-shards.conf:<br/> -------------------<br/> { <br/> name = "inventory,lacp"<br/> shards = [ </p> { name="inventory-lacp" replicas = [ "member-1" ] } <p> ] <br/> }</p> <p>Attached is the karaf log extract, jolokia output</p> <p>Attachment inv-lacp.log has been added with description: Karaf output inventory-lacp multi-module shard karaf log extract for single node cluster</p> <p>Attachment JolokiaOutput.txt has been added with description: JolokiaOutput inventory-lacp multi-module shard Jolokia output for single node cluster</p> Blocks CONTROLLER-1857 Duplicate CONTROLLER-918 Development External issue ID 4150 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i02qdb: