https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146381#M108948 <P>Is there any way I could be informed when this bug is solved? Some kind of newsletter or release notes I can subscribe to?</P> Mon, 25 Jul 2016 18:34:14 GMT yaron_idan 2016-07-25T18:34:14Z https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146379#M108946 <P>I have an HDP cluster, and I am trying to scale down some of it's nodes using cloudbreak. The specific group in question was created with 1 node, scaled up to 4 nodes, and now when I try to scale down I manage to scale the group down to 3 nodes but anything smaller than that gives me the following error - </P><P>`7/25/2016 1:35:07 PM horton-cluster-multi-roles - update failed: New node(s) could not be removed to the cluster. Reason There is not enough node to downscale. Check the replication factor and the ApplicationMaster occupation.`</P><P>The group host contains only the following components - node_manager, metrics_monitor. So I don't understand how replication factor is a consideration for these nodes.</P> Mon, 25 Jul 2016 17:57:38 GMT https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146379#M108946 yaron_idan 2016-07-25T17:57:38Z https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146380#M108947 <P>The default replication factor is 3 so we don't allow scaling a host group below 3. It's a known, bug that we don't consider the services installed on those hosts as in your case it does not affect the replication. It will be fixed in the following versions.</P> Mon, 25 Jul 2016 18:01:52 GMT https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146380#M108947 Krisz 2016-07-25T18:01:52Z https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146381#M108948 <P>Is there any way I could be informed when this bug is solved? Some kind of newsletter or release notes I can subscribe to?</P> Mon, 25 Jul 2016 18:34:14 GMT https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146381#M108948 yaron_idan 2016-07-25T18:34:14Z https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146382#M108949 <P>You can click watch this jira on the associated page. You need to find out the name of the Jira.</P> Mon, 25 Jul 2016 19:06:31 GMT https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146382#M108949 aervits 2016-07-25T19:06:31Z https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146383#M108950 <P>Cloudbreak is not an Apache project, yet so it's an internal JIRA, but I'll update this thread.</P> Mon, 25 Jul 2016 19:15:47 GMT https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146383#M108950 Krisz 2016-07-25T19:15:47Z https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146384#M108951 <P>The fix went in to the rc-1.4 branch so the next release will solve this problem: <A href="https://github.com/sequenceiq/cloudbreak/pull/1814" target="_blank">https://github.com/sequenceiq/cloudbreak/pull/1814</A></P> Tue, 26 Jul 2016 20:46:01 GMT https://community.cloudera.com/t5/Support-Questions/Unable-to-scale-down-nodes-due-to-replication-factor/m-p/146384#M108951 Krisz 2016-07-26T20:46:01Z