Unfolding a System

Prerequisite
  • Make sure you have increased limits. Read about COP entries and make sure your system is properly configured.
  • Create a new system image if a previous restore image was generated or if you have upgraded software since deploying an instance that you are unfolding.
  • For BYOL, make sure you have enough TCores before you unfold the system.
Use this procedure for any of the following:
  • If you did not initially unfold a system during deployment
  • If you previously unfolded a system during deployment and want to unfold again after deployment

It takes about 20 minutes for a 2 node system and 30 minutes for a 4 node system, depending on the number of EBS volumes and AWS provisioning time.

  1. [First time you unfold] Check to see if your system can be unfolded:
    # tdc-unfold -d
  2. Enter one of the following commands to start the unfold process:
    CommandDescription
    # tdc-unfold 2xDoubles the current node count.

    For example, if the current system has 4 nodes, the unfolded system will have 8 nodes.

    # tdc-unfold 4x

    Quadruples the current node count.

    For example, if the current system has 4 nodes, the unfolded system will have 16 nodes.

    The output displays how the configuration changes after the system has unfolded, as shown in the following example:
    Current system will be unfolded by [2x]:
    ===========================================================================
     Nodes:
             Node Count:    2 => 4
    ---------------------------------------------------------------------------
     CPU(Core)/Mem(GB):
              CPUs/Node:   16 == 16       CPUs Total:   32 => 64
               Mem/Node:   65 == 65        Mem Total:  130 => 260
    ---------------------------------------------------------------------------
     AMPs/PEs:
              AMPs/Node:   20 => 10       AMPs Total:   40 == 40
               PEs/Node:    2 == 2         PEs Total:    4 => 8
    ===========================================================================
    Continue? [yes/no] yes
  3. Enter yes.
    When the process completes, the new configuration appears under Current Configuration.
  4. [Optional] Check the status of the database.
    # pdestate –a
  5. [Optional] Check the logs for troubleshooting.

results matching ""

    No results matching ""