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

OceanStor 9000 V300R006C00 Object Storage Service (Compatible with Amazon S3 APIs) Administrator Guide 07

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).
Changing the Node Service Type

Changing the Node Service Type

Nodes that provide the object storage service (compatible with Amazon S3 APIs) can be changed to provide file system services.

Prerequisites

Table 17-4 provides the prerequisites and estimated time for changing the node service type. You are advised to select Offline switchover from Service Switchover Mode, and do not perform capacity expansion when changing the node service type.
Table 17-4  Prerequisites and estimated time for changing the node service type

Service Switchover Mode

Prerequisite

Estimated Time

Offline switchover

Online services are interrupted until the switchover is complete.

About 30 minutes

Online switchover

Online services are not interrupted.
  • In a cluster, the service types of primary and secondary management nodes that provide the object storage service cannot be switched. Otherwise, the system reports a switchover failure.
  • The management nodes of object storage service (compatible with Amazon S3 APIs) cannot change their service type.
  • Service cannot be changed when the nodes are not equipped with NVDIMMs or CBUs, or the existing NVDIMMs or CBUs are faulty.
  • In addition, services cannot be changed when tasks are running in the background, such as data reconstruction and data balancing.
  • To switch node service types, see section Checking Client Connections in an Online Upgrade in Upgrade Guide to avoid service failures caused by switching faults.
  • Ensure that clients are connected using domain name, so that the clients can automatically switch to other available nodes when service types of a node are being switched.
  • When changing the node service type, ensure that the following prerequisites are met:
    • At least five nodes provide the object storage service. After the switchover, at least two nodes provide the object storage service.
    • If only nodes that provide the object storage service exist before the switchover, at least three nodes will be switched to provide the file system service.
    • If the LVS server is configured for the cluster, you need to refer to the LVS Installation Guide to modify the LVS configuration when switching the node service mode from Object Storage Service (compatible with Amazon S3 Interfaces) to file system service.

Depends on the number of nodes. It takes about 1 hour for each node.

  • The management nodes of object storage service (compatible with Amazon S3 APIs) cannot change their service type.
  • Service cannot be changed when the nodes are not equipped with NVDIMMs or CBUs, or the existing NVDIMMs or CBUs are faulty.
  • In addition, services cannot be changed when tasks are running in the background, such as data reconstruction and data balancing.
  • To switch node service types, see section Checking Client Connections in an Online Upgrade in Upgrade Guide to avoid service failures caused by switching faults.
  • Ensure that clients are connected using domain name, so that the clients can automatically switch to other available nodes when service types of a node are being switched.

Procedure

  1. Logging In to Toolkit. Click Service Switchover.

    It is dangerous to change the service type of a node, because services that are running on the node will be interrupted. Therefore, ensure that no service is running on the node before changing the node service type, and change the node service type under guidance of maintenance engineers.

  2. Click Freeze BackgroudTask.

    If you fail to freeze the background tasks, service change cannot continue.

  3. On the left of Service Switchover Method, select Object Storage Service (compatible with Amazon S3 APIs) to file system service.
  4. On the right of Service Switchover Mode, select Online switchover or Offline switchover.

    If you select Offline switchover, system will stop services of all nodes automatically before the change. Nodes you want to change services will be restarted during the change.

    If you select Online switchover, nodes you want to change services will be restarted in sequence during the change. Each node is restarted after the other one completes the restart and data reconstruction.

  5. Select Data redundancy ratio.
  6. In InfoEqualizer DNS, enter the IP address of the DNS server used to achieve the InfoEqualizer feature.

    NOTE:

    The IP address entered in InfoEqualizer DNS and that of the front-end service network must reside at the same network segment.

    Perform the following steps when all nodes in the cluster provide object storage service (compatible with Amazon S3 APIs) before the service change.

  7. Select the node you want to change services in Service Switchover Node List, and then click Start Switchover.
  8. In the dialog box that is displayed, click OK. Carefully read the content of the Warning dialog box that is displayed. Then select I have read and understood the consequences associated with performing this operation for confirmation. Click OK.
  9. After the change, click Unfreeze BackgroudTask.

Follow-up Procedure

After the node service type is switched:
  • If the service type of the cluster is changed to be the file service or the hybrid deployment of the file system service and object storage service and the current application scenario involves massive small files and requires high performance, you are advised to run the show protocol loginfo CLI command to check whether the function for deleting directory logs is enabled. If the function is enabled, you are advised to run the change protocol loginfo CLI command to disable it.
  • If the service type of the cluster is changed to be the file service or the hybrid deployment of the file service and object storage service and the current application scenario does not require high performance, you are advised to run the show protocol loginfo CLI command to check whether the function for deleting directory logs is enabled. If the function is disabled, you are advised to run the change protocol loginfo CLI command to enable it. If the default configurations of the system do not meet your requirements after the function is enabled, you are advised to manually configure the system. For details, see section Managing File and Folder Operation Logs in chapter Cluster Management of the OceanStor 9000 File System Administrator Guide.
Translation
Download
Updated: 2019-04-28

Document ID: EDOC1000122523

Views: 11770

Downloads: 84

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