简体   繁体   English

AWS EMR 集群 - 扩展没有将 dfs.replication 值从 1 更新为 2

[英]AWS EMR cluster - scale up didn't update dfs.replication value from 1 to 2

I provisioned an AWS EMR HBASE cluster with 1 master and 1 core node (m5.xLarge).我配置了一个AWS EMR HBASE集群,其中包含1 master节点和1 core node (m5.xLarge)。 My cluster doesn't have any 'task' node as I plan to use this cluster only for storage.我的集群没有任何“任务”节点,因为我计划仅将此集群用于存储。 The hdfs-site.xml file on both boxes had dfs.replication set to 1 which makes sense.两个盒子上的hdfs-site.xml文件都将dfs.replication设置为 1,这是有道理的。 I then manually added 5 more core nodes.然后我手动添加了 5 个core节点。 I was hoping EMR would bump the replication factor from 1 to 2 as per their docs - https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hdfs-config.html我希望 EMR 会根据他们的文档将复制因子从 1 提高到 2 - https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-hdfs-config.html

As I understand, EMR will set the replication factor to 2 if I supply 6 cores during bootstrap, but what about in my use case where I manually scaled the cluster up after I was up and running?据我所知,如果我在引导期间提供 6 个内核,EMR 会将复制因子设置为 2,但是在我的用例中,我在启动并运行后手动扩展集群时呢?

Looks like EMR won't do it automatically.看起来 EMR 不会自动执行。 After scaling cluster up, I will need to reconfigure the replication factor by manually reconfiguring the instance group - https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-configure-apps-running-cluster.html扩展集群后,我需要通过手动重新配置实例组来重新配置复制因子 - https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-configure-apps-running-cluster.html

--instanceGroups.json below --instanceGroups.json 下面

 [
  {
  "InstanceGroupId":"<ig-1xxxxxxx9>",
  "Configurations":[
     {
        "Classification":"yarn-site",
        "Properties":{
           "yarn.nodemanager.disk-health-checker.enable":"true",
           "yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage":"100.0"
        },
        "Configurations":[]
     }
  ]
 }
]
aws emr modify-instance-groups --cluster-id <j-2AL4XXXXXX5T9> 
--instance-groups file://instanceGroups.json

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 rds.logical_replication 在极光无服务器 AWS 上没有更改为 1 - rds.logical_replication didn't change to 1 on aurora serverless AWS 为什么 EMR Notebook 在以 AWS 账户所有者身份运行时无法连接到其集群 - Why can't EMR Notebook can't connect to its cluster when running as the AWS account owner Kube.netes autoscaler - NotTriggerScaleUp' pod 没有触发扩展(如果添加新节点则不适合) - Kubernetes autoscaler - NotTriggerScaleUp' pod didn't trigger scale-up (it wouldn't fit if a new node is added) AWS EMR:主节点是否在EMR集群中存储hdfs数据? - AWS EMR: Does master node stores hdfs data in EMR cluster? AWS EMR jupyter 错误 403 Forbidden (Workspace is not attached to cluster) - AWS EMR jupyter error 403 Forbidden (Workspace is not attached to cluster) Terraform AWS EMR HBase 集群创建 - 应用程序配置超时 - Terraform AWS EMR HBase cluster creation - application provisioning timed out 如何从正在运行的集群获取 EMR 集群版本 - how to get EMR cluster version from a running cluster AWS EMR 步骤找不到从 s3 导入的 jar - AWS EMR step doesn't find jar imported from s3 如果值未更改,Firestore 文档更新请求是否会运行? - Does Firestore document update request run if the value didn't change? 如何在 EMR 集群 AWS 中使用 java runtime 11 - How to use java runtime 11 in EMR cluster AWS
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM