Expansion of specific resources
This page provides the guidelines for expansion processes that only involve the addition of specific resources.
Most modifications to host configurations can be performed dynamically, without deactivating the host. Such configurations include the addition/removal of memory and network resources, changing IPs, extending network subnets and limiting the Weka system bandwidth on the host.
All these changes can be performed using the relevant
weka cluster hostcommand. Once this command is used with a specific
host-idselected, it will be staged for update on the cluster. To view the un-applied configuration, use the
weka cluster host resources <host-id>command. To apply the changes, use the
weka cluster host apply <host-ids>command. You can also apply these changes locally using the
weka local resources applycommand.
The last local configuration (of a host that successfully joined a cluster) is saved. If a failure/problem occurs with the new configuration, the host will automatically revert to the last known good configuration. To view this configuration, use the
weka cluster host resources <host-id> --stablecommand.
To dynamically change the host's management IPs, you can use the
management-ipsresource editing command.
It is also possible to run modification commands locally on the host by connecting to the desired host and running a
local resourcescommand equivalent to its
weka cluster hostcounterpart. These local commands have the same semantics of their remote counterparts only that they don't receive the host-id as the first parameter and operate instead on the local host.
Commands that can be performed dynamically on an Active host:
weka local resources [--stable] weka local resources apply weka local resources net weka local resources net add weka local resources net remove weka local resources memory weka local resources bandwidth weka local resources management-ips weka local resources dedicate
The following commands cannot be performed on an Active host and require deactivating the host first using
weka cluster host deactivate:
weka local resources failure-domain weka local resources cores
For more information, contact the WekaIO Support Team.