[jira] [Commented] (AMBARI-22125) Druid process fails to start with OOME on small machines with default ambari configs

2017-10-04 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-22125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16192004#comment-16192004
 ] 

Hudson commented on AMBARI-22125:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #332 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/332/])
AMBARI-22125. Better defaults for druid memory configs to avoid (nishant: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=84ae9a0b2a7ae598dc701ae13674b2ed8d83ae26])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-historical.xml
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-broker.xml


> Druid process fails to start with OOME on small machines with default ambari 
> configs
> 
>
> Key: AMBARI-22125
> URL: https://issues.apache.org/jira/browse/AMBARI-22125
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22125.patch
>
>
> Druid fails to start with ambari default configs when all the druid processes 
> are allocated on a single node. 
> stack trace - 
> {code} 
> Caused by: java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at 
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
> at 
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
> at 
> io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
> at 
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
> at 
> io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
> at 
> com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
> at 
> com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
> at 
> com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
> at 
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22125) Druid process fails to start with OOME on small machines with default ambari configs

2017-10-04 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-22125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16192000#comment-16192000
 ] 

Hudson commented on AMBARI-22125:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8207 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8207/])
AMBARI-22125. Better defaults for druid memory configs to avoid (nishant: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1da77356b0de98df51f48bedc087daf01aedbd7c])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-historical.xml
* (edit) ambari-server/src/test/python/stacks/2.6/common/test_stack_advisor.py
* (edit) 
ambari-server/src/main/resources/common-services/DRUID/0.9.2/configuration/druid-broker.xml


> Druid process fails to start with OOME on small machines with default ambari 
> configs
> 
>
> Key: AMBARI-22125
> URL: https://issues.apache.org/jira/browse/AMBARI-22125
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22125.patch
>
>
> Druid fails to start with ambari default configs when all the druid processes 
> are allocated on a single node. 
> stack trace - 
> {code} 
> Caused by: java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at 
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
> at 
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
> at 
> io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
> at 
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
> at 
> io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
> at 
> com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
> at 
> com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
> at 
> com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
> at 
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22125) Druid process fails to start with OOME on small machines with default ambari configs

2017-10-04 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-22125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191264#comment-16191264
 ] 

Hadoop QA commented on AMBARI-22125:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12890256/AMBARI-22125.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12421//console

This message is automatically generated.

> Druid process fails to start with OOME on small machines with default ambari 
> configs
> 
>
> Key: AMBARI-22125
> URL: https://issues.apache.org/jira/browse/AMBARI-22125
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-22125.patch
>
>
> Druid fails to start with ambari default configs when all the druid processes 
> are allocated on a single node. 
> stack trace - 
> {code} 
> Caused by: java.lang.OutOfMemoryError
> at sun.misc.Unsafe.allocateMemory(Native Method)
> at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
> at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
> at 
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:53)
> at 
> io.druid.offheap.OffheapBufferGenerator.get(OffheapBufferGenerator.java:29)
> at 
> io.druid.collections.DefaultBlockingPool.(DefaultBlockingPool.java:58)
> at 
> io.druid.guice.DruidProcessingModule.getMergeBufferPool(DruidProcessingModule.java:126)
> at 
> io.druid.guice.DruidProcessingModule$$FastClassByGuice$$8e266e5c.invoke()
> at 
> com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:264)
> at 
> com.google.inject.internal.ProviderMethod$Factory.provision(ProviderMethod.java:401)
> at 
> com.google.inject.internal.ProviderMethod$Factory.get(ProviderMethod.java:376)
> at 
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)