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


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


FusionInsight HD 6.5.0 Administrator Guide 02

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).
Static Service Resources

Static Service Resources


The resources allocated to each service in a cluster are static service resources. Such services include FTP Server, Flume, HBase, HDFS, Solr, Elasticsearch, Elk, and YARN. The total volume of computing resources allocated to each service is fixed, and they are static. A tenant can exclusively use or share a service to obtain the resources required for running this service.

Static Service Pool

Static service pools are used to specify service resource configurations.

Static service pools centrally manage resources applicable to each service.

  • They restrict the total volume of resources used for services and dynamically configure the total CPU, I/O, and memory resources applicable to nodes running FTP Server, Flume, HBase, Solr, Elasticsearch, Elk, and YARN.
  • The resources of services are isolated. The services in a cluster are isolated from each other, and the workload of one service has limited impact on other services.

Scheduling Mechanism

The time-based dynamic resource scheduling mechanism enables different volumes of static resources to be configured for services at different time, optimizing service running environments and improving the cluster efficiency.

In a complex cluster environment, multiple services share resources in the cluster, but the resource service period of each service may be different.

The following use a bank customer as an example:

  • The HBase query service is heavy in the daytime.
  • The query service is light, but the Hive analysis service is heavy at night.

If fixed resources are allocated to each service, the following problems may occur:

  • The query service cannot obtain sufficient resources while the resources for the analysis service are idle in the daytime.
  • The analysis service cannot obtain sufficient resources while the resources for the query service are idle at night.

As a result, the cluster resource utilization is low and the service capability is weak. Resolve the problem in the following ways:

  • Sufficient resources need to be configured for HBase in the daytime.
  • Sufficient resources need to be configured for Hive at night.

The time-based dynamic scheduling mechanism can efficiently utilize resources and run tasks.

Updated: 2019-05-17

Document ID: EDOC1100074522

Views: 5858

Downloads: 12

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