Help Center > > User Guide> Managing Active Clusters> Managing Jobs> Copying Jobs

Copying Jobs

Updated at:Nov 06, 2019 GMT+08:00

This section describes how to copy new MRS jobs. The function of copying jobs is available only in clusters of MRS 2.0.1 or versions earlier than MRS 1.8.7.

Background

Currently, all types of jobs except for Spark SQL and Distcp jobs can be copied.

Procedure

  1. Log in to the MRS management console.
  2. Choose Clusters > Active Clusters, select a running cluster, and click its name to switch to the cluster details page.
  3. Click Jobs.
  4. In the Operation column corresponding to the to-be-copied job, choose More > Copy.

    The Copy Job dialog box is displayed.

  5. Set job parameters, and click OK.

    Table 1 describes job configuration information.

    After being successfully submitted, a job changes to the Running state by default. You do not need to manually execute the job.

    Table 1 Job configuration information

    Parameter

    Description

    Name

    Job name. It contains 1 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

    NOTE:

    You are advised to set different names for different jobs.

    Program Path

    Path of the program package to be executed. The following requirements must be met:

    • Contains a maximum of 1,023 characters, excluding special characters such as ;|&><'$. The parameter value cannot be empty or full of spaces.
    • The path of the program to be executed can be stored in HDFS or OBS. The path varies depending on the file system.
      • OBS: The path must start with s3a://. Example: s3a://wordcount/program/xxx.jar
      • HDFS: The path must start with /user.
    • For SparkScript, the path must end with .sql. For MapReduce and Spark, the path must end with .jar. The .sql and .jar are case-insensitive.

    Parameters

    Key parameter for program execution. The parameter is specified by the function of the user's program. MRS is only responsible for loading the parameter. Multiple parameters are separated by space.

    Configuration method: Package name.Class name

    The parameter contains a maximum of 2,047 characters, excluding special characters such as ;|&><'$, and can be left blank.

    NOTE:

    When entering a parameter containing sensitive information (for example, login password), you can add an at sign (@) before the parameter name to encrypt the parameter value. This prevents the sensitive information from being persisted in plaintext. When you view job information on the MRS management console, the sensitive information is displayed as *.

    Example: username=admin @password=admin_123

    Import from

    Path for inputting data

    Data can be stored in HDFS or OBS. The path varies depending on the file system.
    • OBS: The path must start with s3a://.
    • HDFS: The path must start with /user.

    The parameter contains a maximum of 1,023 characters, excluding special characters such as ;|&>,<'$, and can be left blank.

    Export to

    Path for outputting data

    NOTE:
    • When setting this parameter, select OBS or HDFS. Select a file directory or manually enter a file directory, and click OK.
    • If you add the hadoop-mapreduce-examples-x.x.x.jar sample program or a program similar to hadoop-mapreduce-examples-x.x.x.jar, enter a directory that does not exist.
    Data can be stored in HDFS or OBS. The path varies depending on the file system.
    • OBS: The path must start with s3a://.
    • HDFS: The path must start with /user.

    The parameter contains a maximum of 1,023 characters, excluding special characters such as ;|&>,<'$, and can be left blank.

    Log Path

    Path for storing job logs that record job running status.

    Data can be stored in HDFS or OBS. The path varies depending on the file system.
    • OBS: The path must start with s3a://.
    • HDFS: The path must start with /user.

    The parameter contains a maximum of 1,023 characters, excluding special characters such as ;|&>,<'$, and can be left blank.

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