W E K A
4.1
4.1
  • WEKA v4.1 documentation
  • WEKA System Overview
    • About the WEKA system
    • SSD capacity management
    • Filesystems, object stores, and filesystem groups
    • WEKA networking
    • Data lifecycle management
    • WEKA client and mount modes
    • WEKA containers architecture overview
    • Glossary
  • Getting Started with WEKA
    • Quick installation guide
    • Manage the system using the WEKA CLI
    • Manage the system using the WEKA GUI
    • Run first IOs with WEKA filesystem
    • Getting started with WEKA REST API
  • Planning and Installation
    • Prerequisites for installation
    • WEKA installation on bare metal
      • Plan the WEKA system Installation
      • Prepare the system for WEKA software installation
        • Enable the SR-IOV
      • Obtain the WEKA software installation package
      • WEKA cluster installation
        • WEKA legacy system installation process
      • Add clients
    • WEKA installation on AWS
      • Self-service portal
      • CloudFormation template generator
      • Deployment types
      • AWS outposts deployment
      • Supported EC2 instance types
      • Add clients
      • Auto scaling group
      • Troubleshooting
    • WEKA installation on Azure
    • WEKA installation on GCP
      • WEKA project description
      • Deployment on GCP using Terraform
      • GCP Terraform package description
      • Required services and supported regions
      • Supported machine types and storage
      • Auto-scale instances in GCP
      • Add clients
      • Troubleshooting
  • 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
    • 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
    • Manage the NFS protocol
      • Supported NFS client mount options
      • Manage NFS networking using the GUI
      • Manage NFS networking using the CLI
    • Manage the SMB protocol
      • Manage SMB using the GUI
      • Manage SMB 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
  • 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
    • 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
    • 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 in a multiple containers architecture
      • Add a backend server in a legacy architecture
      • Expand specific resources of a container
      • Shrink a cluster
    • Background tasks
    • Upgrade WEKA versions
  • Billing & Licensing
    • License overview
    • Classic license
    • Pay-As-You-Go license
  • Support
    • Prerequisites and compatibility
    • 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
    • Weka Home - The WEKA support cloud
      • Local Weka Home overview
      • Local Weka Home deployment
      • Set the Local Weka Home to send alerts or events
      • Download the Usage Report or Analytics
  • Appendix
    • WEKA CSI Plugin
    • Set up the WEKAmon external monitoring
    • Set up the SnapTool external snapshots manager
  • REST API Reference Guide
Powered by GitBook
On this page
  • Add a backend server to an existing cluster
  • Expand the cluster by importing the container settings
  1. Operation Guide
  2. Expand and shrink cluster resources

Add a backend server in a legacy architecture

PreviousAdd a backend server in a multiple containers architectureNextExpand specific resources of a container

Last updated 1 year ago

Expanding a cluster in a legacy architecture with a new backend server is similar to the WEKA legacy system installation process.

Adding a server to the cluster includes adding the containers and configuring the networking, CPU resources, and SSDs.

Note: In most cases, the container configurations are similar. Therefore, importing the container settings from a previously exported container in the cluster is possible, saving time and avoiding misconfiguration. See .

Add a backend server to an existing cluster

  1. Obtain the WEKA install file.

    • Download the WEKA install file used when the existing cluster was last upgraded (or formed, if not upgraded). See Obtain the WEKA software installation package.

    • Use the weka status command to show the current cluster install file version.

  2. Install the WEKA software on the new server.

    • Run the untar command and install.sh command on the new server. At the end of the installation process, the server is in stem mode (the server is not attached to a cluster).

  3. Add the container to the cluster.

    • Run the following command line on any container in the cluster. In the backend-hostname property, specify the IP address or hostname of the new backend server to add.

weka cluster container add <backend-hostname>

Note: Once this step is completed, the container ID of the newly added server appears in response to the command. Make a note of it to use in the following steps.

  1. Configure the networking.

  2. Configure the CPU resources.

  3. Apply the configuration of the container on the newly added server.

Note: You can activate the cluster containers sequentially.

  1. Configure the SSDs.

Expand the cluster by importing the container settings

In most cases, the server configurations are similar. Therefore, importing the server setting from a previously exported server in the cluster is possible, saving time and avoiding misconfiguration.

Procedure:

  1. Connect to one of the servers in the cluster and export the settings by running the following command: weka local resources export.

  2. Connect to the new server and import the settings by running the following command: weka local resources import.

  3. Edit the local configuration.

  4. Apply the configuration on the newly added server.

Perform the instructions in .

Perform the instructions in .

Perform the instructions in .

Perform the instructions in .

Perform only steps 1 to 3 in the procedure (above).

See the section.

See .

Add a backend server to an existing cluster
Expand the cluster by importing the server settings
#local-resources-editing-commands
Adding a server to the cluster in a legacy architecture
#stage-6-configure-the-networking
#stage-8-configure-the-cpu-resources
Stage 13: Apply containers configuration
#7.-configure-the-ssds
Stage 13: Apply containers configuration