W E K A
4.3
4.3
  • WEKA v4.3 documentation
    • Documentation revision history
  • WEKA System Overview
    • WEKA Data Platform introduction
      • WEKA system functionality features
      • Converged WEKA system deployment
      • Optimize redundancy in WEKA deployments
    • SSD capacity management
    • Filesystems, object stores, and filesystem groups
    • WEKA networking
    • Data lifecycle management
    • WEKA client and mount modes
    • WEKA containers architecture overview
    • Glossary
  • Planning and Installation
    • Prerequisites and compatibility
    • WEKA cluster installation on bare metal servers
      • Plan the WEKA system hardware requirements
      • Obtain the WEKA installation packages
      • Install the WEKA cluster using the WMS with WSA
      • Install the WEKA cluster using the WSA
      • Manually install OS and WEKA on servers
      • Manually prepare the system for WEKA configuration
        • Broadcom adapter setup for WEKA system
        • Enable the SR-IOV
      • Configure the WEKA cluster using the WEKA Configurator
      • Manually configure the WEKA cluster using the resource generator
      • Perform post-configuration procedures
      • Add clients to an on-premises WEKA cluster
    • WEKA Cloud Deployment Manager Web (CDM Web) User Guide
    • WEKA Cloud Deployment Manager Local (CDM Local) User Guide
    • WEKA installation on AWS
      • WEKA installation on AWS using Terraform
        • Terraform-AWS-WEKA module description
        • Deployment on AWS using Terraform
        • Required services and supported regions
        • Supported EC2 instance types using Terraform
        • WEKA cluster auto-scaling in AWS
        • Detailed deployment tutorial: WEKA on AWS using Terraform
      • WEKA installation on AWS using the Cloud Formation
        • Self-service portal
        • CloudFormation template generator
        • Deployment types
        • AWS Outposts deployment
        • Supported EC2 instance types using Cloud Formation
        • Add clients to a WEKA cluster on AWS
        • Auto scaling group
        • Troubleshooting
      • Install SMB on AWS
    • WEKA installation on Azure
    • WEKA installation on GCP
      • WEKA project description
      • GCP-WEKA deployment Terraform package description
      • Deployment on GCP using Terraform
      • Required services and supported regions
      • Supported machine types and storage
      • Auto-scale instances in GCP
      • Add clients to a WEKA cluster on GCP
      • Troubleshooting
      • Detailed deployment tutorial: WEKA on GCP using Terraform
      • Google Kubernetes Engine and WEKA over POSIX deployment
  • Getting Started with WEKA
    • Manage the system using the WEKA GUI
    • Manage the system using the WEKA CLI
      • WEKA CLI hierarchy
      • CLI reference guide
    • Run first IOs with WEKA filesystem
    • Getting started with WEKA REST API
    • WEKA REST API and equivalent CLI commands
  • Performance
    • WEKA performance tests
      • Test environment details
  • WEKA Filesystems & Object Stores
    • Manage object stores
      • Manage object stores using the GUI
      • Manage object stores using the CLI
    • Manage filesystem groups
      • Manage filesystem groups using the GUI
      • Manage filesystem groups using the CLI
    • Manage filesystems
      • Manage filesystems using the GUI
      • Manage filesystems using the CLI
    • Attach or detach object store buckets
      • Attach or detach object store bucket using the GUI
      • Attach or detach object store buckets using the CLI
    • Advanced data lifecycle management
      • Advanced time-based policies for data storage location
      • Data management in tiered filesystems
      • Transition between tiered and SSD-only filesystems
      • Manual fetch and release of data
    • Mount filesystems
      • Mount filesystems from Single Client to Multiple Clusters (SCMC)
    • Snapshots
      • Manage snapshots using the GUI
      • Manage snapshots using the CLI
    • Snap-To-Object
      • Manage Snap-To-Object using the GUI
      • Manage Snap-To-Object using the CLI
    • Quota management
      • Manage quotas using the GUI
      • Manage quotas using the CLI
  • Additional Protocols
    • Additional protocol containers
    • Manage the NFS protocol
      • Supported NFS client mount parameters
      • Manage NFS networking using the GUI
      • Manage NFS networking using the CLI
    • Manage the S3 protocol
      • S3 cluster management
        • Manage the S3 service using the GUI
        • Manage the S3 service using the CLI
      • S3 buckets management
        • Manage S3 buckets using the GUI
        • Manage S3 buckets using the CLI
      • S3 users and authentication
        • Manage S3 users and authentication using the CLI
        • Manage S3 service accounts using the CLI
      • S3 rules information lifecycle management (ILM)
        • Manage S3 lifecycle rules using the GUI
        • Manage S3 lifecycle rules using the CLI
      • Audit S3 APIs
        • Configure audit webhook using the GUI
        • Configure audit webhook using the CLI
        • Example: How to use Splunk to audit S3
      • S3 supported APIs and limitations
      • S3 examples using boto3
      • Access S3 using AWS CLI
    • Manage the SMB protocol
      • Manage SMB using the GUI
      • Manage SMB using the CLI
  • Operation Guide
    • Alerts
      • Manage alerts using the GUI
      • Manage alerts using the CLI
      • List of alerts and corrective actions
    • Events
      • Manage events using the GUI
      • Manage events using the CLI
      • List of events
    • Statistics
      • Manage statistics using the GUI
      • Manage statistics using the CLI
      • List of statistics
    • Insights
    • System congestion
    • Security management
      • Obtain authentication tokens
      • KMS management
        • Manage KMS using the GUI
        • Manage KMS using the CLI
      • TLS certificate management
        • Manage the TLS certificate using the GUI
        • Manage the TLS certificate using the CLI
      • CA certificate management
        • Manage the CA certificate using the GUI
        • Manage the CA certificate using the CLI
      • Account lockout threshold policy management
        • Manage the account lockout threshold policy using GUI
        • Manage the account lockout threshold policy using CLI
      • Manage the login banner
        • Manage the login banner using the GUI
        • Manage the login banner using the CLI
      • Manage Cross-Origin Resource Sharing
    • User management
      • Manage users using the GUI
      • Manage users using the CLI
    • Organizations management
      • Manage organizations using the GUI
      • Manage organizations using the CLI
      • Mount authentication for organization filesystems
    • Expand and shrink cluster resources
      • Add a backend server
      • Expand specific resources of a container
      • Shrink a cluster
    • Background tasks
      • Set up a Data Services container for background tasks
      • Manage background tasks using the GUI
      • Manage background tasks using the CLI
    • Upgrade WEKA versions
  • Licensing
    • License overview
    • Classic license
  • Monitor the WEKA Cluster
    • Deploy monitoring tools using the WEKA Management Station (WMS)
    • WEKA Home - The WEKA support cloud
      • Local WEKA Home overview
      • Deploy Local WEKA Home v3.0 or higher
      • Deploy Local WEKA Home v2.x
      • Explore cluster insights and statistics
      • Manage alerts and integrations
      • Enforce security and compliance
      • Optimize support and data management
    • Set up the WEKAmon external monitoring
    • Set up the SnapTool external snapshots manager
  • Support
    • Get support for your WEKA system
    • Diagnostics management
      • Traces management
        • Manage traces using the GUI
        • Manage traces using the CLI
      • Protocols debug level management
        • Manage protocols debug level using the GUI
        • Manage protocols debug level using the CLI
      • Diagnostics data management
  • Best Practice Guides
    • WEKA and Slurm integration
      • Avoid conflicting CPU allocations
    • Storage expansion best practice
  • WEKApod
    • WEKApod Data Platform Appliance overview
    • WEKApod servers overview
    • Rack installation
    • WEKApod initial system setup and configuration
    • WEKApod support process
  • Appendices
    • WEKA CSI Plugin
      • Deployment
      • Storage class configurations
      • Tailor your storage class configuration with mount options
      • Dynamic and static provisioning
      • Launch an application using WEKA as the POD's storage
      • Add SELinux support
      • NFS transport failback
      • Upgrade legacy persistent volumes for capacity enforcement
      • Troubleshooting
    • Convert cluster to multi-container backend
    • Create a client image
    • Update WMS and WSA
    • BIOS tool
Powered by GitBook
On this page
  • Before you begin
  • Remove only some drives from the cluster
  • Deactivate drives
  • Remove drives from the cluster
  • Remove containers with their allocated drives
  • Deactivate containers
  • Remove containers from the cluster
  1. Operation Guide
  2. Expand and shrink cluster resources

Shrink a cluster

PreviousExpand specific resources of a containerNextBackground tasks

Shrinking a cluster may be required when you need to reduce the cluster's costs, and the performance degradation does not affect your business.

You can shrink the cluster by performing one of the following:

  • Remove only some drives from the cluster.

  • Remove containers with their allocated drives.

Removing drives or containers requires deactivating the drives you want to remove. But, if the deactivation leads to insufficient SSD capacity of the currently-provisioned filesystems, the WEKA system does not deactivate the drives, and shrinking the cluster is not allowed.

Before you begin

Run the following command to display a list of all the drives in the cluster with their details, such as UUID and status:

weka cluster drive

Example
root@void-new-1:~# weka cluster drive
DISK ID  UUID                                  HOSTNAME     NODE ID  SIZE      STATUS    LIFETIME % USED  ATTACHMENT  DRIVE STATUS
37       84c4574d-5a46-4644-91aa-df1ceef27ff1  void-new-10  1921     1.09 TiB  ACTIVE    0                OK          OK
45       ecd05959-629c-4319-9d24-f69497c499e3  void-new-19  2401     1.09 TiB  ACTIVE    0                OK          OK
46       4c8af0fa-894b-4096-adb6-17fe98a3a690  void-new-17  2281     1.09 TiB  ACTIVE    0                OK          OK
47       49f684d0-9f2e-4b0a-9153-9aa3570067bd  void-new-18  2341     1.09 TiB  ACTIVE    0                OK          OK
57       7202db57-1f4e-4332-a132-33a47a729d46  void-new-0   1141     1.09 TiB  INACTIVE  0                OK
58       6c2ad35b-a1ff-4b30-9882-0ed3ec166747  void-new-1   1321     1.09 TiB  ACTIVE    0                OK          OK
59       ae8dd40a-9d3d-4154-a26d-3e9643f59e6f  void-new-2   1381     1.09 TiB  ACTIVE    0                OK          OK
60       b96e3c32-3a29-436a-ac35-2e8cf6808e9a  void-new-3   1441     1.09 TiB  ACTIVE    0                OK          OK
61       63ab4d5d-82ed-4248-9ce1-817ce5d7e106  void-new-4   1501     1.09 TiB  ACTIVE    0                OK          OK
62       0f303d2c-5fd0-47e6-9150-0da4afcc454b  void-new-5   1561     1.09 TiB  ACTIVE    0                OK          OK
63       d21f4b3b-1458-4402-8592-06e7ca426d9c  void-new-6   1621     1.09 TiB  ACTIVE    0                OK          OK
64       0c3de49c-b123-4b0b-bd64-e7a90454b41d  void-new-7   1681     1.09 TiB  ACTIVE    0                OK          OK
65       c519e608-ae1d-402e-9f10-da69b227d2c8  void-new-8   1741     1.09 TiB  ACTIVE    0                OK          OK
66       80d53c1d-206e-4021-848b-e52b47bf32fa  void-new-9   1801     1.09 TiB  ACTIVE    0                OK          OK
68       3d669d70-6db2-4a7d-a13b-47ad531f43dd  void-new-11  1861     1.09 TiB  ACTIVE    0                OK          OK
69       ded74ec1-d208-41a9-af2d-eb1c1e81e613  void-new-12  1981     1.09 TiB  ACTIVE    0                OK          OK
70       4451db18-8417-4d4f-b5d0-02bad359b9ff  void-new-13  2041     1.09 TiB  ACTIVE    0                OK          OK
71       019f2b88-c284-4cf4-b384-0a0fde6ea128  void-new-14  2101     1.09 TiB  ACTIVE    0                OK          OK
72       7a315ea8-9f12-4143-b67b-213f2f3f6748  void-new-15  2161     1.09 TiB  ACTIVE    0                OK          OK
73       dce3f522-5672-4964-8db8-383774c11569  void-new-16  2221     1.09 TiB  ACTIVE    0                OK          OK

Remove only some drives from the cluster

Perform the following:

  1. .

  2. .

Deactivate drives

Drive deactivation starts an asynchronous process known as phasing out. It is a gradual redistribution of the data between the remaining drives in the system. On completion, the phased-out drives are in an inactive state. The WEKA cluster does not use inactive drives, but they still appear in the drives list.

To deactivate a drive, run the following command:

weka cluster drive deactivate <uuids>

Parameters

Name
Value

uuids*

Comma-separated drive identifiers.

Running the weka cluster drive command is displayed whether the redistribution is still being performed.

Remove drives from the cluster

Once you remove a drive from the cluster, the drive is not recoverable.

To remove a drive, run the following command:

weka cluster drive remove <uuids>

Parameters

Name
Value

Name

Value

uuids*

Comma-separated drive identifiers.

Remove containers with their allocated drives

Perform the following:

Deactivate containers

To deactivate containers with their drives, run the following command:

weka cluster container deactivate <container-ids> [--allow-unavailable]

Parameters

Name
Value
Default

container-ids*

Space-separated container identifiers

allow-unavailable

Allow deactivation of an unavailable container. If the container-id value returns, it joins the cluster in an active state.

No

Remove containers from the cluster

Removing containers from the cluster switches them to a stem mode (not part of a cluster), so they can be reallocated to another cluster or purpose.

To remove the container from the cluster, run the following command:

weka cluster container remove <container-id>

Parameters

Name
Value

container-id*

Comma-separated container identifiers.

.

.

Deactivate drives
Remove drives from the cluster
Deactivate containers
Remove containers from the cluster