<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Cloudbreak autoscaling doesn't work in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233123#M79894</link>
    <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/48272/mmolnar.html" nodeid="48272"&gt;@mmolnar&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;The error message changed as attached. It indicates the error is because of the unrecognized field "type", however, I have no idea how to fix it unfortunately.&lt;/P&gt;&lt;P&gt;I'm wondering if it's a bug of v2.7.0 because the error doesn't occur when I do the same thing on v2.4.0&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Mai Nakagawa&lt;/P&gt;</description>
    <pubDate>Wed, 27 Jun 2018 07:51:35 GMT</pubDate>
    <dc:creator>nakagawa_mai</dc:creator>
    <dc:date>2018-06-27T07:51:35Z</dc:date>
    <item>
      <title>Cloudbreak autoscaling doesn't work</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233119#M79890</link>
      <description>&lt;P&gt;I launched a Cloudbreak Deployer v2.7.0 (latest) on AWS following the instruction: &lt;A href="https://docs.hortonworks.com/HDPDocuments/Cloudbreak/Cloudbreak-2.4.1/content/aws-launch/index.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/Cloudbreak/Cloudbreak-2.4.1/content/aws-launch/index.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I created a cluster and tested the autoscaling functionality, however, it always failed with the following error found by `cbd logs-tail periscope` command:&lt;/P&gt;&lt;PRE&gt;periscope_1    | 2018-06-26 03:02:30,040 [getThreadPoolExecutorFactoryBean-36] createAmbariClient:44 INFO  c.s.p.s.AmbariClientProvider - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] Create Ambari client to connect to 172.31.47.29:9443
periscope_1    | 2018-06-26 03:02:30,050 [getThreadPoolExecutorFactoryBean-36] run:60 INFO  c.s.p.m.e.MetricEvaluator - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] Checking metric based alert: 'disk-usage'
periscope_1    | 2018-06-26 03:02:30,051 [getThreadPoolExecutorFactoryBean-36] getRawResource:84 INFO  c.s.a.c.AmbariClientUtils - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] AmbariClient getRawResource, resourceRequestMap: {path=https://172.31.47.29:9443/api/v1/clusters, query={fields=Clusters}}
periscope_1    | 2018-06-26 03:02:30,069 [getThreadPoolExecutorFactoryBean-36] getRawResource:84 INFO  c.s.a.c.AmbariClientUtils - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] AmbariClient getRawResource, resourceRequestMap: {path=https://172.31.47.29:9443/api/v1/clusters/aisin-storm/alert_history, query={AlertHistory/definition_name=ambari_agent_disk_usage}}
periscope_1    | 2018-06-26 03:02:30,084 [getThreadPoolExecutorFactoryBean-36] getRawResource:84 INFO  c.s.a.c.AmbariClientUtils - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] AmbariClient getRawResource, resourceRequestMap: {path=https://172.31.47.29:9443/api/v1/clusters/aisin-storm/alert_history/28}
periscope_1    | 2018-06-26 03:02:30,097 [getThreadPoolExecutorFactoryBean-36] run:72 INFO  c.s.p.m.e.MetricEvaluator - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] Alert: disk-usage is in 'CRITICAL' state since 5.22 min(s)
periscope_1    | 2018-06-26 03:02:30,103 [getThreadPoolExecutorFactoryBean-36] createAmbariClient:44 INFO  c.s.p.s.AmbariClientProvider - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] Create Ambari client to connect to 172.31.47.29:9443
periscope_1    | 2018-06-26 03:02:30,107 [getThreadPoolExecutorFactoryBean-36] getRawResource:84 INFO  c.s.a.c.AmbariClientUtils - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] AmbariClient getRawResource, resourceRequestMap: {path=https://172.31.47.29:9443/api/v1/clusters, query={fields=Clusters}}
periscope_1    | 2018-06-26 03:02:30,130 [getThreadPoolExecutorFactoryBean-36] getRawResource:84 INFO  c.s.a.c.AmbariClientUtils - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] AmbariClient getRawResource, resourceRequestMap: {path=https://172.31.47.29:9443/api/v1/clusters/aisin-storm}
periscope_1    | 2018-06-26 03:02:30,249 [getThreadPoolExecutorFactoryBean-43] scaleUp:76 INFO  c.s.p.m.h.ScalingRequest - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] Sending request to add 1 instance(s) into host group 'supervisor', triggered policy 'scale-out'
periscope_1    | 2018-06-26 03:02:30,313 [getThreadPoolExecutorFactoryBean-43] logExceptions:127 WARN  o.h.e.j.s.SqlExceptionHelper - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] SQL Error: 0, SQLState: 22001
periscope_1    | 2018-06-26 03:02:30,313 [getThreadPoolExecutorFactoryBean-43] logExceptions:127 WARN  o.h.e.j.s.SqlExceptionHelper - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] SQL Error: 0, SQLState: 22001
periscope_1    | 2018-06-26 03:02:30,314 [getThreadPoolExecutorFactoryBean-43] logExceptions:129 ERROR o.h.e.j.s.SqlExceptionHelper - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] ERROR: value too long for type character varying(255)
periscope_1    | 2018-06-26 03:02:30,314 [getThreadPoolExecutorFactoryBean-43] logExceptions:129 ERROR o.h.e.j.s.SqlExceptionHelper - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] ERROR: value too long for type character varying(255)
periscope_1    | 2018-06-26 03:02:30,314 [getThreadPoolExecutorFactoryBean-43] release:193 INFO  o.h.e.j.b.i.AbstractBatchImpl - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] HHH000010: On release of batch it still contained JDBC statements
periscope_1    | 2018-06-26 03:02:30,314 [getThreadPoolExecutorFactoryBean-43] release:193 INFO  o.h.e.j.b.i.AbstractBatchImpl - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] HHH000010: On release of batch it still contained JDBC statements
periscope_1    | 2018-06-26 03:02:30,315 [getThreadPoolExecutorFactoryBean-43] run:65 ERROR c.s.p.m.h.ScalingRequest - [owner:11d6ae4f-8de0-446e-83d9-1b3492185d6b] [id:3] [cb-stack-id:3] Cannot retrieve an oauth token from the identity server
periscope_1    | org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; nested exception is org.hibernate.exception.DataException: could not execute statement
periscope_1    | 	at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:282)
periscope_1    | 	at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:244)
periscope_1    | 	at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:521)
periscope_1    | 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
periscope_1    | 	at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
periscope_1    | 	at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:504)
periscope_1    | 	at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:292)
periscope_1    | 	at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
periscope_1    | 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
periscope_1    | 	at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:136)
periscope_1    | 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
periscope_1    | 	at org.springframework.data.jpa.repository.support.CrudMethodMetadataPostProcessor$CrudMethodMetadataPopulatingMethodInterceptor.invoke(CrudMethodMetadataPostProcessor.java:133)
periscope_1    | 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
periscope_1    | 	at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
periscope_1    | 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
periscope_1    | 	at org.springframework.data.repository.core.support.SurroundingTransactionDetectorMethodInterceptor.invoke(SurroundingTransactionDetectorMethodInterceptor.java:57)
periscope_1    | 	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
periscope_1    | 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
periscope_1    | 	at com.sun.proxy.$Proxy188.save(Unknown Source)
periscope_1    | 	at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source)
periscope_1    | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
periscope_1    | 	at java.lang.reflect.Method.invoke(Method.java:498)
periscope_1    | 	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333)
periscope_1    | 	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
periscope_1    | 	at com.sun.proxy.$Proxy189.save(Unknown Source)
periscope_1    | 	at com.sequenceiq.periscope.service.HistoryService.createEntry(HistoryService.java:28)
periscope_1    | 	at com.sequenceiq.periscope.monitor.handler.ScalingRequest.scaleUp(ScalingRequest.java:88)
periscope_1    | 	at com.sequenceiq.periscope.monitor.handler.ScalingRequest.run(ScalingRequest.java:60)
periscope_1    | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
periscope_1    | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
periscope_1    | 	at java.lang.Thread.run(Thread.java:748)
periscope_1    | Caused by: org.hibernate.exception.DataException: could not execute statement
periscope_1    | 	at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:118)
periscope_1    | 	at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:42)
periscope_1    | 	at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:109)
periscope_1    | 	at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:95)
periscope_1    | 	at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:207)
periscope_1    | 	at org.hibernate.engine.jdbc.batch.internal.NonBatchingBatch.addToBatch(NonBatchingBatch.java:45)
periscope_1    | 	at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2949)
periscope_1    | 	at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3449)
periscope_1    | 	at org.hibernate.action.internal.EntityInsertAction.execute(EntityInsertAction.java:89)
periscope_1    | 	at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:582)
periscope_1    | 	at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:456)
periscope_1    | 	at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:337)
periscope_1    | 	at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:39)
periscope_1    | 	at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1282)
periscope_1    | 	at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:465)
periscope_1    | 	at org.hibernate.internal.SessionImpl.flushBeforeTransactionCompletion(SessionImpl.java:2963)
periscope_1    | 	at org.hibernate.internal.SessionImpl.beforeTransactionCompletion(SessionImpl.java:2339)
periscope_1    | 	at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.beforeTransactionCompletion(JdbcCoordinatorImpl.java:485)
periscope_1    | 	at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.beforeCompletionCallback(JdbcResourceLocalTransactionCoordinatorImpl.java:147)
periscope_1    | 	at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl.access$100(JdbcResourceLocalTransactionCoordinatorImpl.java:38)
periscope_1    | 	at org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl$TransactionDriverControlImpl.commit(JdbcResourceLocalTransactionCoordinatorImpl.java:231)
periscope_1    | 	at org.hibernate.engine.transaction.internal.TransactionImpl.commit(TransactionImpl.java:65)
periscope_1    | 	at org.hibernate.jpa.internal.TransactionImpl.commit(TransactionImpl.java:61)
periscope_1    | 	at org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:517)
periscope_1    | 	... 28 common frames omitted
periscope_1    | Caused by: org.postgresql.util.PSQLException: ERROR: value too long for type character varying(255)
periscope_1    | 	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455)
periscope_1    | 	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155)
periscope_1    | 	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288)
periscope_1    | 	at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430)
periscope_1    | 	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356)
periscope_1    | 	at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:168)
periscope_1    | 	at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:135)
periscope_1    | 	at com.zaxxer.hikari.proxy.PreparedStatementProxy.executeUpdate(PreparedStatementProxy.java:61)
periscope_1    | 	at com.zaxxer.hikari.proxy.HikariPreparedStatementProxy.executeUpdate(HikariPreparedStatementProxy.java)
periscope_1    | 	at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:204)
periscope_1    | 	... 47 common frames omitted
periscope_1    | 2018-06-26 03:02:31,236 [Timer-1] collectStackDetails:49 INFO  c.s.p.s.StackCollectorService - [owner:spring] [id:] [cb-stack-id:] Evaluate cluster management for stack: aisin-storm (ID:3)
periscope_1    | 2018-06-26 03:02:31,260 [getThreadPoolExecutorFactoryBean-35] createAmbariClient:44 INFO  c.s.p.s.AmbariClientProvider - [owner:periscope] [id:] [cb-stack-id:] Create Ambari client to connect to 172.31.47.29:9443&amp;lt;br&amp;gt;&lt;/PRE&gt;&lt;P&gt;Looks like Cloudbreak Deployer failed to add or update a record in PostgreSQL because a value to add is too long for the type character varying(255), according to the error log above. However, I have no idea what value it is and how to make it shorter.&lt;/P&gt;&lt;P&gt;Could you please help me how to resolve the problem? Thank you in advance.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jun 2018 10:41:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233119#M79890</guid>
      <dc:creator>nakagawa_mai</dc:creator>
      <dc:date>2018-06-26T10:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak autoscaling doesn't work</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233120#M79891</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/52169/nakagawamai.html" nodeid="52169"&gt;@Mai Nakagawa&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;It looks like we have some logging issue here, so I can't see the real reason. Could you attach please the Cloudbreak  log file from the same time? You can find the file under your deployment directory in the logs subfolder.&lt;/P&gt;&lt;P&gt;In the meanwhile we will work on fixing the logging issue.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jun 2018 16:09:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233120#M79891</guid>
      <dc:creator>mmolnar</dc:creator>
      <dc:date>2018-06-26T16:09:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak autoscaling doesn't work</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233121#M79892</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/48272/mmolnar.html" nodeid="48272"&gt;@mmolnar&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;Thank you for your quick response. Attached please find the files in the logs subfolder of my deployment directory.&lt;/P&gt;&lt;P&gt;Please note that &lt;A href="https://community.cloudera.com/legacyfs/online/attachments/77823-logs-1.tar.gz"&gt;logs-1.tar.gz&lt;/A&gt; contains files under&lt;EM&gt; logs/autoscale&lt;/EM&gt; and &lt;EM&gt;logs/cloudbreak directories&lt;/EM&gt; and that &lt;A href="https://community.cloudera.com/legacyfs/online/attachments/77824-logs-2.tar.gz"&gt;logs-2.tar.gz&lt;/A&gt; contains the other files under &lt;EM&gt;logs&lt;/EM&gt; directory. Also, please be noted that the both files are actually .tar.bz2 - this is in order to make the size smaller than the limitation (512 kB). I used .tar.gz extension just because the website doesn't allow .tar.bz2 extension for attachments. &lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Mai Nakagawa&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jun 2018 21:13:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233121#M79892</guid>
      <dc:creator>nakagawa_mai</dc:creator>
      <dc:date>2018-06-26T21:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak autoscaling doesn't work</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233122#M79893</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/52169/nakagawamai.html" nodeid="52169"&gt;@Mai Nakagawa&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;I could not find the cause of you issue in the logs, but I have a build which have the logging issue solved hopefully. If it is a test environment you have, you can check out the new periscope to see the real error.&lt;/P&gt;&lt;P&gt;To have the new version please add the following line to you Profile under deployment directory:&lt;/P&gt;&lt;PRE&gt;export DOCKER_TAG_PERISCOPE=2.7.1-rc.11&lt;/PRE&gt;&lt;P&gt;And after it you have to issue the &lt;/P&gt;&lt;PRE&gt;cbd restart&lt;/PRE&gt;&lt;P&gt;command. This will terminate cloudbreak, regenerate the docker-compose.yml with the new version of periscope, then start cloudbreak again.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jun 2018 22:00:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233122#M79893</guid>
      <dc:creator>mmolnar</dc:creator>
      <dc:date>2018-06-26T22:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak autoscaling doesn't work</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233123#M79894</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/48272/mmolnar.html" nodeid="48272"&gt;@mmolnar&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;The error message changed as attached. It indicates the error is because of the unrecognized field "type", however, I have no idea how to fix it unfortunately.&lt;/P&gt;&lt;P&gt;I'm wondering if it's a bug of v2.7.0 because the error doesn't occur when I do the same thing on v2.4.0&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Mai Nakagawa&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jun 2018 07:51:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233123#M79894</guid>
      <dc:creator>nakagawa_mai</dc:creator>
      <dc:date>2018-06-27T07:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak autoscaling doesn't work</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233124#M79895</link>
      <description>&lt;P&gt;
	Hi &lt;A rel="user" href="https://community.cloudera.com/users/52169/nakagawamai.html" nodeid="52169"&gt;@Mai Nakagawa&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;
	yes, it's a bug in 2.7.0 but we managed to create the fix, but we are not ready yet to release 2.7.1&lt;BR /&gt;
	If you would like to use the fix, please update the DOCKER_TAG_PERISCOPE variable to 2.7.1-rc.13&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jun 2018 21:48:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-autoscaling-doesn-t-work/m-p/233124#M79895</guid>
      <dc:creator>mmolnar</dc:creator>
      <dc:date>2018-06-27T21:48:35Z</dc:date>
    </item>
  </channel>
</rss>

