Documentation
Rate This Document
Findability
Accuracy
Completeness
Readability
SubmitClose

Failed to Match Recommended Parameters During Recommendation Tasks

Problem Description

Table 1 Basic information

Item

Information

Source of the Problem

Online maintenance

Product

Kunpeng BoostKit

Sub-item

Big data

Service Scenario

Debugging and running

Component

Other

Output Time

2023-01-29

Author

Ma Xiaoqi

Team

Kunpeng BoostKit

Review Result

Review passed

Review Date

2024-01-30

Release Date

2024-03-30

Keywords

Optimal parameter recommendation failure during task execution

Document

OmniAdvisor Feature Guide

Symptom

During SQL recommendation tasks, if the query statement of the submitted task is inconsistent with the query statement after parsing, or if the JAR package of the submitted task is inconsistent with the JAR package after parsing, the hash value of the task ID is incorrect. As a result, the optimal parameters fail to be recommended during task execution. The following message is displayed:

ERROR - 'NoneType' object has no attribute 'parameters'

Key Process and Cause Analysis

None

Conclusion and Solution

Modify identification_type in the $OMNIADVISOR_HOME/BoostKit-omniadvisor_1.1.0/config/common_config.cfg file.

  1. Open the configuration file.
    1
    		 
    vi $OMNIADVISOR_HOME/BoostKit-omniadvisor_1.1.0/config/common_config.cfg
  2. Change identification_type to application_name.
    1
2
3
    		 
    # You need to specify the unique ID of the task. You can choose to use the hash value of the task name (application_name) or the hash value of the task (corresponding to the hash value of the query statement or JAR package) to search for the optimal parameters of the task in the database.
# options: [application_name, job_hash]
identification_type = application_name
  3. Press Esc, type :wq!, and press Enter to save the file and exit.
  4. Perform log parsing for the task again to re-start parameter optimization.
Parent topic: Troubleshooting