Help Center > > User Guide> FusionInsight Manager Operation Guide (Applicable to 3.x)> Cluster> Cluster Management> Static Service Pool> Static Service Resources

Static Service Resources

Updated at: Mar 25, 2021 GMT+08:00

Overview

The resources allocated to each service in a cluster are static service resources. Such services include Flume, HBase, HDFS 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 Flume, HBase, HDFS 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.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel