Docs Home
flexibleengine 1.46.0 published on Monday, Apr 14, 2025 by flexibleenginecloud
flexibleengine.MrsClusterV2
Explore with Pulumi AI
flexibleengine 1.46.0 published on Monday, Apr 14, 2025 by flexibleenginecloud
Manages a MRS cluster resource within FlexibleEngine.
Example Usage
Create an analysis cluster
import * as pulumi from "@pulumi/pulumi";
import * as flexibleengine from "@pulumi/flexibleengine";
const config = new pulumi.Config();
const mrsAz = config.requireObject("mrsAz");
const clusterName = config.requireObject("clusterName");
const password = config.requireObject("password");
const keypair = config.requireObject("keypair");
const exampleVpc = new flexibleengine.VpcV1("exampleVpc", {cidr: "192.168.0.0/16"});
const exampleSubnet = new flexibleengine.VpcSubnetV1("exampleSubnet", {
cidr: "192.168.0.0/24",
gatewayIp: "192.168.0.1",
vpcId: exampleVpc.vpcV1Id,
});
const test = new flexibleengine.MrsClusterV2("test", {
availabilityZone: mrsAz,
version: "MRS 2.0.1",
type: "ANALYSIS",
componentLists: [
"Hadoop",
"Spark",
"Hive",
"Tez",
],
managerAdminPwd: password,
nodeKeyPair: keypair,
vpcId: exampleVpc.vpcV1Id,
subnetId: exampleSubnet.vpcSubnetV1Id,
masterNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 2,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
analysisCoreNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 3,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
tags: {
foo: "bar",
key: "value",
},
});
import pulumi
import pulumi_flexibleengine as flexibleengine
config = pulumi.Config()
mrs_az = config.require_object("mrsAz")
cluster_name = config.require_object("clusterName")
password = config.require_object("password")
keypair = config.require_object("keypair")
example_vpc = flexibleengine.VpcV1("exampleVpc", cidr="192.168.0.0/16")
example_subnet = flexibleengine.VpcSubnetV1("exampleSubnet",
cidr="192.168.0.0/24",
gateway_ip="192.168.0.1",
vpc_id=example_vpc.vpc_v1_id)
test = flexibleengine.MrsClusterV2("test",
availability_zone=mrs_az,
version="MRS 2.0.1",
type="ANALYSIS",
component_lists=[
"Hadoop",
"Spark",
"Hive",
"Tez",
],
manager_admin_pwd=password,
node_key_pair=keypair,
vpc_id=example_vpc.vpc_v1_id,
subnet_id=example_subnet.vpc_subnet_v1_id,
master_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 2,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
analysis_core_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 3,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
tags={
"foo": "bar",
"key": "value",
})
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/flexibleengine/flexibleengine"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi/config"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
cfg := config.New(ctx, "")
mrsAz := cfg.RequireObject("mrsAz")
clusterName := cfg.RequireObject("clusterName")
password := cfg.RequireObject("password")
keypair := cfg.RequireObject("keypair")
exampleVpc, err := flexibleengine.NewVpcV1(ctx, "exampleVpc", &flexibleengine.VpcV1Args{
Cidr: pulumi.String("192.168.0.0/16"),
})
if err != nil {
return err
}
exampleSubnet, err := flexibleengine.NewVpcSubnetV1(ctx, "exampleSubnet", &flexibleengine.VpcSubnetV1Args{
Cidr: pulumi.String("192.168.0.0/24"),
GatewayIp: pulumi.String("192.168.0.1"),
VpcId: exampleVpc.VpcV1Id,
})
if err != nil {
return err
}
_, err = flexibleengine.NewMrsClusterV2(ctx, "test", &flexibleengine.MrsClusterV2Args{
AvailabilityZone: pulumi.Any(mrsAz),
Version: pulumi.String("MRS 2.0.1"),
Type: pulumi.String("ANALYSIS"),
ComponentLists: pulumi.StringArray{
pulumi.String("Hadoop"),
pulumi.String("Spark"),
pulumi.String("Hive"),
pulumi.String("Tez"),
},
ManagerAdminPwd: pulumi.Any(password),
NodeKeyPair: pulumi.Any(keypair),
VpcId: exampleVpc.VpcV1Id,
SubnetId: exampleSubnet.VpcSubnetV1Id,
MasterNodes: &flexibleengine.MrsClusterV2MasterNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(2),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
AnalysisCoreNodes: &flexibleengine.MrsClusterV2AnalysisCoreNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(3),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
Tags: pulumi.StringMap{
"foo": pulumi.String("bar"),
"key": pulumi.String("value"),
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Flexibleengine = Pulumi.Flexibleengine;
return await Deployment.RunAsync(() =>
{
var config = new Config();
var mrsAz = config.RequireObject<dynamic>("mrsAz");
var clusterName = config.RequireObject<dynamic>("clusterName");
var password = config.RequireObject<dynamic>("password");
var keypair = config.RequireObject<dynamic>("keypair");
var exampleVpc = new Flexibleengine.VpcV1("exampleVpc", new()
{
Cidr = "192.168.0.0/16",
});
var exampleSubnet = new Flexibleengine.VpcSubnetV1("exampleSubnet", new()
{
Cidr = "192.168.0.0/24",
GatewayIp = "192.168.0.1",
VpcId = exampleVpc.VpcV1Id,
});
var test = new Flexibleengine.MrsClusterV2("test", new()
{
AvailabilityZone = mrsAz,
Version = "MRS 2.0.1",
Type = "ANALYSIS",
ComponentLists = new[]
{
"Hadoop",
"Spark",
"Hive",
"Tez",
},
ManagerAdminPwd = password,
NodeKeyPair = keypair,
VpcId = exampleVpc.VpcV1Id,
SubnetId = exampleSubnet.VpcSubnetV1Id,
MasterNodes = new Flexibleengine.Inputs.MrsClusterV2MasterNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 2,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
AnalysisCoreNodes = new Flexibleengine.Inputs.MrsClusterV2AnalysisCoreNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 3,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
Tags =
{
{ "foo", "bar" },
{ "key", "value" },
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.flexibleengine.VpcV1;
import com.pulumi.flexibleengine.VpcV1Args;
import com.pulumi.flexibleengine.VpcSubnetV1;
import com.pulumi.flexibleengine.VpcSubnetV1Args;
import com.pulumi.flexibleengine.MrsClusterV2;
import com.pulumi.flexibleengine.MrsClusterV2Args;
import com.pulumi.flexibleengine.inputs.MrsClusterV2MasterNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2AnalysisCoreNodesArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var config = ctx.config();
final var mrsAz = config.get("mrsAz");
final var clusterName = config.get("clusterName");
final var password = config.get("password");
final var keypair = config.get("keypair");
var exampleVpc = new VpcV1("exampleVpc", VpcV1Args.builder()
.cidr("192.168.0.0/16")
.build());
var exampleSubnet = new VpcSubnetV1("exampleSubnet", VpcSubnetV1Args.builder()
.cidr("192.168.0.0/24")
.gatewayIp("192.168.0.1")
.vpcId(exampleVpc.vpcV1Id())
.build());
var test = new MrsClusterV2("test", MrsClusterV2Args.builder()
.availabilityZone(mrsAz)
.version("MRS 2.0.1")
.type("ANALYSIS")
.componentLists(
"Hadoop",
"Spark",
"Hive",
"Tez")
.managerAdminPwd(password)
.nodeKeyPair(keypair)
.vpcId(exampleVpc.vpcV1Id())
.subnetId(exampleSubnet.vpcSubnetV1Id())
.masterNodes(MrsClusterV2MasterNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(2)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.analysisCoreNodes(MrsClusterV2AnalysisCoreNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(3)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.tags(Map.ofEntries(
Map.entry("foo", "bar"),
Map.entry("key", "value")
))
.build());
}
}
configuration:
mrsAz:
type: dynamic
clusterName:
type: dynamic
password:
type: dynamic
keypair:
type: dynamic
resources:
exampleVpc:
type: flexibleengine:VpcV1
properties:
cidr: 192.168.0.0/16
exampleSubnet:
type: flexibleengine:VpcSubnetV1
properties:
cidr: 192.168.0.0/24
gatewayIp: 192.168.0.1
vpcId: ${exampleVpc.vpcV1Id}
test:
type: flexibleengine:MrsClusterV2
properties:
availabilityZone: ${mrsAz}
version: MRS 2.0.1
type: ANALYSIS
componentLists:
- Hadoop
- Spark
- Hive
- Tez
managerAdminPwd: ${password}
nodeKeyPair: ${keypair}
vpcId: ${exampleVpc.vpcV1Id}
subnetId: ${exampleSubnet.vpcSubnetV1Id}
masterNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 2
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
analysisCoreNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 3
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
tags:
foo: bar
key: value
Create a stream cluster
import * as pulumi from "@pulumi/pulumi";
import * as flexibleengine from "@pulumi/flexibleengine";
const config = new pulumi.Config();
const mrsAz = config.requireObject("mrsAz");
const clusterName = config.requireObject("clusterName");
const password = config.requireObject("password");
const keypair = config.requireObject("keypair");
const exampleVpc = new flexibleengine.VpcV1("exampleVpc", {cidr: "192.168.0.0/16"});
const exampleSubnet = new flexibleengine.VpcSubnetV1("exampleSubnet", {
cidr: "192.168.0.0/24",
gatewayIp: "192.168.0.1",
vpcId: exampleVpc.vpcV1Id,
});
const test = new flexibleengine.MrsClusterV2("test", {
availabilityZone: mrsAz,
type: "STREAMING",
version: "MRS 3.1.0-LTS.1",
managerAdminPwd: password,
nodeKeyPair: keypair,
vpcId: exampleVpc.vpcV1Id,
subnetId: exampleSubnet.vpcSubnetV1Id,
componentLists: [
"Ranger",
"Kafka",
"ZooKeeper",
],
masterNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 2,
rootVolumeType: "SAS",
rootVolumeSize: 480,
dataVolumeType: "SAS",
dataVolumeSize: 600,
dataVolumeCount: 1,
},
streamingCoreNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 3,
rootVolumeType: "SAS",
rootVolumeSize: 480,
dataVolumeType: "SAS",
dataVolumeSize: 600,
dataVolumeCount: 1,
},
tags: {
foo: "bar",
key: "value",
},
});
import pulumi
import pulumi_flexibleengine as flexibleengine
config = pulumi.Config()
mrs_az = config.require_object("mrsAz")
cluster_name = config.require_object("clusterName")
password = config.require_object("password")
keypair = config.require_object("keypair")
example_vpc = flexibleengine.VpcV1("exampleVpc", cidr="192.168.0.0/16")
example_subnet = flexibleengine.VpcSubnetV1("exampleSubnet",
cidr="192.168.0.0/24",
gateway_ip="192.168.0.1",
vpc_id=example_vpc.vpc_v1_id)
test = flexibleengine.MrsClusterV2("test",
availability_zone=mrs_az,
type="STREAMING",
version="MRS 3.1.0-LTS.1",
manager_admin_pwd=password,
node_key_pair=keypair,
vpc_id=example_vpc.vpc_v1_id,
subnet_id=example_subnet.vpc_subnet_v1_id,
component_lists=[
"Ranger",
"Kafka",
"ZooKeeper",
],
master_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 2,
"root_volume_type": "SAS",
"root_volume_size": 480,
"data_volume_type": "SAS",
"data_volume_size": 600,
"data_volume_count": 1,
},
streaming_core_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 3,
"root_volume_type": "SAS",
"root_volume_size": 480,
"data_volume_type": "SAS",
"data_volume_size": 600,
"data_volume_count": 1,
},
tags={
"foo": "bar",
"key": "value",
})
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/flexibleengine/flexibleengine"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi/config"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
cfg := config.New(ctx, "")
mrsAz := cfg.RequireObject("mrsAz")
clusterName := cfg.RequireObject("clusterName")
password := cfg.RequireObject("password")
keypair := cfg.RequireObject("keypair")
exampleVpc, err := flexibleengine.NewVpcV1(ctx, "exampleVpc", &flexibleengine.VpcV1Args{
Cidr: pulumi.String("192.168.0.0/16"),
})
if err != nil {
return err
}
exampleSubnet, err := flexibleengine.NewVpcSubnetV1(ctx, "exampleSubnet", &flexibleengine.VpcSubnetV1Args{
Cidr: pulumi.String("192.168.0.0/24"),
GatewayIp: pulumi.String("192.168.0.1"),
VpcId: exampleVpc.VpcV1Id,
})
if err != nil {
return err
}
_, err = flexibleengine.NewMrsClusterV2(ctx, "test", &flexibleengine.MrsClusterV2Args{
AvailabilityZone: pulumi.Any(mrsAz),
Type: pulumi.String("STREAMING"),
Version: pulumi.String("MRS 3.1.0-LTS.1"),
ManagerAdminPwd: pulumi.Any(password),
NodeKeyPair: pulumi.Any(keypair),
VpcId: exampleVpc.VpcV1Id,
SubnetId: exampleSubnet.VpcSubnetV1Id,
ComponentLists: pulumi.StringArray{
pulumi.String("Ranger"),
pulumi.String("Kafka"),
pulumi.String("ZooKeeper"),
},
MasterNodes: &flexibleengine.MrsClusterV2MasterNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(2),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(480),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(600),
DataVolumeCount: pulumi.Float64(1),
},
StreamingCoreNodes: &flexibleengine.MrsClusterV2StreamingCoreNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(3),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(480),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(600),
DataVolumeCount: pulumi.Float64(1),
},
Tags: pulumi.StringMap{
"foo": pulumi.String("bar"),
"key": pulumi.String("value"),
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Flexibleengine = Pulumi.Flexibleengine;
return await Deployment.RunAsync(() =>
{
var config = new Config();
var mrsAz = config.RequireObject<dynamic>("mrsAz");
var clusterName = config.RequireObject<dynamic>("clusterName");
var password = config.RequireObject<dynamic>("password");
var keypair = config.RequireObject<dynamic>("keypair");
var exampleVpc = new Flexibleengine.VpcV1("exampleVpc", new()
{
Cidr = "192.168.0.0/16",
});
var exampleSubnet = new Flexibleengine.VpcSubnetV1("exampleSubnet", new()
{
Cidr = "192.168.0.0/24",
GatewayIp = "192.168.0.1",
VpcId = exampleVpc.VpcV1Id,
});
var test = new Flexibleengine.MrsClusterV2("test", new()
{
AvailabilityZone = mrsAz,
Type = "STREAMING",
Version = "MRS 3.1.0-LTS.1",
ManagerAdminPwd = password,
NodeKeyPair = keypair,
VpcId = exampleVpc.VpcV1Id,
SubnetId = exampleSubnet.VpcSubnetV1Id,
ComponentLists = new[]
{
"Ranger",
"Kafka",
"ZooKeeper",
},
MasterNodes = new Flexibleengine.Inputs.MrsClusterV2MasterNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 2,
RootVolumeType = "SAS",
RootVolumeSize = 480,
DataVolumeType = "SAS",
DataVolumeSize = 600,
DataVolumeCount = 1,
},
StreamingCoreNodes = new Flexibleengine.Inputs.MrsClusterV2StreamingCoreNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 3,
RootVolumeType = "SAS",
RootVolumeSize = 480,
DataVolumeType = "SAS",
DataVolumeSize = 600,
DataVolumeCount = 1,
},
Tags =
{
{ "foo", "bar" },
{ "key", "value" },
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.flexibleengine.VpcV1;
import com.pulumi.flexibleengine.VpcV1Args;
import com.pulumi.flexibleengine.VpcSubnetV1;
import com.pulumi.flexibleengine.VpcSubnetV1Args;
import com.pulumi.flexibleengine.MrsClusterV2;
import com.pulumi.flexibleengine.MrsClusterV2Args;
import com.pulumi.flexibleengine.inputs.MrsClusterV2MasterNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2StreamingCoreNodesArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var config = ctx.config();
final var mrsAz = config.get("mrsAz");
final var clusterName = config.get("clusterName");
final var password = config.get("password");
final var keypair = config.get("keypair");
var exampleVpc = new VpcV1("exampleVpc", VpcV1Args.builder()
.cidr("192.168.0.0/16")
.build());
var exampleSubnet = new VpcSubnetV1("exampleSubnet", VpcSubnetV1Args.builder()
.cidr("192.168.0.0/24")
.gatewayIp("192.168.0.1")
.vpcId(exampleVpc.vpcV1Id())
.build());
var test = new MrsClusterV2("test", MrsClusterV2Args.builder()
.availabilityZone(mrsAz)
.type("STREAMING")
.version("MRS 3.1.0-LTS.1")
.managerAdminPwd(password)
.nodeKeyPair(keypair)
.vpcId(exampleVpc.vpcV1Id())
.subnetId(exampleSubnet.vpcSubnetV1Id())
.componentLists(
"Ranger",
"Kafka",
"ZooKeeper")
.masterNodes(MrsClusterV2MasterNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(2)
.rootVolumeType("SAS")
.rootVolumeSize(480)
.dataVolumeType("SAS")
.dataVolumeSize(600)
.dataVolumeCount(1)
.build())
.streamingCoreNodes(MrsClusterV2StreamingCoreNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(3)
.rootVolumeType("SAS")
.rootVolumeSize(480)
.dataVolumeType("SAS")
.dataVolumeSize(600)
.dataVolumeCount(1)
.build())
.tags(Map.ofEntries(
Map.entry("foo", "bar"),
Map.entry("key", "value")
))
.build());
}
}
configuration:
mrsAz:
type: dynamic
clusterName:
type: dynamic
password:
type: dynamic
keypair:
type: dynamic
resources:
exampleVpc:
type: flexibleengine:VpcV1
properties:
cidr: 192.168.0.0/16
exampleSubnet:
type: flexibleengine:VpcSubnetV1
properties:
cidr: 192.168.0.0/24
gatewayIp: 192.168.0.1
vpcId: ${exampleVpc.vpcV1Id}
test:
type: flexibleengine:MrsClusterV2
properties:
availabilityZone: ${mrsAz}
type: STREAMING
version: MRS 3.1.0-LTS.1
managerAdminPwd: ${password}
nodeKeyPair: ${keypair}
vpcId: ${exampleVpc.vpcV1Id}
subnetId: ${exampleSubnet.vpcSubnetV1Id}
componentLists:
- Ranger
- Kafka
- ZooKeeper
masterNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 2
rootVolumeType: SAS
rootVolumeSize: 480
dataVolumeType: SAS
dataVolumeSize: 600
dataVolumeCount: 1
streamingCoreNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 3
rootVolumeType: SAS
rootVolumeSize: 480
dataVolumeType: SAS
dataVolumeSize: 600
dataVolumeCount: 1
tags:
foo: bar
key: value
Create a hybrid cluster
import * as pulumi from "@pulumi/pulumi";
import * as flexibleengine from "@pulumi/flexibleengine";
const config = new pulumi.Config();
const mrsAz = config.requireObject("mrsAz");
const clusterName = config.requireObject("clusterName");
const password = config.requireObject("password");
const keypair = config.requireObject("keypair");
const exampleVpc = new flexibleengine.VpcV1("exampleVpc", {cidr: "192.168.0.0/16"});
const exampleSubnet = new flexibleengine.VpcSubnetV1("exampleSubnet", {
cidr: "192.168.0.0/24",
gatewayIp: "192.168.0.1",
vpcId: exampleVpc.vpcV1Id,
});
const test = new flexibleengine.MrsClusterV2("test", {
availabilityZone: mrsAz,
version: "MRS 2.0.1",
type: "MIXED",
componentLists: [
"Hadoop",
"Spark",
"Hive",
"Tez",
"Storm",
],
managerAdminPwd: password,
nodeKeyPair: keypair,
vpcId: exampleVpc.vpcV1Id,
subnetId: exampleSubnet.vpcSubnetV1Id,
masterNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 2,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
analysisCoreNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 2,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
streamingCoreNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 2,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
analysisTaskNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 1,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
streamingTaskNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 1,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
tags: {
foo: "bar",
key: "value",
},
});
import pulumi
import pulumi_flexibleengine as flexibleengine
config = pulumi.Config()
mrs_az = config.require_object("mrsAz")
cluster_name = config.require_object("clusterName")
password = config.require_object("password")
keypair = config.require_object("keypair")
example_vpc = flexibleengine.VpcV1("exampleVpc", cidr="192.168.0.0/16")
example_subnet = flexibleengine.VpcSubnetV1("exampleSubnet",
cidr="192.168.0.0/24",
gateway_ip="192.168.0.1",
vpc_id=example_vpc.vpc_v1_id)
test = flexibleengine.MrsClusterV2("test",
availability_zone=mrs_az,
version="MRS 2.0.1",
type="MIXED",
component_lists=[
"Hadoop",
"Spark",
"Hive",
"Tez",
"Storm",
],
manager_admin_pwd=password,
node_key_pair=keypair,
vpc_id=example_vpc.vpc_v1_id,
subnet_id=example_subnet.vpc_subnet_v1_id,
master_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 2,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
analysis_core_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 2,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
streaming_core_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 2,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
analysis_task_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 1,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
streaming_task_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 1,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
tags={
"foo": "bar",
"key": "value",
})
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/flexibleengine/flexibleengine"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi/config"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
cfg := config.New(ctx, "")
mrsAz := cfg.RequireObject("mrsAz")
clusterName := cfg.RequireObject("clusterName")
password := cfg.RequireObject("password")
keypair := cfg.RequireObject("keypair")
exampleVpc, err := flexibleengine.NewVpcV1(ctx, "exampleVpc", &flexibleengine.VpcV1Args{
Cidr: pulumi.String("192.168.0.0/16"),
})
if err != nil {
return err
}
exampleSubnet, err := flexibleengine.NewVpcSubnetV1(ctx, "exampleSubnet", &flexibleengine.VpcSubnetV1Args{
Cidr: pulumi.String("192.168.0.0/24"),
GatewayIp: pulumi.String("192.168.0.1"),
VpcId: exampleVpc.VpcV1Id,
})
if err != nil {
return err
}
_, err = flexibleengine.NewMrsClusterV2(ctx, "test", &flexibleengine.MrsClusterV2Args{
AvailabilityZone: pulumi.Any(mrsAz),
Version: pulumi.String("MRS 2.0.1"),
Type: pulumi.String("MIXED"),
ComponentLists: pulumi.StringArray{
pulumi.String("Hadoop"),
pulumi.String("Spark"),
pulumi.String("Hive"),
pulumi.String("Tez"),
pulumi.String("Storm"),
},
ManagerAdminPwd: pulumi.Any(password),
NodeKeyPair: pulumi.Any(keypair),
VpcId: exampleVpc.VpcV1Id,
SubnetId: exampleSubnet.VpcSubnetV1Id,
MasterNodes: &flexibleengine.MrsClusterV2MasterNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(2),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
AnalysisCoreNodes: &flexibleengine.MrsClusterV2AnalysisCoreNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(2),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
StreamingCoreNodes: &flexibleengine.MrsClusterV2StreamingCoreNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(2),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
AnalysisTaskNodes: &flexibleengine.MrsClusterV2AnalysisTaskNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(1),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
StreamingTaskNodes: &flexibleengine.MrsClusterV2StreamingTaskNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(1),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
Tags: pulumi.StringMap{
"foo": pulumi.String("bar"),
"key": pulumi.String("value"),
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Flexibleengine = Pulumi.Flexibleengine;
return await Deployment.RunAsync(() =>
{
var config = new Config();
var mrsAz = config.RequireObject<dynamic>("mrsAz");
var clusterName = config.RequireObject<dynamic>("clusterName");
var password = config.RequireObject<dynamic>("password");
var keypair = config.RequireObject<dynamic>("keypair");
var exampleVpc = new Flexibleengine.VpcV1("exampleVpc", new()
{
Cidr = "192.168.0.0/16",
});
var exampleSubnet = new Flexibleengine.VpcSubnetV1("exampleSubnet", new()
{
Cidr = "192.168.0.0/24",
GatewayIp = "192.168.0.1",
VpcId = exampleVpc.VpcV1Id,
});
var test = new Flexibleengine.MrsClusterV2("test", new()
{
AvailabilityZone = mrsAz,
Version = "MRS 2.0.1",
Type = "MIXED",
ComponentLists = new[]
{
"Hadoop",
"Spark",
"Hive",
"Tez",
"Storm",
},
ManagerAdminPwd = password,
NodeKeyPair = keypair,
VpcId = exampleVpc.VpcV1Id,
SubnetId = exampleSubnet.VpcSubnetV1Id,
MasterNodes = new Flexibleengine.Inputs.MrsClusterV2MasterNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 2,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
AnalysisCoreNodes = new Flexibleengine.Inputs.MrsClusterV2AnalysisCoreNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 2,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
StreamingCoreNodes = new Flexibleengine.Inputs.MrsClusterV2StreamingCoreNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 2,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
AnalysisTaskNodes = new Flexibleengine.Inputs.MrsClusterV2AnalysisTaskNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 1,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
StreamingTaskNodes = new Flexibleengine.Inputs.MrsClusterV2StreamingTaskNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 1,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
Tags =
{
{ "foo", "bar" },
{ "key", "value" },
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.flexibleengine.VpcV1;
import com.pulumi.flexibleengine.VpcV1Args;
import com.pulumi.flexibleengine.VpcSubnetV1;
import com.pulumi.flexibleengine.VpcSubnetV1Args;
import com.pulumi.flexibleengine.MrsClusterV2;
import com.pulumi.flexibleengine.MrsClusterV2Args;
import com.pulumi.flexibleengine.inputs.MrsClusterV2MasterNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2AnalysisCoreNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2StreamingCoreNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2AnalysisTaskNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2StreamingTaskNodesArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var config = ctx.config();
final var mrsAz = config.get("mrsAz");
final var clusterName = config.get("clusterName");
final var password = config.get("password");
final var keypair = config.get("keypair");
var exampleVpc = new VpcV1("exampleVpc", VpcV1Args.builder()
.cidr("192.168.0.0/16")
.build());
var exampleSubnet = new VpcSubnetV1("exampleSubnet", VpcSubnetV1Args.builder()
.cidr("192.168.0.0/24")
.gatewayIp("192.168.0.1")
.vpcId(exampleVpc.vpcV1Id())
.build());
var test = new MrsClusterV2("test", MrsClusterV2Args.builder()
.availabilityZone(mrsAz)
.version("MRS 2.0.1")
.type("MIXED")
.componentLists(
"Hadoop",
"Spark",
"Hive",
"Tez",
"Storm")
.managerAdminPwd(password)
.nodeKeyPair(keypair)
.vpcId(exampleVpc.vpcV1Id())
.subnetId(exampleSubnet.vpcSubnetV1Id())
.masterNodes(MrsClusterV2MasterNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(2)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.analysisCoreNodes(MrsClusterV2AnalysisCoreNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(2)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.streamingCoreNodes(MrsClusterV2StreamingCoreNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(2)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.analysisTaskNodes(MrsClusterV2AnalysisTaskNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(1)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.streamingTaskNodes(MrsClusterV2StreamingTaskNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(1)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.tags(Map.ofEntries(
Map.entry("foo", "bar"),
Map.entry("key", "value")
))
.build());
}
}
configuration:
mrsAz:
type: dynamic
clusterName:
type: dynamic
password:
type: dynamic
keypair:
type: dynamic
resources:
exampleVpc:
type: flexibleengine:VpcV1
properties:
cidr: 192.168.0.0/16
exampleSubnet:
type: flexibleengine:VpcSubnetV1
properties:
cidr: 192.168.0.0/24
gatewayIp: 192.168.0.1
vpcId: ${exampleVpc.vpcV1Id}
test:
type: flexibleengine:MrsClusterV2
properties:
availabilityZone: ${mrsAz}
version: MRS 2.0.1
type: MIXED
componentLists:
- Hadoop
- Spark
- Hive
- Tez
- Storm
managerAdminPwd: ${password}
nodeKeyPair: ${keypair}
vpcId: ${exampleVpc.vpcV1Id}
subnetId: ${exampleSubnet.vpcSubnetV1Id}
masterNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 2
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
analysisCoreNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 2
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
streamingCoreNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 2
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
analysisTaskNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 1
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
streamingTaskNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 1
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
tags:
foo: bar
key: value
Create a custom cluster
import * as pulumi from "@pulumi/pulumi";
import * as flexibleengine from "@pulumi/flexibleengine";
const config = new pulumi.Config();
const mrsAz = config.requireObject("mrsAz");
const clusterName = config.requireObject("clusterName");
const password = config.requireObject("password");
const keypair = config.requireObject("keypair");
const exampleVpc = new flexibleengine.VpcV1("exampleVpc", {cidr: "192.168.0.0/16"});
const exampleSubnet = new flexibleengine.VpcSubnetV1("exampleSubnet", {
cidr: "192.168.0.0/24",
gatewayIp: "192.168.0.1",
vpcId: exampleVpc.vpcV1Id,
});
const test = new flexibleengine.MrsClusterV2("test", {
availabilityZone: mrsAz,
version: "MRS 3.1.0-LTS.1",
type: "CUSTOM",
safeMode: true,
managerAdminPwd: password,
nodeKeyPair: keypair,
vpcId: exampleVpc.vpcV1Id,
subnetId: exampleSubnet.vpcSubnetV1Id,
templateId: "mgmt_control_combined_v4",
componentLists: [
"DBService",
"Hadoop",
"ZooKeeper",
"Ranger",
],
masterNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 3,
rootVolumeType: "SAS",
rootVolumeSize: 480,
dataVolumeType: "SAS",
dataVolumeSize: 600,
dataVolumeCount: 1,
assignedRoles: [
"OMSServer:1,2",
"SlapdServer:1,2",
"KerberosServer:1,2",
"KerberosAdmin:1,2",
"quorumpeer:1,2,3",
"NameNode:2,3",
"Zkfc:2,3",
"JournalNode:1,2,3",
"ResourceManager:2,3",
"JobHistoryServer:3",
"DBServer:1,3",
"HttpFS:1,3",
"TimelineServer:3",
"RangerAdmin:1,2",
"UserSync:2",
"TagSync:2",
"KerberosClient",
"SlapdClient",
"meta",
],
},
customNodes: [{
groupName: "node_group_1",
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 4,
rootVolumeType: "SAS",
rootVolumeSize: 480,
dataVolumeType: "SAS",
dataVolumeSize: 600,
dataVolumeCount: 1,
assignedRoles: [
"DataNode",
"NodeManager",
"KerberosClient",
"SlapdClient",
"meta",
],
}],
});
import pulumi
import pulumi_flexibleengine as flexibleengine
config = pulumi.Config()
mrs_az = config.require_object("mrsAz")
cluster_name = config.require_object("clusterName")
password = config.require_object("password")
keypair = config.require_object("keypair")
example_vpc = flexibleengine.VpcV1("exampleVpc", cidr="192.168.0.0/16")
example_subnet = flexibleengine.VpcSubnetV1("exampleSubnet",
cidr="192.168.0.0/24",
gateway_ip="192.168.0.1",
vpc_id=example_vpc.vpc_v1_id)
test = flexibleengine.MrsClusterV2("test",
availability_zone=mrs_az,
version="MRS 3.1.0-LTS.1",
type="CUSTOM",
safe_mode=True,
manager_admin_pwd=password,
node_key_pair=keypair,
vpc_id=example_vpc.vpc_v1_id,
subnet_id=example_subnet.vpc_subnet_v1_id,
template_id="mgmt_control_combined_v4",
component_lists=[
"DBService",
"Hadoop",
"ZooKeeper",
"Ranger",
],
master_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 3,
"root_volume_type": "SAS",
"root_volume_size": 480,
"data_volume_type": "SAS",
"data_volume_size": 600,
"data_volume_count": 1,
"assigned_roles": [
"OMSServer:1,2",
"SlapdServer:1,2",
"KerberosServer:1,2",
"KerberosAdmin:1,2",
"quorumpeer:1,2,3",
"NameNode:2,3",
"Zkfc:2,3",
"JournalNode:1,2,3",
"ResourceManager:2,3",
"JobHistoryServer:3",
"DBServer:1,3",
"HttpFS:1,3",
"TimelineServer:3",
"RangerAdmin:1,2",
"UserSync:2",
"TagSync:2",
"KerberosClient",
"SlapdClient",
"meta",
],
},
custom_nodes=[{
"group_name": "node_group_1",
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 4,
"root_volume_type": "SAS",
"root_volume_size": 480,
"data_volume_type": "SAS",
"data_volume_size": 600,
"data_volume_count": 1,
"assigned_roles": [
"DataNode",
"NodeManager",
"KerberosClient",
"SlapdClient",
"meta",
],
}])
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/flexibleengine/flexibleengine"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi/config"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
cfg := config.New(ctx, "")
mrsAz := cfg.RequireObject("mrsAz")
clusterName := cfg.RequireObject("clusterName")
password := cfg.RequireObject("password")
keypair := cfg.RequireObject("keypair")
exampleVpc, err := flexibleengine.NewVpcV1(ctx, "exampleVpc", &flexibleengine.VpcV1Args{
Cidr: pulumi.String("192.168.0.0/16"),
})
if err != nil {
return err
}
exampleSubnet, err := flexibleengine.NewVpcSubnetV1(ctx, "exampleSubnet", &flexibleengine.VpcSubnetV1Args{
Cidr: pulumi.String("192.168.0.0/24"),
GatewayIp: pulumi.String("192.168.0.1"),
VpcId: exampleVpc.VpcV1Id,
})
if err != nil {
return err
}
_, err = flexibleengine.NewMrsClusterV2(ctx, "test", &flexibleengine.MrsClusterV2Args{
AvailabilityZone: pulumi.Any(mrsAz),
Version: pulumi.String("MRS 3.1.0-LTS.1"),
Type: pulumi.String("CUSTOM"),
SafeMode: pulumi.Bool(true),
ManagerAdminPwd: pulumi.Any(password),
NodeKeyPair: pulumi.Any(keypair),
VpcId: exampleVpc.VpcV1Id,
SubnetId: exampleSubnet.VpcSubnetV1Id,
TemplateId: pulumi.String("mgmt_control_combined_v4"),
ComponentLists: pulumi.StringArray{
pulumi.String("DBService"),
pulumi.String("Hadoop"),
pulumi.String("ZooKeeper"),
pulumi.String("Ranger"),
},
MasterNodes: &flexibleengine.MrsClusterV2MasterNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(3),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(480),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(600),
DataVolumeCount: pulumi.Float64(1),
AssignedRoles: pulumi.StringArray{
pulumi.String("OMSServer:1,2"),
pulumi.String("SlapdServer:1,2"),
pulumi.String("KerberosServer:1,2"),
pulumi.String("KerberosAdmin:1,2"),
pulumi.String("quorumpeer:1,2,3"),
pulumi.String("NameNode:2,3"),
pulumi.String("Zkfc:2,3"),
pulumi.String("JournalNode:1,2,3"),
pulumi.String("ResourceManager:2,3"),
pulumi.String("JobHistoryServer:3"),
pulumi.String("DBServer:1,3"),
pulumi.String("HttpFS:1,3"),
pulumi.String("TimelineServer:3"),
pulumi.String("RangerAdmin:1,2"),
pulumi.String("UserSync:2"),
pulumi.String("TagSync:2"),
pulumi.String("KerberosClient"),
pulumi.String("SlapdClient"),
pulumi.String("meta"),
},
},
CustomNodes: flexibleengine.MrsClusterV2CustomNodeArray{
&flexibleengine.MrsClusterV2CustomNodeArgs{
GroupName: pulumi.String("node_group_1"),
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(4),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(480),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(600),
DataVolumeCount: pulumi.Float64(1),
AssignedRoles: pulumi.StringArray{
pulumi.String("DataNode"),
pulumi.String("NodeManager"),
pulumi.String("KerberosClient"),
pulumi.String("SlapdClient"),
pulumi.String("meta"),
},
},
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Flexibleengine = Pulumi.Flexibleengine;
return await Deployment.RunAsync(() =>
{
var config = new Config();
var mrsAz = config.RequireObject<dynamic>("mrsAz");
var clusterName = config.RequireObject<dynamic>("clusterName");
var password = config.RequireObject<dynamic>("password");
var keypair = config.RequireObject<dynamic>("keypair");
var exampleVpc = new Flexibleengine.VpcV1("exampleVpc", new()
{
Cidr = "192.168.0.0/16",
});
var exampleSubnet = new Flexibleengine.VpcSubnetV1("exampleSubnet", new()
{
Cidr = "192.168.0.0/24",
GatewayIp = "192.168.0.1",
VpcId = exampleVpc.VpcV1Id,
});
var test = new Flexibleengine.MrsClusterV2("test", new()
{
AvailabilityZone = mrsAz,
Version = "MRS 3.1.0-LTS.1",
Type = "CUSTOM",
SafeMode = true,
ManagerAdminPwd = password,
NodeKeyPair = keypair,
VpcId = exampleVpc.VpcV1Id,
SubnetId = exampleSubnet.VpcSubnetV1Id,
TemplateId = "mgmt_control_combined_v4",
ComponentLists = new[]
{
"DBService",
"Hadoop",
"ZooKeeper",
"Ranger",
},
MasterNodes = new Flexibleengine.Inputs.MrsClusterV2MasterNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 3,
RootVolumeType = "SAS",
RootVolumeSize = 480,
DataVolumeType = "SAS",
DataVolumeSize = 600,
DataVolumeCount = 1,
AssignedRoles = new[]
{
"OMSServer:1,2",
"SlapdServer:1,2",
"KerberosServer:1,2",
"KerberosAdmin:1,2",
"quorumpeer:1,2,3",
"NameNode:2,3",
"Zkfc:2,3",
"JournalNode:1,2,3",
"ResourceManager:2,3",
"JobHistoryServer:3",
"DBServer:1,3",
"HttpFS:1,3",
"TimelineServer:3",
"RangerAdmin:1,2",
"UserSync:2",
"TagSync:2",
"KerberosClient",
"SlapdClient",
"meta",
},
},
CustomNodes = new[]
{
new Flexibleengine.Inputs.MrsClusterV2CustomNodeArgs
{
GroupName = "node_group_1",
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 4,
RootVolumeType = "SAS",
RootVolumeSize = 480,
DataVolumeType = "SAS",
DataVolumeSize = 600,
DataVolumeCount = 1,
AssignedRoles = new[]
{
"DataNode",
"NodeManager",
"KerberosClient",
"SlapdClient",
"meta",
},
},
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.flexibleengine.VpcV1;
import com.pulumi.flexibleengine.VpcV1Args;
import com.pulumi.flexibleengine.VpcSubnetV1;
import com.pulumi.flexibleengine.VpcSubnetV1Args;
import com.pulumi.flexibleengine.MrsClusterV2;
import com.pulumi.flexibleengine.MrsClusterV2Args;
import com.pulumi.flexibleengine.inputs.MrsClusterV2MasterNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2CustomNodeArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var config = ctx.config();
final var mrsAz = config.get("mrsAz");
final var clusterName = config.get("clusterName");
final var password = config.get("password");
final var keypair = config.get("keypair");
var exampleVpc = new VpcV1("exampleVpc", VpcV1Args.builder()
.cidr("192.168.0.0/16")
.build());
var exampleSubnet = new VpcSubnetV1("exampleSubnet", VpcSubnetV1Args.builder()
.cidr("192.168.0.0/24")
.gatewayIp("192.168.0.1")
.vpcId(exampleVpc.vpcV1Id())
.build());
var test = new MrsClusterV2("test", MrsClusterV2Args.builder()
.availabilityZone(mrsAz)
.version("MRS 3.1.0-LTS.1")
.type("CUSTOM")
.safeMode(true)
.managerAdminPwd(password)
.nodeKeyPair(keypair)
.vpcId(exampleVpc.vpcV1Id())
.subnetId(exampleSubnet.vpcSubnetV1Id())
.templateId("mgmt_control_combined_v4")
.componentLists(
"DBService",
"Hadoop",
"ZooKeeper",
"Ranger")
.masterNodes(MrsClusterV2MasterNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(3)
.rootVolumeType("SAS")
.rootVolumeSize(480)
.dataVolumeType("SAS")
.dataVolumeSize(600)
.dataVolumeCount(1)
.assignedRoles(
"OMSServer:1,2",
"SlapdServer:1,2",
"KerberosServer:1,2",
"KerberosAdmin:1,2",
"quorumpeer:1,2,3",
"NameNode:2,3",
"Zkfc:2,3",
"JournalNode:1,2,3",
"ResourceManager:2,3",
"JobHistoryServer:3",
"DBServer:1,3",
"HttpFS:1,3",
"TimelineServer:3",
"RangerAdmin:1,2",
"UserSync:2",
"TagSync:2",
"KerberosClient",
"SlapdClient",
"meta")
.build())
.customNodes(MrsClusterV2CustomNodeArgs.builder()
.groupName("node_group_1")
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(4)
.rootVolumeType("SAS")
.rootVolumeSize(480)
.dataVolumeType("SAS")
.dataVolumeSize(600)
.dataVolumeCount(1)
.assignedRoles(
"DataNode",
"NodeManager",
"KerberosClient",
"SlapdClient",
"meta")
.build())
.build());
}
}
configuration:
mrsAz:
type: dynamic
clusterName:
type: dynamic
password:
type: dynamic
keypair:
type: dynamic
resources:
exampleVpc:
type: flexibleengine:VpcV1
properties:
cidr: 192.168.0.0/16
exampleSubnet:
type: flexibleengine:VpcSubnetV1
properties:
cidr: 192.168.0.0/24
gatewayIp: 192.168.0.1
vpcId: ${exampleVpc.vpcV1Id}
test:
type: flexibleengine:MrsClusterV2
properties:
availabilityZone: ${mrsAz}
version: MRS 3.1.0-LTS.1
type: CUSTOM
safeMode: true
managerAdminPwd: ${password}
nodeKeyPair: ${keypair}
vpcId: ${exampleVpc.vpcV1Id}
subnetId: ${exampleSubnet.vpcSubnetV1Id}
templateId: mgmt_control_combined_v4
componentLists:
- DBService
- Hadoop
- ZooKeeper
- Ranger
masterNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 3
rootVolumeType: SAS
rootVolumeSize: 480
dataVolumeType: SAS
dataVolumeSize: 600
dataVolumeCount: 1
assignedRoles:
- OMSServer:1,2
- SlapdServer:1,2
- KerberosServer:1,2
- KerberosAdmin:1,2
- quorumpeer:1,2,3
- NameNode:2,3
- Zkfc:2,3
- JournalNode:1,2,3
- ResourceManager:2,3
- JobHistoryServer:3
- DBServer:1,3
- HttpFS:1,3
- TimelineServer:3
- RangerAdmin:1,2
- UserSync:2
- TagSync:2
- KerberosClient
- SlapdClient
- meta
customNodes:
- groupName: node_group_1
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 4
rootVolumeType: SAS
rootVolumeSize: 480
dataVolumeType: SAS
dataVolumeSize: 600
dataVolumeCount: 1
assignedRoles:
- DataNode
- NodeManager
- KerberosClient
- SlapdClient
- meta
Create an analysis cluster and bind public IP
import * as pulumi from "@pulumi/pulumi";
import * as flexibleengine from "@pulumi/flexibleengine";
const config = new pulumi.Config();
const mrsAz = config.requireObject("mrsAz");
const clusterName = config.requireObject("clusterName");
const password = config.requireObject("password");
const keypair = config.requireObject("keypair");
const publicIp = config.requireObject("publicIp");
const exampleVpc = new flexibleengine.VpcV1("exampleVpc", {cidr: "192.168.0.0/16"});
const exampleSubnet = new flexibleengine.VpcSubnetV1("exampleSubnet", {
cidr: "192.168.0.0/24",
gatewayIp: "192.168.0.1",
vpcId: exampleVpc.vpcV1Id,
});
const test = new flexibleengine.MrsClusterV2("test", {
availabilityZone: mrsAz,
version: "MRS 2.0.1",
type: "ANALYSIS",
componentLists: [
"Hadoop",
"Hive",
"Tez",
],
managerAdminPwd: password,
nodeKeyPair: keypair,
vpcId: exampleVpc.vpcV1Id,
subnetId: exampleSubnet.vpcSubnetV1Id,
publicIp: publicIp,
masterNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 2,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
analysisCoreNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 2,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
analysisTaskNodes: {
flavor: "c6.4xlarge.4.linux.mrs",
nodeNumber: 1,
rootVolumeType: "SAS",
rootVolumeSize: 300,
dataVolumeType: "SAS",
dataVolumeSize: 480,
dataVolumeCount: 1,
},
tags: {
foo: "bar",
key: "value",
},
});
import pulumi
import pulumi_flexibleengine as flexibleengine
config = pulumi.Config()
mrs_az = config.require_object("mrsAz")
cluster_name = config.require_object("clusterName")
password = config.require_object("password")
keypair = config.require_object("keypair")
public_ip = config.require_object("publicIp")
example_vpc = flexibleengine.VpcV1("exampleVpc", cidr="192.168.0.0/16")
example_subnet = flexibleengine.VpcSubnetV1("exampleSubnet",
cidr="192.168.0.0/24",
gateway_ip="192.168.0.1",
vpc_id=example_vpc.vpc_v1_id)
test = flexibleengine.MrsClusterV2("test",
availability_zone=mrs_az,
version="MRS 2.0.1",
type="ANALYSIS",
component_lists=[
"Hadoop",
"Hive",
"Tez",
],
manager_admin_pwd=password,
node_key_pair=keypair,
vpc_id=example_vpc.vpc_v1_id,
subnet_id=example_subnet.vpc_subnet_v1_id,
public_ip=public_ip,
master_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 2,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
analysis_core_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 2,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
analysis_task_nodes={
"flavor": "c6.4xlarge.4.linux.mrs",
"node_number": 1,
"root_volume_type": "SAS",
"root_volume_size": 300,
"data_volume_type": "SAS",
"data_volume_size": 480,
"data_volume_count": 1,
},
tags={
"foo": "bar",
"key": "value",
})
package main
import (
"github.com/pulumi/pulumi-terraform-provider/sdks/go/flexibleengine/flexibleengine"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi/config"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
cfg := config.New(ctx, "")
mrsAz := cfg.RequireObject("mrsAz")
clusterName := cfg.RequireObject("clusterName")
password := cfg.RequireObject("password")
keypair := cfg.RequireObject("keypair")
publicIp := cfg.RequireObject("publicIp")
exampleVpc, err := flexibleengine.NewVpcV1(ctx, "exampleVpc", &flexibleengine.VpcV1Args{
Cidr: pulumi.String("192.168.0.0/16"),
})
if err != nil {
return err
}
exampleSubnet, err := flexibleengine.NewVpcSubnetV1(ctx, "exampleSubnet", &flexibleengine.VpcSubnetV1Args{
Cidr: pulumi.String("192.168.0.0/24"),
GatewayIp: pulumi.String("192.168.0.1"),
VpcId: exampleVpc.VpcV1Id,
})
if err != nil {
return err
}
_, err = flexibleengine.NewMrsClusterV2(ctx, "test", &flexibleengine.MrsClusterV2Args{
AvailabilityZone: pulumi.Any(mrsAz),
Version: pulumi.String("MRS 2.0.1"),
Type: pulumi.String("ANALYSIS"),
ComponentLists: pulumi.StringArray{
pulumi.String("Hadoop"),
pulumi.String("Hive"),
pulumi.String("Tez"),
},
ManagerAdminPwd: pulumi.Any(password),
NodeKeyPair: pulumi.Any(keypair),
VpcId: exampleVpc.VpcV1Id,
SubnetId: exampleSubnet.VpcSubnetV1Id,
PublicIp: pulumi.Any(publicIp),
MasterNodes: &flexibleengine.MrsClusterV2MasterNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(2),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
AnalysisCoreNodes: &flexibleengine.MrsClusterV2AnalysisCoreNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(2),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
AnalysisTaskNodes: &flexibleengine.MrsClusterV2AnalysisTaskNodesArgs{
Flavor: pulumi.String("c6.4xlarge.4.linux.mrs"),
NodeNumber: pulumi.Float64(1),
RootVolumeType: pulumi.String("SAS"),
RootVolumeSize: pulumi.Float64(300),
DataVolumeType: pulumi.String("SAS"),
DataVolumeSize: pulumi.Float64(480),
DataVolumeCount: pulumi.Float64(1),
},
Tags: pulumi.StringMap{
"foo": pulumi.String("bar"),
"key": pulumi.String("value"),
},
})
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Flexibleengine = Pulumi.Flexibleengine;
return await Deployment.RunAsync(() =>
{
var config = new Config();
var mrsAz = config.RequireObject<dynamic>("mrsAz");
var clusterName = config.RequireObject<dynamic>("clusterName");
var password = config.RequireObject<dynamic>("password");
var keypair = config.RequireObject<dynamic>("keypair");
var publicIp = config.RequireObject<dynamic>("publicIp");
var exampleVpc = new Flexibleengine.VpcV1("exampleVpc", new()
{
Cidr = "192.168.0.0/16",
});
var exampleSubnet = new Flexibleengine.VpcSubnetV1("exampleSubnet", new()
{
Cidr = "192.168.0.0/24",
GatewayIp = "192.168.0.1",
VpcId = exampleVpc.VpcV1Id,
});
var test = new Flexibleengine.MrsClusterV2("test", new()
{
AvailabilityZone = mrsAz,
Version = "MRS 2.0.1",
Type = "ANALYSIS",
ComponentLists = new[]
{
"Hadoop",
"Hive",
"Tez",
},
ManagerAdminPwd = password,
NodeKeyPair = keypair,
VpcId = exampleVpc.VpcV1Id,
SubnetId = exampleSubnet.VpcSubnetV1Id,
PublicIp = publicIp,
MasterNodes = new Flexibleengine.Inputs.MrsClusterV2MasterNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 2,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
AnalysisCoreNodes = new Flexibleengine.Inputs.MrsClusterV2AnalysisCoreNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 2,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
AnalysisTaskNodes = new Flexibleengine.Inputs.MrsClusterV2AnalysisTaskNodesArgs
{
Flavor = "c6.4xlarge.4.linux.mrs",
NodeNumber = 1,
RootVolumeType = "SAS",
RootVolumeSize = 300,
DataVolumeType = "SAS",
DataVolumeSize = 480,
DataVolumeCount = 1,
},
Tags =
{
{ "foo", "bar" },
{ "key", "value" },
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.flexibleengine.VpcV1;
import com.pulumi.flexibleengine.VpcV1Args;
import com.pulumi.flexibleengine.VpcSubnetV1;
import com.pulumi.flexibleengine.VpcSubnetV1Args;
import com.pulumi.flexibleengine.MrsClusterV2;
import com.pulumi.flexibleengine.MrsClusterV2Args;
import com.pulumi.flexibleengine.inputs.MrsClusterV2MasterNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2AnalysisCoreNodesArgs;
import com.pulumi.flexibleengine.inputs.MrsClusterV2AnalysisTaskNodesArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var config = ctx.config();
final var mrsAz = config.get("mrsAz");
final var clusterName = config.get("clusterName");
final var password = config.get("password");
final var keypair = config.get("keypair");
final var publicIp = config.get("publicIp");
var exampleVpc = new VpcV1("exampleVpc", VpcV1Args.builder()
.cidr("192.168.0.0/16")
.build());
var exampleSubnet = new VpcSubnetV1("exampleSubnet", VpcSubnetV1Args.builder()
.cidr("192.168.0.0/24")
.gatewayIp("192.168.0.1")
.vpcId(exampleVpc.vpcV1Id())
.build());
var test = new MrsClusterV2("test", MrsClusterV2Args.builder()
.availabilityZone(mrsAz)
.version("MRS 2.0.1")
.type("ANALYSIS")
.componentLists(
"Hadoop",
"Hive",
"Tez")
.managerAdminPwd(password)
.nodeKeyPair(keypair)
.vpcId(exampleVpc.vpcV1Id())
.subnetId(exampleSubnet.vpcSubnetV1Id())
.publicIp(publicIp)
.masterNodes(MrsClusterV2MasterNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(2)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.analysisCoreNodes(MrsClusterV2AnalysisCoreNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(2)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.analysisTaskNodes(MrsClusterV2AnalysisTaskNodesArgs.builder()
.flavor("c6.4xlarge.4.linux.mrs")
.nodeNumber(1)
.rootVolumeType("SAS")
.rootVolumeSize(300)
.dataVolumeType("SAS")
.dataVolumeSize(480)
.dataVolumeCount(1)
.build())
.tags(Map.ofEntries(
Map.entry("foo", "bar"),
Map.entry("key", "value")
))
.build());
}
}
configuration:
mrsAz:
type: dynamic
clusterName:
type: dynamic
password:
type: dynamic
keypair:
type: dynamic
publicIp:
type: dynamic
resources:
exampleVpc:
type: flexibleengine:VpcV1
properties:
cidr: 192.168.0.0/16
exampleSubnet:
type: flexibleengine:VpcSubnetV1
properties:
cidr: 192.168.0.0/24
gatewayIp: 192.168.0.1
vpcId: ${exampleVpc.vpcV1Id}
test:
type: flexibleengine:MrsClusterV2
properties:
availabilityZone: ${mrsAz}
version: MRS 2.0.1
type: ANALYSIS
componentLists:
- Hadoop
- Hive
- Tez
managerAdminPwd: ${password}
nodeKeyPair: ${keypair}
vpcId: ${exampleVpc.vpcV1Id}
subnetId: ${exampleSubnet.vpcSubnetV1Id}
publicIp: ${publicIp}
masterNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 2
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
analysisCoreNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 2
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
analysisTaskNodes:
flavor: c6.4xlarge.4.linux.mrs
nodeNumber: 1
rootVolumeType: SAS
rootVolumeSize: 300
dataVolumeType: SAS
dataVolumeSize: 480
dataVolumeCount: 1
tags:
foo: bar
key: value
Create MrsClusterV2 Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new MrsClusterV2(name: string, args: MrsClusterV2Args, opts?: CustomResourceOptions);@overload
def MrsClusterV2(resource_name: str,
args: MrsClusterV2Args,
opts: Optional[ResourceOptions] = None)
@overload
def MrsClusterV2(resource_name: str,
opts: Optional[ResourceOptions] = None,
master_nodes: Optional[MrsClusterV2MasterNodesArgs] = None,
vpc_id: Optional[str] = None,
availability_zone: Optional[str] = None,
component_lists: Optional[Sequence[str]] = None,
version: Optional[str] = None,
subnet_id: Optional[str] = None,
node_key_pair: Optional[str] = None,
manager_admin_pwd: Optional[str] = None,
log_collection: Optional[bool] = None,
streaming_task_nodes: Optional[MrsClusterV2StreamingTaskNodesArgs] = None,
name: Optional[str] = None,
analysis_core_nodes: Optional[MrsClusterV2AnalysisCoreNodesArgs] = None,
public_ip: Optional[str] = None,
region: Optional[str] = None,
safe_mode: Optional[bool] = None,
security_group_ids: Optional[Sequence[str]] = None,
streaming_core_nodes: Optional[MrsClusterV2StreamingCoreNodesArgs] = None,
mrs_cluster_v2_id: Optional[str] = None,
eip_id: Optional[str] = None,
tags: Optional[Mapping[str, str]] = None,
template_id: Optional[str] = None,
timeouts: Optional[MrsClusterV2TimeoutsArgs] = None,
type: Optional[str] = None,
custom_nodes: Optional[Sequence[MrsClusterV2CustomNodeArgs]] = None,
analysis_task_nodes: Optional[MrsClusterV2AnalysisTaskNodesArgs] = None)func NewMrsClusterV2(ctx *Context, name string, args MrsClusterV2Args, opts ...ResourceOption) (*MrsClusterV2, error)public MrsClusterV2(string name, MrsClusterV2Args args, CustomResourceOptions? opts = null)
public MrsClusterV2(String name, MrsClusterV2Args args)
public MrsClusterV2(String name, MrsClusterV2Args args, CustomResourceOptions options)
type: flexibleengine:MrsClusterV2
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args MrsClusterV2Args
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args MrsClusterV2Args
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args MrsClusterV2Args
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args MrsClusterV2Args
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args MrsClusterV2Args
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var mrsClusterV2Resource = new Flexibleengine.MrsClusterV2("mrsClusterV2Resource", new()
{
MasterNodes = new Flexibleengine.Inputs.MrsClusterV2MasterNodesArgs
{
DataVolumeCount = 0,
Flavor = "string",
NodeNumber = 0,
RootVolumeSize = 0,
RootVolumeType = "string",
AssignedRoles = new[]
{
"string",
},
DataVolumeSize = 0,
DataVolumeType = "string",
HostIps = new[]
{
"string",
},
},
VpcId = "string",
AvailabilityZone = "string",
ComponentLists = new[]
{
"string",
},
Version = "string",
SubnetId = "string",
NodeKeyPair = "string",
ManagerAdminPwd = "string",
LogCollection = false,
StreamingTaskNodes = new Flexibleengine.Inputs.MrsClusterV2StreamingTaskNodesArgs
{
DataVolumeCount = 0,
Flavor = "string",
NodeNumber = 0,
RootVolumeSize = 0,
RootVolumeType = "string",
AssignedRoles = new[]
{
"string",
},
DataVolumeSize = 0,
DataVolumeType = "string",
HostIps = new[]
{
"string",
},
},
Name = "string",
AnalysisCoreNodes = new Flexibleengine.Inputs.MrsClusterV2AnalysisCoreNodesArgs
{
DataVolumeCount = 0,
Flavor = "string",
NodeNumber = 0,
RootVolumeSize = 0,
RootVolumeType = "string",
AssignedRoles = new[]
{
"string",
},
DataVolumeSize = 0,
DataVolumeType = "string",
HostIps = new[]
{
"string",
},
},
PublicIp = "string",
Region = "string",
SafeMode = false,
SecurityGroupIds = new[]
{
"string",
},
StreamingCoreNodes = new Flexibleengine.Inputs.MrsClusterV2StreamingCoreNodesArgs
{
DataVolumeCount = 0,
Flavor = "string",
NodeNumber = 0,
RootVolumeSize = 0,
RootVolumeType = "string",
AssignedRoles = new[]
{
"string",
},
DataVolumeSize = 0,
DataVolumeType = "string",
HostIps = new[]
{
"string",
},
},
MrsClusterV2Id = "string",
EipId = "string",
Tags =
{
{ "string", "string" },
},
TemplateId = "string",
Timeouts = new Flexibleengine.Inputs.MrsClusterV2TimeoutsArgs
{
Create = "string",
Delete = "string",
Update = "string",
},
Type = "string",
CustomNodes = new[]
{
new Flexibleengine.Inputs.MrsClusterV2CustomNodeArgs
{
DataVolumeCount = 0,
Flavor = "string",
GroupName = "string",
NodeNumber = 0,
RootVolumeSize = 0,
RootVolumeType = "string",
AssignedRoles = new[]
{
"string",
},
DataVolumeSize = 0,
DataVolumeType = "string",
HostIps = new[]
{
"string",
},
},
},
AnalysisTaskNodes = new Flexibleengine.Inputs.MrsClusterV2AnalysisTaskNodesArgs
{
DataVolumeCount = 0,
Flavor = "string",
NodeNumber = 0,
RootVolumeSize = 0,
RootVolumeType = "string",
AssignedRoles = new[]
{
"string",
},
DataVolumeSize = 0,
DataVolumeType = "string",
HostIps = new[]
{
"string",
},
},
});
example, err := flexibleengine.NewMrsClusterV2(ctx, "mrsClusterV2Resource", &flexibleengine.MrsClusterV2Args{
MasterNodes: &flexibleengine.MrsClusterV2MasterNodesArgs{
DataVolumeCount: pulumi.Float64(0),
Flavor: pulumi.String("string"),
NodeNumber: pulumi.Float64(0),
RootVolumeSize: pulumi.Float64(0),
RootVolumeType: pulumi.String("string"),
AssignedRoles: pulumi.StringArray{
pulumi.String("string"),
},
DataVolumeSize: pulumi.Float64(0),
DataVolumeType: pulumi.String("string"),
HostIps: pulumi.StringArray{
pulumi.String("string"),
},
},
VpcId: pulumi.String("string"),
AvailabilityZone: pulumi.String("string"),
ComponentLists: pulumi.StringArray{
pulumi.String("string"),
},
Version: pulumi.String("string"),
SubnetId: pulumi.String("string"),
NodeKeyPair: pulumi.String("string"),
ManagerAdminPwd: pulumi.String("string"),
LogCollection: pulumi.Bool(false),
StreamingTaskNodes: &flexibleengine.MrsClusterV2StreamingTaskNodesArgs{
DataVolumeCount: pulumi.Float64(0),
Flavor: pulumi.String("string"),
NodeNumber: pulumi.Float64(0),
RootVolumeSize: pulumi.Float64(0),
RootVolumeType: pulumi.String("string"),
AssignedRoles: pulumi.StringArray{
pulumi.String("string"),
},
DataVolumeSize: pulumi.Float64(0),
DataVolumeType: pulumi.String("string"),
HostIps: pulumi.StringArray{
pulumi.String("string"),
},
},
Name: pulumi.String("string"),
AnalysisCoreNodes: &flexibleengine.MrsClusterV2AnalysisCoreNodesArgs{
DataVolumeCount: pulumi.Float64(0),
Flavor: pulumi.String("string"),
NodeNumber: pulumi.Float64(0),
RootVolumeSize: pulumi.Float64(0),
RootVolumeType: pulumi.String("string"),
AssignedRoles: pulumi.StringArray{
pulumi.String("string"),
},
DataVolumeSize: pulumi.Float64(0),
DataVolumeType: pulumi.String("string"),
HostIps: pulumi.StringArray{
pulumi.String("string"),
},
},
PublicIp: pulumi.String("string"),
Region: pulumi.String("string"),
SafeMode: pulumi.Bool(false),
SecurityGroupIds: pulumi.StringArray{
pulumi.String("string"),
},
StreamingCoreNodes: &flexibleengine.MrsClusterV2StreamingCoreNodesArgs{
DataVolumeCount: pulumi.Float64(0),
Flavor: pulumi.String("string"),
NodeNumber: pulumi.Float64(0),
RootVolumeSize: pulumi.Float64(0),
RootVolumeType: pulumi.String("string"),
AssignedRoles: pulumi.StringArray{
pulumi.String("string"),
},
DataVolumeSize: pulumi.Float64(0),
DataVolumeType: pulumi.String("string"),
HostIps: pulumi.StringArray{
pulumi.String("string"),
},
},
MrsClusterV2Id: pulumi.String("string"),
EipId: pulumi.String("string"),
Tags: pulumi.StringMap{
"string": pulumi.String("string"),
},
TemplateId: pulumi.String("string"),
Timeouts: &flexibleengine.MrsClusterV2TimeoutsArgs{
Create: pulumi.String("string"),
Delete: pulumi.String("string"),
Update: pulumi.String("string"),
},
Type: pulumi.String("string"),
CustomNodes: flexibleengine.MrsClusterV2CustomNodeArray{
&flexibleengine.MrsClusterV2CustomNodeArgs{
DataVolumeCount: pulumi.Float64(0),
Flavor: pulumi.String("string"),
GroupName: pulumi.String("string"),
NodeNumber: pulumi.Float64(0),
RootVolumeSize: pulumi.Float64(0),
RootVolumeType: pulumi.String("string"),
AssignedRoles: pulumi.StringArray{
pulumi.String("string"),
},
DataVolumeSize: pulumi.Float64(0),
DataVolumeType: pulumi.String("string"),
HostIps: pulumi.StringArray{
pulumi.String("string"),
},
},
},
AnalysisTaskNodes: &flexibleengine.MrsClusterV2AnalysisTaskNodesArgs{
DataVolumeCount: pulumi.Float64(0),
Flavor: pulumi.String("string"),
NodeNumber: pulumi.Float64(0),
RootVolumeSize: pulumi.Float64(0),
RootVolumeType: pulumi.String("string"),
AssignedRoles: pulumi.StringArray{
pulumi.String("string"),
},
DataVolumeSize: pulumi.Float64(0),
DataVolumeType: pulumi.String("string"),
HostIps: pulumi.StringArray{
pulumi.String("string"),
},
},
})
var mrsClusterV2Resource = new MrsClusterV2("mrsClusterV2Resource", MrsClusterV2Args.builder()
.masterNodes(MrsClusterV2MasterNodesArgs.builder()
.dataVolumeCount(0)
.flavor("string")
.nodeNumber(0)
.rootVolumeSize(0)
.rootVolumeType("string")
.assignedRoles("string")
.dataVolumeSize(0)
.dataVolumeType("string")
.hostIps("string")
.build())
.vpcId("string")
.availabilityZone("string")
.componentLists("string")
.version("string")
.subnetId("string")
.nodeKeyPair("string")
.managerAdminPwd("string")
.logCollection(false)
.streamingTaskNodes(MrsClusterV2StreamingTaskNodesArgs.builder()
.dataVolumeCount(0)
.flavor("string")
.nodeNumber(0)
.rootVolumeSize(0)
.rootVolumeType("string")
.assignedRoles("string")
.dataVolumeSize(0)
.dataVolumeType("string")
.hostIps("string")
.build())
.name("string")
.analysisCoreNodes(MrsClusterV2AnalysisCoreNodesArgs.builder()
.dataVolumeCount(0)
.flavor("string")
.nodeNumber(0)
.rootVolumeSize(0)
.rootVolumeType("string")
.assignedRoles("string")
.dataVolumeSize(0)
.dataVolumeType("string")
.hostIps("string")
.build())
.publicIp("string")
.region("string")
.safeMode(false)
.securityGroupIds("string")
.streamingCoreNodes(MrsClusterV2StreamingCoreNodesArgs.builder()
.dataVolumeCount(0)
.flavor("string")
.nodeNumber(0)
.rootVolumeSize(0)
.rootVolumeType("string")
.assignedRoles("string")
.dataVolumeSize(0)
.dataVolumeType("string")
.hostIps("string")
.build())
.mrsClusterV2Id("string")
.eipId("string")
.tags(Map.of("string", "string"))
.templateId("string")
.timeouts(MrsClusterV2TimeoutsArgs.builder()
.create("string")
.delete("string")
.update("string")
.build())
.type("string")
.customNodes(MrsClusterV2CustomNodeArgs.builder()
.dataVolumeCount(0)
.flavor("string")
.groupName("string")
.nodeNumber(0)
.rootVolumeSize(0)
.rootVolumeType("string")
.assignedRoles("string")
.dataVolumeSize(0)
.dataVolumeType("string")
.hostIps("string")
.build())
.analysisTaskNodes(MrsClusterV2AnalysisTaskNodesArgs.builder()
.dataVolumeCount(0)
.flavor("string")
.nodeNumber(0)
.rootVolumeSize(0)
.rootVolumeType("string")
.assignedRoles("string")
.dataVolumeSize(0)
.dataVolumeType("string")
.hostIps("string")
.build())
.build());
mrs_cluster_v2_resource = flexibleengine.MrsClusterV2("mrsClusterV2Resource",
master_nodes={
"data_volume_count": 0,
"flavor": "string",
"node_number": 0,
"root_volume_size": 0,
"root_volume_type": "string",
"assigned_roles": ["string"],
"data_volume_size": 0,
"data_volume_type": "string",
"host_ips": ["string"],
},
vpc_id="string",
availability_zone="string",
component_lists=["string"],
version="string",
subnet_id="string",
node_key_pair="string",
manager_admin_pwd="string",
log_collection=False,
streaming_task_nodes={
"data_volume_count": 0,
"flavor": "string",
"node_number": 0,
"root_volume_size": 0,
"root_volume_type": "string",
"assigned_roles": ["string"],
"data_volume_size": 0,
"data_volume_type": "string",
"host_ips": ["string"],
},
name="string",
analysis_core_nodes={
"data_volume_count": 0,
"flavor": "string",
"node_number": 0,
"root_volume_size": 0,
"root_volume_type": "string",
"assigned_roles": ["string"],
"data_volume_size": 0,
"data_volume_type": "string",
"host_ips": ["string"],
},
public_ip="string",
region="string",
safe_mode=False,
security_group_ids=["string"],
streaming_core_nodes={
"data_volume_count": 0,
"flavor": "string",
"node_number": 0,
"root_volume_size": 0,
"root_volume_type": "string",
"assigned_roles": ["string"],
"data_volume_size": 0,
"data_volume_type": "string",
"host_ips": ["string"],
},
mrs_cluster_v2_id="string",
eip_id="string",
tags={
"string": "string",
},
template_id="string",
timeouts={
"create": "string",
"delete": "string",
"update": "string",
},
type="string",
custom_nodes=[{
"data_volume_count": 0,
"flavor": "string",
"group_name": "string",
"node_number": 0,
"root_volume_size": 0,
"root_volume_type": "string",
"assigned_roles": ["string"],
"data_volume_size": 0,
"data_volume_type": "string",
"host_ips": ["string"],
}],
analysis_task_nodes={
"data_volume_count": 0,
"flavor": "string",
"node_number": 0,
"root_volume_size": 0,
"root_volume_type": "string",
"assigned_roles": ["string"],
"data_volume_size": 0,
"data_volume_type": "string",
"host_ips": ["string"],
})
const mrsClusterV2Resource = new flexibleengine.MrsClusterV2("mrsClusterV2Resource", {
masterNodes: {
dataVolumeCount: 0,
flavor: "string",
nodeNumber: 0,
rootVolumeSize: 0,
rootVolumeType: "string",
assignedRoles: ["string"],
dataVolumeSize: 0,
dataVolumeType: "string",
hostIps: ["string"],
},
vpcId: "string",
availabilityZone: "string",
componentLists: ["string"],
version: "string",
subnetId: "string",
nodeKeyPair: "string",
managerAdminPwd: "string",
logCollection: false,
streamingTaskNodes: {
dataVolumeCount: 0,
flavor: "string",
nodeNumber: 0,
rootVolumeSize: 0,
rootVolumeType: "string",
assignedRoles: ["string"],
dataVolumeSize: 0,
dataVolumeType: "string",
hostIps: ["string"],
},
name: "string",
analysisCoreNodes: {
dataVolumeCount: 0,
flavor: "string",
nodeNumber: 0,
rootVolumeSize: 0,
rootVolumeType: "string",
assignedRoles: ["string"],
dataVolumeSize: 0,
dataVolumeType: "string",
hostIps: ["string"],
},
publicIp: "string",
region: "string",
safeMode: false,
securityGroupIds: ["string"],
streamingCoreNodes: {
dataVolumeCount: 0,
flavor: "string",
nodeNumber: 0,
rootVolumeSize: 0,
rootVolumeType: "string",
assignedRoles: ["string"],
dataVolumeSize: 0,
dataVolumeType: "string",
hostIps: ["string"],
},
mrsClusterV2Id: "string",
eipId: "string",
tags: {
string: "string",
},
templateId: "string",
timeouts: {
create: "string",
"delete": "string",
update: "string",
},
type: "string",
customNodes: [{
dataVolumeCount: 0,
flavor: "string",
groupName: "string",
nodeNumber: 0,
rootVolumeSize: 0,
rootVolumeType: "string",
assignedRoles: ["string"],
dataVolumeSize: 0,
dataVolumeType: "string",
hostIps: ["string"],
}],
analysisTaskNodes: {
dataVolumeCount: 0,
flavor: "string",
nodeNumber: 0,
rootVolumeSize: 0,
rootVolumeType: "string",
assignedRoles: ["string"],
dataVolumeSize: 0,
dataVolumeType: "string",
hostIps: ["string"],
},
});
type: flexibleengine:MrsClusterV2
properties:
analysisCoreNodes:
assignedRoles:
- string
dataVolumeCount: 0
dataVolumeSize: 0
dataVolumeType: string
flavor: string
hostIps:
- string
nodeNumber: 0
rootVolumeSize: 0
rootVolumeType: string
analysisTaskNodes:
assignedRoles:
- string
dataVolumeCount: 0
dataVolumeSize: 0
dataVolumeType: string
flavor: string
hostIps:
- string
nodeNumber: 0
rootVolumeSize: 0
rootVolumeType: string
availabilityZone: string
componentLists:
- string
customNodes:
- assignedRoles:
- string
dataVolumeCount: 0
dataVolumeSize: 0
dataVolumeType: string
flavor: string
groupName: string
hostIps:
- string
nodeNumber: 0
rootVolumeSize: 0
rootVolumeType: string
eipId: string
logCollection: false
managerAdminPwd: string
masterNodes:
assignedRoles:
- string
dataVolumeCount: 0
dataVolumeSize: 0
dataVolumeType: string
flavor: string
hostIps:
- string
nodeNumber: 0
rootVolumeSize: 0
rootVolumeType: string
mrsClusterV2Id: string
name: string
nodeKeyPair: string
publicIp: string
region: string
safeMode: false
securityGroupIds:
- string
streamingCoreNodes:
assignedRoles:
- string
dataVolumeCount: 0
dataVolumeSize: 0
dataVolumeType: string
flavor: string
hostIps:
- string
nodeNumber: 0
rootVolumeSize: 0
rootVolumeType: string
streamingTaskNodes:
assignedRoles:
- string
dataVolumeCount: 0
dataVolumeSize: 0
dataVolumeType: string
flavor: string
hostIps:
- string
nodeNumber: 0
rootVolumeSize: 0
rootVolumeType: string
subnetId: string
tags:
string: string
templateId: string
timeouts:
create: string
delete: string
update: string
type: string
version: string
vpcId: string
MrsClusterV2 Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The MrsClusterV2 resource accepts the following input properties:
- Availability
Zone string - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- Component
Lists List<string> - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- Manager
Admin stringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - Master
Nodes MrsCluster V2Master Nodes - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - Node
Key stringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- Subnet
Id string - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - Vpc
Id string - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Analysis
Core MrsNodes Cluster V2Analysis Core Nodes - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - Analysis
Task MrsNodes Cluster V2Analysis Task Nodes - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - Custom
Nodes List<MrsCluster V2Custom Node> - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - Eip
Id string - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- Log
Collection bool - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - Mrs
Cluster stringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- Name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- Public
Ip string - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- Region string
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- Safe
Mode bool - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- Security
Group List<string>Ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- Streaming
Core MrsNodes Cluster V2Streaming Core Nodes - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - Streaming
Task MrsNodes Cluster V2Streaming Task Nodes - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - Dictionary<string, string>
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- Template
Id string - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- Timeouts
Mrs
Cluster V2Timeouts - Type string
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- Availability
Zone string - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- Component
Lists []string - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- Manager
Admin stringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - Master
Nodes MrsCluster V2Master Nodes Args - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - Node
Key stringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- Subnet
Id string - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - Vpc
Id string - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Analysis
Core MrsNodes Cluster V2Analysis Core Nodes Args - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - Analysis
Task MrsNodes Cluster V2Analysis Task Nodes Args - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - Custom
Nodes []MrsCluster V2Custom Node Args - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - Eip
Id string - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- Log
Collection bool - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - Mrs
Cluster stringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- Name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- Public
Ip string - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- Region string
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- Safe
Mode bool - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- Security
Group []stringIds - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- Streaming
Core MrsNodes Cluster V2Streaming Core Nodes Args - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - Streaming
Task MrsNodes Cluster V2Streaming Task Nodes Args - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - map[string]string
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- Template
Id string - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- Timeouts
Mrs
Cluster V2Timeouts Args - Type string
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- availability
Zone String - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- component
Lists List<String> - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- manager
Admin StringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - master
Nodes MrsCluster V2Master Nodes - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - node
Key StringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- subnet
Id String - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- version String
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - vpc
Id String - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- analysis
Core MrsNodes Cluster V2Analysis Core Nodes - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - analysis
Task MrsNodes Cluster V2Analysis Task Nodes - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - custom
Nodes List<MrsCluster V2Custom Node> - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - eip
Id String - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- log
Collection Boolean - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - mrs
Cluster StringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name String
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- public
Ip String - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- region String
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- safe
Mode Boolean - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- security
Group List<String>Ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- streaming
Core MrsNodes Cluster V2Streaming Core Nodes - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - streaming
Task MrsNodes Cluster V2Streaming Task Nodes - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - Map<String,String>
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- template
Id String - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- timeouts
Mrs
Cluster V2Timeouts - type String
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- availability
Zone string - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- component
Lists string[] - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- manager
Admin stringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - master
Nodes MrsCluster V2Master Nodes - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - node
Key stringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- subnet
Id string - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - vpc
Id string - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- analysis
Core MrsNodes Cluster V2Analysis Core Nodes - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - analysis
Task MrsNodes Cluster V2Analysis Task Nodes - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - custom
Nodes MrsCluster V2Custom Node[] - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - eip
Id string - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- log
Collection boolean - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - mrs
Cluster stringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- public
Ip string - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- region string
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- safe
Mode boolean - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- security
Group string[]Ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- streaming
Core MrsNodes Cluster V2Streaming Core Nodes - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - streaming
Task MrsNodes Cluster V2Streaming Task Nodes - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - {[key: string]: string}
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- template
Id string - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- timeouts
Mrs
Cluster V2Timeouts - type string
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- availability_
zone str - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- component_
lists Sequence[str] - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- manager_
admin_ strpwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - master_
nodes MrsCluster V2Master Nodes Args - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - node_
key_ strpair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- subnet_
id str - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- version str
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - vpc_
id str - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- analysis_
core_ Mrsnodes Cluster V2Analysis Core Nodes Args - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - analysis_
task_ Mrsnodes Cluster V2Analysis Task Nodes Args - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - custom_
nodes Sequence[MrsCluster V2Custom Node Args] - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - eip_
id str - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- log_
collection bool - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - mrs_
cluster_ strv2_ id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name str
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- public_
ip str - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- region str
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- safe_
mode bool - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- security_
group_ Sequence[str]ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- streaming_
core_ Mrsnodes Cluster V2Streaming Core Nodes Args - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - streaming_
task_ Mrsnodes Cluster V2Streaming Task Nodes Args - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - Mapping[str, str]
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- template_
id str - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- timeouts
Mrs
Cluster V2Timeouts Args - type str
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- availability
Zone String - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- component
Lists List<String> - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- manager
Admin StringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - master
Nodes Property Map - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - node
Key StringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- subnet
Id String - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- version String
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - vpc
Id String - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- analysis
Core Property MapNodes - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - analysis
Task Property MapNodes - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - custom
Nodes List<Property Map> - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - eip
Id String - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- log
Collection Boolean - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - mrs
Cluster StringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name String
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- public
Ip String - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- region String
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- safe
Mode Boolean - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- security
Group List<String>Ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- streaming
Core Property MapNodes - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - streaming
Task Property MapNodes - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - Map<String>
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- template
Id String - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- timeouts Property Map
- type String
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
Outputs
All input properties are implicitly available as output properties. Additionally, the MrsClusterV2 resource produces the following output properties:
- Charging
Start stringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- Components
List<Mrs
Cluster V2Component> - Component list information. The components object structure is documented below.
- Create
Time string - The cluster creation time, in RFC-3339 format.
- Id string
- The provider-assigned unique ID for this managed resource.
- Master
Node stringIp - The IP address of the master node.
- Private
Ip string - The preferred private IP address of the master node.
- Status string
- The cluster state, which include: running, frozen, abnormal and failed.
- Total
Node doubleNumber - The total number of nodes deployed in the cluster.
- Update
Time string - The cluster update time, in RFC-3339 format.
- Charging
Start stringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- Components
[]Mrs
Cluster V2Component - Component list information. The components object structure is documented below.
- Create
Time string - The cluster creation time, in RFC-3339 format.
- Id string
- The provider-assigned unique ID for this managed resource.
- Master
Node stringIp - The IP address of the master node.
- Private
Ip string - The preferred private IP address of the master node.
- Status string
- The cluster state, which include: running, frozen, abnormal and failed.
- Total
Node float64Number - The total number of nodes deployed in the cluster.
- Update
Time string - The cluster update time, in RFC-3339 format.
- charging
Start StringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- components
List<Mrs
Cluster V2Component> - Component list information. The components object structure is documented below.
- create
Time String - The cluster creation time, in RFC-3339 format.
- id String
- The provider-assigned unique ID for this managed resource.
- master
Node StringIp - The IP address of the master node.
- private
Ip String - The preferred private IP address of the master node.
- status String
- The cluster state, which include: running, frozen, abnormal and failed.
- total
Node DoubleNumber - The total number of nodes deployed in the cluster.
- update
Time String - The cluster update time, in RFC-3339 format.
- charging
Start stringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- components
Mrs
Cluster V2Component[] - Component list information. The components object structure is documented below.
- create
Time string - The cluster creation time, in RFC-3339 format.
- id string
- The provider-assigned unique ID for this managed resource.
- master
Node stringIp - The IP address of the master node.
- private
Ip string - The preferred private IP address of the master node.
- status string
- The cluster state, which include: running, frozen, abnormal and failed.
- total
Node numberNumber - The total number of nodes deployed in the cluster.
- update
Time string - The cluster update time, in RFC-3339 format.
- charging_
start_ strtime - The charging start time which is the start time of billing, in RFC-3339 format.
- components
Sequence[Mrs
Cluster V2Component] - Component list information. The components object structure is documented below.
- create_
time str - The cluster creation time, in RFC-3339 format.
- id str
- The provider-assigned unique ID for this managed resource.
- master_
node_ strip - The IP address of the master node.
- private_
ip str - The preferred private IP address of the master node.
- status str
- The cluster state, which include: running, frozen, abnormal and failed.
- total_
node_ floatnumber - The total number of nodes deployed in the cluster.
- update_
time str - The cluster update time, in RFC-3339 format.
- charging
Start StringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- components List<Property Map>
- Component list information. The components object structure is documented below.
- create
Time String - The cluster creation time, in RFC-3339 format.
- id String
- The provider-assigned unique ID for this managed resource.
- master
Node StringIp - The IP address of the master node.
- private
Ip String - The preferred private IP address of the master node.
- status String
- The cluster state, which include: running, frozen, abnormal and failed.
- total
Node NumberNumber - The total number of nodes deployed in the cluster.
- update
Time String - The cluster update time, in RFC-3339 format.
Look up Existing MrsClusterV2 Resource
Get an existing MrsClusterV2 resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: MrsClusterV2State, opts?: CustomResourceOptions): MrsClusterV2@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
analysis_core_nodes: Optional[MrsClusterV2AnalysisCoreNodesArgs] = None,
analysis_task_nodes: Optional[MrsClusterV2AnalysisTaskNodesArgs] = None,
availability_zone: Optional[str] = None,
charging_start_time: Optional[str] = None,
component_lists: Optional[Sequence[str]] = None,
components: Optional[Sequence[MrsClusterV2ComponentArgs]] = None,
create_time: Optional[str] = None,
custom_nodes: Optional[Sequence[MrsClusterV2CustomNodeArgs]] = None,
eip_id: Optional[str] = None,
log_collection: Optional[bool] = None,
manager_admin_pwd: Optional[str] = None,
master_node_ip: Optional[str] = None,
master_nodes: Optional[MrsClusterV2MasterNodesArgs] = None,
mrs_cluster_v2_id: Optional[str] = None,
name: Optional[str] = None,
node_key_pair: Optional[str] = None,
private_ip: Optional[str] = None,
public_ip: Optional[str] = None,
region: Optional[str] = None,
safe_mode: Optional[bool] = None,
security_group_ids: Optional[Sequence[str]] = None,
status: Optional[str] = None,
streaming_core_nodes: Optional[MrsClusterV2StreamingCoreNodesArgs] = None,
streaming_task_nodes: Optional[MrsClusterV2StreamingTaskNodesArgs] = None,
subnet_id: Optional[str] = None,
tags: Optional[Mapping[str, str]] = None,
template_id: Optional[str] = None,
timeouts: Optional[MrsClusterV2TimeoutsArgs] = None,
total_node_number: Optional[float] = None,
type: Optional[str] = None,
update_time: Optional[str] = None,
version: Optional[str] = None,
vpc_id: Optional[str] = None) -> MrsClusterV2func GetMrsClusterV2(ctx *Context, name string, id IDInput, state *MrsClusterV2State, opts ...ResourceOption) (*MrsClusterV2, error)public static MrsClusterV2 Get(string name, Input<string> id, MrsClusterV2State? state, CustomResourceOptions? opts = null)public static MrsClusterV2 get(String name, Output<String> id, MrsClusterV2State state, CustomResourceOptions options)resources: _: type: flexibleengine:MrsClusterV2 get: id: ${id}- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Analysis
Core MrsNodes Cluster V2Analysis Core Nodes - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - Analysis
Task MrsNodes Cluster V2Analysis Task Nodes - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - Availability
Zone string - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- Charging
Start stringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- Component
Lists List<string> - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- Components
List<Mrs
Cluster V2Component> - Component list information. The components object structure is documented below.
- Create
Time string - The cluster creation time, in RFC-3339 format.
- Custom
Nodes List<MrsCluster V2Custom Node> - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - Eip
Id string - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- Log
Collection bool - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - Manager
Admin stringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - Master
Node stringIp - The IP address of the master node.
- Master
Nodes MrsCluster V2Master Nodes - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - Mrs
Cluster stringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- Name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- Node
Key stringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- Private
Ip string - The preferred private IP address of the master node.
- Public
Ip string - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- Region string
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- Safe
Mode bool - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- Security
Group List<string>Ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- Status string
- The cluster state, which include: running, frozen, abnormal and failed.
- Streaming
Core MrsNodes Cluster V2Streaming Core Nodes - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - Streaming
Task MrsNodes Cluster V2Streaming Task Nodes - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - Subnet
Id string - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Dictionary<string, string>
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- Template
Id string - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- Timeouts
Mrs
Cluster V2Timeouts - Total
Node doubleNumber - The total number of nodes deployed in the cluster.
- Type string
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- Update
Time string - The cluster update time, in RFC-3339 format.
- Version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - Vpc
Id string - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Analysis
Core MrsNodes Cluster V2Analysis Core Nodes Args - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - Analysis
Task MrsNodes Cluster V2Analysis Task Nodes Args - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - Availability
Zone string - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- Charging
Start stringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- Component
Lists []string - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- Components
[]Mrs
Cluster V2Component Args - Component list information. The components object structure is documented below.
- Create
Time string - The cluster creation time, in RFC-3339 format.
- Custom
Nodes []MrsCluster V2Custom Node Args - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - Eip
Id string - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- Log
Collection bool - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - Manager
Admin stringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - Master
Node stringIp - The IP address of the master node.
- Master
Nodes MrsCluster V2Master Nodes Args - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - Mrs
Cluster stringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- Name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- Node
Key stringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- Private
Ip string - The preferred private IP address of the master node.
- Public
Ip string - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- Region string
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- Safe
Mode bool - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- Security
Group []stringIds - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- Status string
- The cluster state, which include: running, frozen, abnormal and failed.
- Streaming
Core MrsNodes Cluster V2Streaming Core Nodes Args - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - Streaming
Task MrsNodes Cluster V2Streaming Task Nodes Args - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - Subnet
Id string - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- map[string]string
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- Template
Id string - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- Timeouts
Mrs
Cluster V2Timeouts Args - Total
Node float64Number - The total number of nodes deployed in the cluster.
- Type string
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- Update
Time string - The cluster update time, in RFC-3339 format.
- Version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - Vpc
Id string - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- analysis
Core MrsNodes Cluster V2Analysis Core Nodes - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - analysis
Task MrsNodes Cluster V2Analysis Task Nodes - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - availability
Zone String - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- charging
Start StringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- component
Lists List<String> - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- components
List<Mrs
Cluster V2Component> - Component list information. The components object structure is documented below.
- create
Time String - The cluster creation time, in RFC-3339 format.
- custom
Nodes List<MrsCluster V2Custom Node> - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - eip
Id String - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- log
Collection Boolean - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - manager
Admin StringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - master
Node StringIp - The IP address of the master node.
- master
Nodes MrsCluster V2Master Nodes - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - mrs
Cluster StringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name String
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- node
Key StringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- private
Ip String - The preferred private IP address of the master node.
- public
Ip String - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- region String
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- safe
Mode Boolean - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- security
Group List<String>Ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- status String
- The cluster state, which include: running, frozen, abnormal and failed.
- streaming
Core MrsNodes Cluster V2Streaming Core Nodes - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - streaming
Task MrsNodes Cluster V2Streaming Task Nodes - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - subnet
Id String - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Map<String,String>
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- template
Id String - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- timeouts
Mrs
Cluster V2Timeouts - total
Node DoubleNumber - The total number of nodes deployed in the cluster.
- type String
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- update
Time String - The cluster update time, in RFC-3339 format.
- version String
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - vpc
Id String - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- analysis
Core MrsNodes Cluster V2Analysis Core Nodes - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - analysis
Task MrsNodes Cluster V2Analysis Task Nodes - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - availability
Zone string - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- charging
Start stringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- component
Lists string[] - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- components
Mrs
Cluster V2Component[] - Component list information. The components object structure is documented below.
- create
Time string - The cluster creation time, in RFC-3339 format.
- custom
Nodes MrsCluster V2Custom Node[] - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - eip
Id string - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- log
Collection boolean - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - manager
Admin stringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - master
Node stringIp - The IP address of the master node.
- master
Nodes MrsCluster V2Master Nodes - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - mrs
Cluster stringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- node
Key stringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- private
Ip string - The preferred private IP address of the master node.
- public
Ip string - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- region string
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- safe
Mode boolean - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- security
Group string[]Ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- status string
- The cluster state, which include: running, frozen, abnormal and failed.
- streaming
Core MrsNodes Cluster V2Streaming Core Nodes - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - streaming
Task MrsNodes Cluster V2Streaming Task Nodes - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - subnet
Id string - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- {[key: string]: string}
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- template
Id string - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- timeouts
Mrs
Cluster V2Timeouts - total
Node numberNumber - The total number of nodes deployed in the cluster.
- type string
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- update
Time string - The cluster update time, in RFC-3339 format.
- version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - vpc
Id string - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- analysis_
core_ Mrsnodes Cluster V2Analysis Core Nodes Args - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - analysis_
task_ Mrsnodes Cluster V2Analysis Task Nodes Args - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - availability_
zone str - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- charging_
start_ strtime - The charging start time which is the start time of billing, in RFC-3339 format.
- component_
lists Sequence[str] - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- components
Sequence[Mrs
Cluster V2Component Args] - Component list information. The components object structure is documented below.
- create_
time str - The cluster creation time, in RFC-3339 format.
- custom_
nodes Sequence[MrsCluster V2Custom Node Args] - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - eip_
id str - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- log_
collection bool - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - manager_
admin_ strpwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - master_
node_ strip - The IP address of the master node.
- master_
nodes MrsCluster V2Master Nodes Args - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - mrs_
cluster_ strv2_ id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name str
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- node_
key_ strpair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- private_
ip str - The preferred private IP address of the master node.
- public_
ip str - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- region str
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- safe_
mode bool - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- security_
group_ Sequence[str]ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- status str
- The cluster state, which include: running, frozen, abnormal and failed.
- streaming_
core_ Mrsnodes Cluster V2Streaming Core Nodes Args - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - streaming_
task_ Mrsnodes Cluster V2Streaming Task Nodes Args - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - subnet_
id str - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Mapping[str, str]
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- template_
id str - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- timeouts
Mrs
Cluster V2Timeouts Args - total_
node_ floatnumber - The total number of nodes deployed in the cluster.
- type str
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- update_
time str - The cluster update time, in RFC-3339 format.
- version str
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - vpc_
id str - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- analysis
Core Property MapNodes - Specifies a list of the information about the analysis core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_core_nodesis documented below. - analysis
Task Property MapNodes - Specifies a list of the information about the analysis task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
analysis_task_nodesis documented below. - availability
Zone String - Specifies the availability zone in which to create the cluster. Changing this will create a new MRS cluster resource.
- charging
Start StringTime - The charging start time which is the start time of billing, in RFC-3339 format.
- component
Lists List<String> - Specifies the list of component names. Changing this will create a new MRS cluster resource. The supported components are as follows:
- components List<Property Map>
- Component list information. The components object structure is documented below.
- create
Time String - The cluster creation time, in RFC-3339 format.
- custom
Nodes List<Property Map> - Specifies a list of the information about the custom nodes in the MRS
cluster. Unlike other nodes, it needs to specify group_name. Changing this will create a new MRS cluster resource.
The nodes object structure of the
custom_nodesis documented below. - eip
Id String - Specifies the EIP ID which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- log
Collection Boolean - Specifies whether logs are collected when cluster installation fails.
Default to true. If
log_collectionset true, the OBS buckets will be created and only used to collect logs that record MRS cluster creation failures. Changing this will create a new MRS cluster resource. - manager
Admin StringPwd - Specifies the administrator password, which is used to login to
the cluster management page. The password can contain 8 to 26 charactors and cannot be the username or the username
spelled backwards. The password must contain lowercase letters, uppercase letters, digits, spaces and the special
characters:
!?,.:-_{}[]@$^+=/. Changing this will create a new MRS cluster resource. - master
Node StringIp - The IP address of the master node.
- master
Nodes Property Map - Specifies a list of the information about the master nodes in the
MRS cluster.
The nodes object structure of the
master_nodesis documented below. Changing this will create a new MRS cluster resource. - mrs
Cluster StringV2Id - Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name String
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- node
Key StringPair - Specifies the name of a key pair, which is used to login to the each nodes(ECSs). Changing this will create a new MRS cluster resource.
- private
Ip String - The preferred private IP address of the master node.
- public
Ip String - Specifies the EIP address which bound to the MRS cluster. The EIP must have been created and must be in the same region as the cluster. Changing this will create a new MRS cluster resource.
- region String
- The region in which to create the MRS cluster resource. If omitted, the provider-level region will be used. Changing this will create a new MRS cluster resource.
- safe
Mode Boolean - Specifies whether the running mode of the MRS cluster is secure,
default to true.
- true: enable Kerberos authentication.
- false: disable Kerberos authentication. Changing this will create a new MRS cluster resource.
- security
Group List<String>Ids - Specifies an array of one or more security group ID to attach to the MRS cluster. If using the specified security group, the group need to open the specified port (9022) rules. Changing this will create a new MRS cluster resource.
- status String
- The cluster state, which include: running, frozen, abnormal and failed.
- streaming
Core Property MapNodes - Specifies a list of the information about the streaming core nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_core_nodesis documented below. - streaming
Task Property MapNodes - Specifies a list of the information about the streaming task nodes
in the MRS cluster. Changing this will create a new MRS cluster resource.
The nodes object structure of the
streaming_task_nodesis documented below. - subnet
Id String - Specifies the ID of the VPC Subnet which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
- Map<String>
Specifies the key/value pairs to associate with the cluster.
The
nodesblock supports:- template
Id String - Specifies the template used for node deployment when the cluster type is
CUSTOM. Changing this will create a new MRS cluster resource.
- mgmt_control_combined_v2: template for jointly deploying the management and control nodes. The management and control roles are co-deployed on the Master node, and data instances are deployed in the same node group. This deployment mode applies to scenarios where the number of control nodes is less than 100, reducing costs.
- mgmt_control_separated_v2: The management and control roles are deployed on different master nodes, and data instances are deployed in the same node group. This deployment mode is applicable to a cluster with 100 to 500 nodes and delivers better performance in high-concurrency load scenarios.
- mgmt_control_data_separated_v2: The management role and control role are deployed on different Master nodes, and data instances are deployed in different node groups. This deployment mode is applicable to a cluster with more than 500 nodes. Components can be deployed separately, which can be used for a larger cluster scale.
- timeouts Property Map
- total
Node NumberNumber - The total number of nodes deployed in the cluster.
- type String
- Specifies the type of the MRS cluster. The valid values are ANALYSIS, STREAMING, MIXED and CUSTOM (supported in MRS 3.x only), default to ANALYSIS. Changing this will create a new MRS cluster resource.
- update
Time String - The cluster update time, in RFC-3339 format.
- version String
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource. - vpc
Id String - Specifies the ID of the VPC which bound to the MRS cluster. Changing this will create a new MRS cluster resource.
Supporting Types
MrsClusterV2AnalysisCoreNodes, MrsClusterV2AnalysisCoreNodesArgs
- Data
Volume doubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume doubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles List<string> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume doubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips List<string> - The host list of this nodes group in the cluster.
- Data
Volume float64Count Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number float64 - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume float64Size - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles []string Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume float64Size - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips []string - The host list of this nodes group in the cluster.
- data
Volume DoubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume DoubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume DoubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
- data
Volume numberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume numberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles string[] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume numberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips string[] - The host list of this nodes group in the cluster.
- data_
volume_ floatcount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor str
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node_
number float - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root_
volume_ floatsize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root_
volume_ strtype - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned_
roles Sequence[str] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data_
volume_ floatsize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data_
volume_ strtype - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host_
ips Sequence[str] - The host list of this nodes group in the cluster.
- data
Volume NumberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume NumberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume NumberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
MrsClusterV2AnalysisTaskNodes, MrsClusterV2AnalysisTaskNodesArgs
- Data
Volume doubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume doubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles List<string> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume doubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips List<string> - The host list of this nodes group in the cluster.
- Data
Volume float64Count Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number float64 - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume float64Size - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles []string Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume float64Size - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips []string - The host list of this nodes group in the cluster.
- data
Volume DoubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume DoubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume DoubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
- data
Volume numberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume numberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles string[] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume numberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips string[] - The host list of this nodes group in the cluster.
- data_
volume_ floatcount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor str
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node_
number float - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root_
volume_ floatsize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root_
volume_ strtype - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned_
roles Sequence[str] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data_
volume_ floatsize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data_
volume_ strtype - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host_
ips Sequence[str] - The host list of this nodes group in the cluster.
- data
Volume NumberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume NumberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume NumberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
MrsClusterV2Component, MrsClusterV2ComponentArgs
- Description string
- Component description.
- Id string
- Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- Name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- Version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource.
- Description string
- Component description.
- Id string
- Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- Name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- Version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource.
- description String
- Component description.
- id String
- Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name String
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- version String
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource.
- description string
- Component description.
- id string
- Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name string
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- version string
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource.
- description str
- Component description.
- id str
- Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name str
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- version str
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource.
- description String
- Component description.
- id String
- Component ID. For example, component_id of Hadoop is MRS 3.1.0-LTS.1_001, MRS 2.0.1_001, and MRS 1.8.9_001.
- name String
- Specifies the name of the MRS cluster. The name can contain 2 to 64 characters, which may consist of letters, digits, underscores (_) and hyphens (-). Changing this will create a new MRS cluster resource.
- version String
- Specifies the MRS cluster version. Currently,
MRS 1.8.9,MRS 2.0.1, andMRS 3.1.0-LTS.1are supported. Changing this will create a new MRS cluster resource.
MrsClusterV2CustomNode, MrsClusterV2CustomNodeArgs
- Data
Volume doubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Group
Name string - Specifies the name of nodes for the node group. This argument is Required when the cluster type is CUSTOM. Changing this will create a new MRS cluster resource.
- Node
Number double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume doubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles List<string> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume doubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips List<string> - The host list of this nodes group in the cluster.
- Data
Volume float64Count Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Group
Name string - Specifies the name of nodes for the node group. This argument is Required when the cluster type is CUSTOM. Changing this will create a new MRS cluster resource.
- Node
Number float64 - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume float64Size - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles []string Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume float64Size - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips []string - The host list of this nodes group in the cluster.
- data
Volume DoubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- group
Name String - Specifies the name of nodes for the node group. This argument is Required when the cluster type is CUSTOM. Changing this will create a new MRS cluster resource.
- node
Number Double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume DoubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume DoubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
- data
Volume numberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- group
Name string - Specifies the name of nodes for the node group. This argument is Required when the cluster type is CUSTOM. Changing this will create a new MRS cluster resource.
- node
Number number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume numberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles string[] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume numberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips string[] - The host list of this nodes group in the cluster.
- data_
volume_ floatcount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor str
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- group_
name str - Specifies the name of nodes for the node group. This argument is Required when the cluster type is CUSTOM. Changing this will create a new MRS cluster resource.
- node_
number float - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root_
volume_ floatsize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root_
volume_ strtype - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned_
roles Sequence[str] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data_
volume_ floatsize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data_
volume_ strtype - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host_
ips Sequence[str] - The host list of this nodes group in the cluster.
- data
Volume NumberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- group
Name String - Specifies the name of nodes for the node group. This argument is Required when the cluster type is CUSTOM. Changing this will create a new MRS cluster resource.
- node
Number Number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume NumberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume NumberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
MrsClusterV2MasterNodes, MrsClusterV2MasterNodesArgs
- Data
Volume doubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume doubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles List<string> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume doubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips List<string> - The host list of this nodes group in the cluster.
- Data
Volume float64Count Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number float64 - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume float64Size - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles []string Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume float64Size - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips []string - The host list of this nodes group in the cluster.
- data
Volume DoubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume DoubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume DoubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
- data
Volume numberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume numberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles string[] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume numberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips string[] - The host list of this nodes group in the cluster.
- data_
volume_ floatcount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor str
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node_
number float - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root_
volume_ floatsize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root_
volume_ strtype - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned_
roles Sequence[str] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data_
volume_ floatsize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data_
volume_ strtype - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host_
ips Sequence[str] - The host list of this nodes group in the cluster.
- data
Volume NumberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume NumberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume NumberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
MrsClusterV2StreamingCoreNodes, MrsClusterV2StreamingCoreNodesArgs
- Data
Volume doubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume doubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles List<string> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume doubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips List<string> - The host list of this nodes group in the cluster.
- Data
Volume float64Count Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number float64 - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume float64Size - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles []string Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume float64Size - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips []string - The host list of this nodes group in the cluster.
- data
Volume DoubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume DoubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume DoubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
- data
Volume numberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume numberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles string[] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume numberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips string[] - The host list of this nodes group in the cluster.
- data_
volume_ floatcount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor str
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node_
number float - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root_
volume_ floatsize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root_
volume_ strtype - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned_
roles Sequence[str] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data_
volume_ floatsize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data_
volume_ strtype - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host_
ips Sequence[str] - The host list of this nodes group in the cluster.
- data
Volume NumberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume NumberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume NumberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
MrsClusterV2StreamingTaskNodes, MrsClusterV2StreamingTaskNodesArgs
- Data
Volume doubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume doubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles List<string> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume doubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips List<string> - The host list of this nodes group in the cluster.
- Data
Volume float64Count Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- Flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- Node
Number float64 - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- Root
Volume float64Size - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- Root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- Assigned
Roles []string Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- Data
Volume float64Size - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - Data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- Host
Ips []string - The host list of this nodes group in the cluster.
- data
Volume DoubleCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Double - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume DoubleSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume DoubleSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
- data
Volume numberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor string
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume numberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume stringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles string[] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume numberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume stringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips string[] - The host list of this nodes group in the cluster.
- data_
volume_ floatcount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor str
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node_
number float - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root_
volume_ floatsize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root_
volume_ strtype - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned_
roles Sequence[str] Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data_
volume_ floatsize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data_
volume_ strtype - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host_
ips Sequence[str] - The host list of this nodes group in the cluster.
- data
Volume NumberCount Specifies the data disk number of the nodes. The number configuration of each node are as follows:
- master_nodes: 1.
- analysis_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- streaming_core_nodes: minimum is one and the maximum is subject to the configuration of the corresponding flavor.
- analysis_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
- streaming_task_nodes: minimum is zero and the maximum is subject to the configuration of the corresponding flavor.
Changing this will create a new MRS cluster resource.
- flavor String
- Specifies the instance specifications for each nodes in node group. Changing this will create a new MRS cluster resource.
- node
Number Number - Specifies the number of nodes for the node group. Only the core group and task group updations are allowed. The number of nodes after scaling cannot be less than the number of nodes originally created. It is ForceNew when the node type are master_nodes or custom_nodes, and changing this will create a new MRS cluster resource.
- root
Volume NumberSize - Specifies the system disk size of the nodes. Changing this will create a new MRS cluster resource.
- root
Volume StringType - Specifies the system disk flavor of the nodes. Changing this will create a new MRS cluster resource.
- assigned
Roles List<String> Specifies the roles deployed in a node group. This argument is Required when the cluster type is CUSTOM. Each character string represents a role expression. Changing this will create a new MRS cluster resource.
Role expression definition:
- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
DataNode. - If the role is deployed on a specified subscript node in the node group: role_name:index1,index2..., indexN,
for example:
DataNode:1,2. The subscript starts from 1. - Some roles support multi-instance deployment (that is, multiple instances of the same role are deployed on a node):
role_name[instance_count], for example:
EsNode[9].
Mapping between roles and components
DBServiceis a basic component of a cluster. Components such as Hive, Hue, Oozie, Loader, and Redis, and Loader store their metadata in DBService, and provide the metadata backup and restoration functions by using DBService.- If the role is deployed on all nodes in the node group, set this parameter to role_name, for example:
- data
Volume NumberSize - Specifies the data disk size of the nodes,in GB. The value range is 10
to 32768. Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. - data
Volume StringType - Specifies the data disk flavor of the nodes.
Required if
data_volume_countis greater than zero. Changing this will create a new MRS cluster resource. The following disk types are supported:SATA: common I/O diskSAS: high I/O diskSSD: ultra-high I/O disk
- host
Ips List<String> - The host list of this nodes group in the cluster.
MrsClusterV2Timeouts, MrsClusterV2TimeoutsArgs
Import
Clusters can be imported by their id. For example,
$ pulumi import flexibleengine:index/mrsClusterV2:MrsClusterV2 test b11b407c-e604-4e8d-8bc4-92398320b847
Note that the imported state may not be identical to your resource definition, due to some attrubutes missing from the
API response, security or some other reason. The missing attributes include:
manager_admin_pwd, template_id and assigned_roles.
It is generally recommended running pulumi preview after importing a cluster.
You can then decide if changes should be applied to the cluster, or the resource definition
should be updated to align with the cluster. Also you can ignore changes as below.
hcl
resource “flexibleengine_mrs_cluster_v2” “test” {
...
lifecycle {
ignore_changes = [
manager_admin_pwd,
]
}
}
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- flexibleengine flexibleenginecloud/terraform-provider-flexibleengine
- License
- Notes
- This Pulumi package is based on the
flexibleengineTerraform Provider.
flexibleengine 1.46.0 published on Monday, Apr 14, 2025 by flexibleenginecloud