No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionStorage V100R006C30 Block Storage Service Troubleshooting Guide 05

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Manually Rolling back the Switchover from Single-Pool Mode to Multi-Pool Upon a Failure

Manually Rolling back the Switchover from Single-Pool Mode to Multi-Pool Upon a Failure

Scenarios

If administrators fail to switch the FusionStorage Block system from multi-pool mode to single-pool mode using scripts, manually modify the configuration file on the FSM node, and ZooKeeper, MDC, VBS, OSD, or VFS configuration file on the FSA node to complete the switch.

Prerequisites

Conditions

  • Floating IP address of FSM nodes
  • Password of user root as well as the username and password used for logging in to the FSA node

Procedure

    Locate all the nodes.

    1. On FusionStorage Block Self-Maintenance Platform, choose Resource Pool > Summary.

      The page similar to Figure 4-1 is displayed.

      Figure 4-1  Summary

    2. In the Process status pane, check all the FSA nodes and the types of processes running on these nodes.

      Log in to each FSA node and modify the configuration files based on the types of the running processes.

    Modify the configuration file on the active FSM node.

    1. Use PuTTY and the management plane IP address of the active FSM node to log in to the active FSM node.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode in the FusionStorage Block Storage Service Administrator Guide.

    2. Run the following command and enter the password of user root to switch to user root:

      su - root

    3. Run the following command to open the FSM configuration file SystemConfiguration.xml using the vi editor:

      vi /opt/dsware/manager/webapps/dsware/WEB-INF/SystemConfiguration.xml

    4. Press i to enter editing mode.
    5. Edit the SystemConfiguration.xml file.

      Change the value of g_multy_pool_feature_pool_num to 2.

      The file content is as follows:
      <g_multy_pool_feature_pool_num desc="The max pool number in system." range="[1:128]" type="initial">2</g_multy_pool_feature_pool_num>

    6. Press Esc and enter :wq to save the configuration and exit the vi editor.
    7. Run the following command to restart the Tomcat process as user omm:

      su - omm -c restart_tomcat

      The command is successfully executed if the following information is displayed:
      Tomcat is restarted successfully.

    (Optional) Modify the ZooKeeper configuration file.

    Perform this step only on the FSA nodes with ZooKeeper processes deployed. You can obtain the process topology from 2.

    1. Use PuTTY to log in to the FSA node with the ZooKeeper process deployed.

      Ensure that the management IP address of the FSA node is used to establish the connection.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode in the FusionStorage Block Storage Service Administrator Guide.

    2. Run the following command and enter the password of user root to switch to user root:

      su - root

    3. Run the following command to open the ZooKeeper configuration file java.env using the vi editor:

      vi /opt/dsware/agent/zk/conf/java.env

    4. Press i to enter editing mode.
    5. Edit the java.env file.

      Change -Xms and -Xmx in the export JVMFLAGS= field to -Xms1450m and -Xmx1450m, respectively.

      The file content after modification is as follows:
      export JVMFLAGS="-Xms1450m –Xmx1450m -XX:ErrorFile=/var/log/dsware/hs_err_pid%p.log.0 $JVMFLAGS"

    6. Press Esc and enter :wq to save the configuration and exit the vi editor.
    7. Run the following command to obtain the ID of the ZooKeeper process:

      ps auxww | grep -w zookeeper | grep dsware | grep -v grep | awk '{print $2}'

      Information similar to the following is displayed:
      123445

    8. Run the following command to stop the ZooKeeper process:

      kill -9 ID of the ZooKeeper process

      The ID of the ZooKeeper process is obtained from 16.

      Example: kill -9 123445

      NOTE:
      The ZooKeeper process automatically restarts 15 seconds after you stop it, and the new configuration takes effect after the restart.

    9. If ZooKeeper processes are deployed on multiple FSA nodes, repeat 10 to 17 to modify the ZooKeeper configuration files on other FSA nodes.

    (Optional) Modify the MDC configuration file.

    Perform this step only on the FSA nodes with MDC processes deployed. You can obtain the process topology from 2.

    1. Use PuTTY to log in to the FSA node with the MDC process deployed.

      Ensure that the management IP address of the FSA node is used to establish the connection.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode in the FusionStorage Block Storage Service Administrator Guide.

    2. Run the following command and enter the password of user root to switch to user root:

      su - root

    3. Run the following command to open the MDC configuration file mdc_conf.cfg using the vi editor:

      vi /opt/dsware/mdc/conf/mdc_conf.cfg

    4. Press i to enter editing mode.
    5. Edit the mdc_conf.cfg file.

      Change the value of the g_multy_pool_feature_pool_num= field to 2.

      The file content after modification is as follows:
      g_multy_pool_feature_pool_num=2

    6. Press Esc and enter :wq to save the configuration and exit the vi editor.
    7. If MDC processes are deployed on multiple FSA nodes, repeat 19 to 24 to modify the MDC configuration files on other FSA nodes.

    (Optional) Modify the VBS configuration file.

    Perform this step only on the FSA nodes with VBS processes deployed. You can obtain the process topology from 2.

    1. Use PuTTY to log in to the FSA node with the VBS process deployed.

      Ensure that the management IP address of the FSA node is used to establish the connection.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode in the FusionStorage Block Storage Service Administrator Guide.

    2. Run the following command and enter the password of user root to switch to user root:

      su - root

    3. Run the following command to open the VBS configuration file vbs_Floating IP address of FSM nodes_conf.cfg using the vi editor:

      vi /opt/dsware/vbs/conf/vbs_Floating IP address of FSM nodes_conf.cfg

      Example: vi /opt/dsware/vbs/conf/vbs_192.168.2.1_conf.cfg

      NOTE:
      The VBS configuration file is named in the vbs_Floating IP address of FSM node_conf.cfg format. For example, if the floating IP address of FSM nodes is 192.168.2.1, the VBS configuration file is named vbs_192.168.2.1_conf.cfg.

    4. Press i to enter editing mode.
    5. Edit the vbs_Floating IP address of FSM nodes_conf.cfg file.

      Change the value of the g_multy_pool_feature_pool_num= field to 2.

      The file content after modification is as follows:
      g_multy_pool_feature_pool_num=2

    6. Press Esc and enter :wq to save the configuration and exit the vi editor.

    7. Run the following command to obtain the ID of the VBS process:

      ps -efww | grep Floating IP address of FSM nodes | grep dsware_vbs | grep -v grep | awk '{print $2}'

      Information similar to the following is displayed:
      20975

    8. Run the following command to stop the VBS process:

      kill -9 ID of the VBS process

      The ID of the VBS process is obtained from 16.

      Example: kill -9 20975

      NOTE:
      The VBS process automatically restarts 15 seconds after you stop it, and the new configuration takes effect after the restart.

    9. If VBS processes are deployed on multiple FSA nodes, repeat 26 to 33 to modify the VBS configuration files on other FSA nodes.

    (Optional) Modify the OSD configuration file.

    Perform this step only on the FSA nodes with OSD processes deployed. You can obtain the process topology from 2.

    1. Use PuTTY to log in to the FSA node with the OSD process deployed.

      Ensure that the management IP address of the FSA node is used to establish the connection.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode in the FusionStorage Block Storage Service Administrator Guide.

    2. Run the following command and enter the password of user root to switch to user root:

      su - root

    3. Run the following command to open the OSD configuration file osd_Storage pool ID_conf.cfg using the vi editor:

      vi /opt/dsware/osd/conf/osd_Storage pool ID_conf.cfg

      Example: vi /opt/dsware/osd/conf/osd_0_conf.cfg

      NOTE:
      On FusionStorage Block Self-Maintenance Platform, choose Resource Pool > Storage Pools to query the storage pool ID.

    4. Press i to enter editing mode.
    5. Edit the osd_Storage pool ID_conf.cfg file.

      Change the value of the g_multy_pool_feature_pool_num= field to 2.

      The file content after modification is as follows:
      g_multy_pool_feature_pool_num=2

    6. Press Esc and enter :wq to save the configuration and exit the vi editor.

    7. If OSD processes are deployed on multiple FSA nodes, repeat 35 to 40 to modify the OSD configuration files on other FSA nodes.
Translation
Download
Updated: 2019-09-09

Document ID: EDOC1100027999

Views: 5864

Downloads: 17

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next