On this page

Configuration Page
Parameters

Show all

Help Center/ MapReduce Service/ Component Operation Guide (LTS) (Ankara Region)/ Using MemArtsCC/ Setting Typical MemArtsCC Parameters

Setting Typical MemArtsCC Parameters

Updated on 2024-11-29 GMT+08:00

View PDF

Configuration Page

Go to the MemArtsCC configuration page by referring to Modifying Cluster Service Configuration Parameters.

Parameters

**Table 1** MemArtsCC configuration parameters
Parameter	Description	Default Value
access_token_enable	Whether to enable Access token authentication If this function is enabled, token verification is required when the SDK reads the cache through the worker. When the SDK sends a read request to the worker for the first time, the worker performs Kerberos authentication, generates a key, saves the key to the local host and ZooKeeper, uses the key to generate a token, and returns the token to the SDK. When the SDK sends other read requests to the worker, the token is transferred to the worker for verification with the key, the cache can be read only after the verification is successful.	The value is true for a security cluster and false for a normal cluster.
cache_cap_max_availabe_rate	Ratio of the maximum available capacity on each disk for MemArtsCC The value ranges from 0.01 to 1.0, and the step is 0.01. This parameter determines the maximum disk capacity (percentage) can be used by MemArtsCC. The default value is 30%. For example, if the disk capacity is 3 TB, the maximum cache space that can be used by the MemArtsCC is 900 GB. If the cache exceeds 900 GB, the MemArtsCC dynamically clears the cache.	0.3
cache_reserved_space	Space to be dynamically reserved for each disk cache_reserved_space determines the reserved disk space. The default value is 512 MB. Set this parameter to a value greater than 10% of the disk capacity. For example, for a 3 TB disk, set cache_reserved_space to 300 GB and cache_cap_max_available_rate to 30%. If the disk space is less than 300 GB, MemArtsCC dynamically clears the cache even if the cache does not reach the maximum limit (900 GB).	512MB
auto_isolate_broken_disk	Whether to automatically isolate faulty disks	true
broken_disk_list	List of faulty disks	-

Parent topic: Using MemArtsCC

Previous topic: Using MemArtsCC

Next topic: Configuring the Connection Between Hive and MemArtsCC

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback

Log In and Submit Submit Cancel