[BUG]UnionForAlert test case fail

[Zhang, Edward (GDI Hadoop)]

I found TestStormRunner::UnionForAlert fail with type incompatibility, I think 
that is because Hao has refactored processing layer, but we should fix those 
unit test cases.


object UnionForAlert extends App{
  val config : Config = ConfigFactory.load;
  val env = StormExecutionEnvironment(config)
  val tail1 = 
env.fromSpout(TestSpout()).flatMap(WordPrependForAlertExecutor("test")).map2(a 
=> ("key1",a))
  val tail2 = 
env.fromSpout(TestSpout()).flatMap(WordAppendForAlertExecutor("test")).map2(a 
=> ("key2",a))
  tail1.streamUnion(List(tail2)).alert(Seq("s1","s2"), "alert1", consume = 
false)
  env.execute()
}

2015-12-28 18:19:17,940 ERROR [Thread-8-MapperProducer_9] 
storm.AbstractStreamBolt[98]: Got exception when processing source: 
WordPrependForAlertExecutor(test)_2:6, stream: default, id: {}, [key1, 
{word=test_abc}]
java.lang.ClassCastException: scala.Tuple2 cannot be cast to 
org.apache.eagle.datastream.Tuple2
at 
org.apache.eagle.datastream.UnionForAlert$$anonfun$1.apply(TestStormRunner.scala:34)
at 
org.apache.eagle.datastream.core.StreamAlertExpansion$$anonfun$1.apply(StreamAlertExpansion.scala:159)
at 
org.apache.eagle.datastream.storm.MapBoltWrapper.onValues(MapBoltWrapper.scala:56)
at 
org.apache.eagle.datastream.storm.AbstractStreamBolt.execute(AbstractStreamBolt.scala:93)
at 
backtype.storm.daemon.executor$fn__3441$tuple_action_fn__3443.invoke(executor.clj:633)
at 
backtype.storm.daemon.executor$mk_task_receiver$fn__3364.invoke(executor.clj:401)
at 
backtype.storm.disruptor$clojure_handler$reify__1447.onEvent(disruptor.clj:58)
at 
backtype.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:125)
at 
backtype.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:99)
at 
backtype.storm.disruptor$consume_batch_when_available.invoke(disruptor.clj:80)
at 
backtype.storm.daemon.executor$fn__3441$fn__3453$fn__3500.invoke(executor.clj:748)
at backtype.storm.util$async_loop$fn__464.invoke(util.clj:463)
at clojure.lang.AFn.run(AFn.java:24)
at java.lang.Thread.run(Thread.java:745)

thanks
Edward

[jira] [Commented] (EAGLE-103) add comments to readme to tell users: currently, eagle is tested under jdk1.7.x, may have compile error with jdk1.8.x

[Prasad Mujumdar (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072566#comment-15072566
 ] 

Prasad Mujumdar commented on EAGLE-103:
---

  It would be nice to add other requirements like scala,  npm and maven in the 
REAME. Typically ASF project readme would list all the required tools for 
building the project.

> add comments to readme to tell users: currently, eagle is tested under 
> jdk1.7.x, may have compile error with jdk1.8.x
> -
>
> Key: EAGLE-103
> URL: https://issues.apache.org/jira/browse/EAGLE-103
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Michael Wu
>Assignee: Hao Chen
>Priority: Minor
>
> Compilation error found while building with JDK1.8.x (refer to 
> https://issues.apache.org/jira/browse/EAGLE-101).
> I think we should update the required version of jdk in readme file of the 
> project.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: unit test fails while build incubator-eagle

[Prasad Mujumdar]

   Created EAGLE-104  to
track the issue and attached the patch. will run the tests and submit pull
request.
Are we suppose to use ReviewBoard or some other tool for code reviews ?

thanks
Prasad


On Mon, Dec 28, 2015 at 1:37 AM, Prasad Mujumdar  wrote:

>
>   Looks like the problem is that the UGI parsing method is not handling
> the simple authentication scenario where user name is not a kerberos
> principal. I can log a ticket and submit a patch if nobody else is looking
> into this.
>
> thanks
> Prasad
>
>
> On Sun, Dec 27, 2015 at 9:27 PM, Michael Wu  wrote:
>
>> Hi guys,
>>
>> While I was trying to kick off a build at
>> https://builds.apache.org/job/incubator-eagle-pr-reviewer, an exception
>> was
>> thrown out from a unit test method with the message pasted at the bottom.
>> Could anyone who is responsible for this unit test to take a look and fix
>> it, please? Otherwise it may block pull requests from getting passed for
>> CI
>> verification.
>> Error message from Unit test:
>> **
>> 
>> 
>> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>> at
>> java.lang.String.substring(String.java:1911) at
>>
>> org.apache.eagle.security.util.LogParseUtil.parseUserFromUGI(LogParseUtil.java:39)
>> at
>>
>> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parseAttr(HDFSSecurityLogParser.java:78)
>> at
>>
>> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parse(HDFSSecurityLogParser.java:52)
>> at
>>
>> org.apache.eagle.security.TestHDFSSecuritylogParser.test(TestHDFSSecuritylogParser.java:36)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606) at
>>
>> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>> at
>>
>> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>> at
>>
>> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>> at
>>
>> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at
>>
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>> at
>>
>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at
>> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at
>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at
>> org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at
>> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at
>> org.junit.runners.ParentRunner.run(ParentRunner.java:300) at
>>
>> org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)
>> at
>>
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)
>> at
>>
>> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)
>> at org.apache.maven.surefire.Surefire.run(Surefire.java:169) at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606) at
>>
>> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)
>> at
>>
>> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)
>> 
>> 
>> log4j:WARN No appenders could be found for logger
>> (org.apache.eagle.common.config.EagleConfigFactory). log4j:WARN Please
>> initialize the log4j system properly. log4j:WARN See
>> http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
>> 
>> 
>> **
>>
>> To get more detailed info about the error, please refer to
>>
>> https://builds.apache.org/job/incubator-eagle-pr-reviewer/ws/eagle-security/eagle-security-hdfs-securitylog/target/surefire-reports/
>>
>> Thanks.
>> Michael
>>
>
>

[jira] [Created] (EAGLE-104) Fix the unit test TestHDFSSecuritylogParser

[Prasad Mujumdar (JIRA)]

Prasad Mujumdar created EAGLE-104:
-

 Summary: Fix the unit test TestHDFSSecuritylogParser  
 Key: EAGLE-104
 URL: https://issues.apache.org/jira/browse/EAGLE-104
 Project: Eagle
  Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Prasad Mujumdar


The test fails with following error
{noformat}
java.lang.StringIndexOutOfBoundsException">
java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at
java.lang.String.substring(String.java:1911) at
org.apache.eagle.security.util.LogParseUtil.parseUserFromUGI(LogParseUtil.java:39)
at
org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parseAttr(HDFSSecurityLogParser.java:78)
at
org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parse(HDFSSecurityLogParser.java:52)
at
org.apache.eagle.security.TestHDFSSecuritylogParser.test(TestHDFSSecuritylogParser.java:36)
{noformat}

Looks like the problem is that the UGI parsing method is not handling the 
simple authentication scenario where user name is not a kerberos principal. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-100) provide tools to collect hadoop jmx metrics

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072579#comment-15072579
 ] 

ASF GitHub Bot commented on EAGLE-100:
--

GitHub user qingwen220 opened a pull request:

https://github.com/apache/incubator-eagle/pull/41

[EAGLE-100] Add hadoop jmx collector scripts

https://issues.apache.org/jira/browse/EAGLE-100

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-100

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/41.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #41


commit 315f555ab394c3d3e6767412323e713a2bd40334
Author: Zhao, Qingwen 
Date:   2015-12-28T10:00:29Z

add hadoop jmx collector scripts




> provide tools to collect hadoop jmx metrics
> ---
>
> Key: EAGLE-100
> URL: https://issues.apache.org/jira/browse/EAGLE-100
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Priority: Critical
>
> Provide scripts to collect Hadoop jmx metrics and evently sent these metrics 
> to stdout or Kafka.
> A user can easily run these scrips by crontab 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: [EAGLE-100] Add hadoop jmx collector...

[qingwen220]

GitHub user qingwen220 opened a pull request:

https://github.com/apache/incubator-eagle/pull/41

[EAGLE-100] Add hadoop jmx collector scripts

https://issues.apache.org/jira/browse/EAGLE-100

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-100

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/41.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #41


commit 315f555ab394c3d3e6767412323e713a2bd40334
Author: Zhao, Qingwen 
Date:   2015-12-28T10:00:29Z

add hadoop jmx collector scripts




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-61) HDFS classification supports HA and secured cluster connection

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072562#comment-15072562
 ] 

ASF GitHub Bot commented on EAGLE-61:
-

GitHub user qingwen220 opened a pull request:

https://github.com/apache/incubator-eagle/pull/40

[EAGLE-61] Supports HA and secured cluster connection on Eagle Web

https://issues.apache.org/jira/browse/EAGLE-61

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-61

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/40.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #40


commit 523c05bc6c36142f8ad438d431ba06926ba33a59
Author: Zhao, Qingwen 
Date:   2015-12-08T10:15:24Z

Enable eagle ldap authentication

commit 308d91b81e9656ca90dc2f4d63cd53c55bcbe0aa
Author: Zhao, Qingwen 
Date:   2015-12-15T08:37:49Z

Merge branch 'master' of https://github.com/apache/incubator-eagle into 
EAGLE-61

merge from master branch

commit 3270d0d8eafd2616ed548065df6c26fb46aa83f6
Author: Zhao, Qingwen 
Date:   2015-12-24T09:02:33Z

update eagle-external unit tests

commit d75bb19067ea8f4500148c31eea876efbeeb2328
Author: Zhao, Qingwen 
Date:   2015-12-26T10:01:18Z

add kerberos authentication in hdfs/hbase web

commit f75435dbd2c1348a2cc385d0a121bc4ecbc9538d
Author: Zhao, Qingwen 
Date:   2015-12-26T10:01:18Z

add kerberos authentication in hdfs/hbase web

commit 5d6184c1324a5e8acc7908272f7a3cb43667be36
Author: Zhao, Qingwen 
Date:   2015-12-26T10:46:10Z

Merge branch 'EAGLE-61' of https://github.com/qingwen220/incubator-eagle 
into EAGLE-61




> HDFS classification supports HA and secured cluster connection
> --
>
> Key: EAGLE-61
> URL: https://issues.apache.org/jira/browse/EAGLE-61
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Zhao, Qingwen
>
> 1) support HA cluster connection
> 2) support kerberos secure cluster connection



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: [EAGLE-61] Supports HA and secured c...

[qingwen220]

GitHub user qingwen220 opened a pull request:

https://github.com/apache/incubator-eagle/pull/40

[EAGLE-61] Supports HA and secured cluster connection on Eagle Web

https://issues.apache.org/jira/browse/EAGLE-61

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-61

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/40.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #40


commit 523c05bc6c36142f8ad438d431ba06926ba33a59
Author: Zhao, Qingwen 
Date:   2015-12-08T10:15:24Z

Enable eagle ldap authentication

commit 308d91b81e9656ca90dc2f4d63cd53c55bcbe0aa
Author: Zhao, Qingwen 
Date:   2015-12-15T08:37:49Z

Merge branch 'master' of https://github.com/apache/incubator-eagle into 
EAGLE-61

merge from master branch

commit 3270d0d8eafd2616ed548065df6c26fb46aa83f6
Author: Zhao, Qingwen 
Date:   2015-12-24T09:02:33Z

update eagle-external unit tests

commit d75bb19067ea8f4500148c31eea876efbeeb2328
Author: Zhao, Qingwen 
Date:   2015-12-26T10:01:18Z

add kerberos authentication in hdfs/hbase web

commit f75435dbd2c1348a2cc385d0a121bc4ecbc9538d
Author: Zhao, Qingwen 
Date:   2015-12-26T10:01:18Z

add kerberos authentication in hdfs/hbase web

commit 5d6184c1324a5e8acc7908272f7a3cb43667be36
Author: Zhao, Qingwen 
Date:   2015-12-26T10:46:10Z

Merge branch 'EAGLE-61' of https://github.com/qingwen220/incubator-eagle 
into EAGLE-61




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Requesting contributor access to Jira

[Prasad Mujumdar]

Hello,

  I would be interested in contributing to the project. Requesting
contributor access to the Jira so that I can assign tickets to myself.

thanks
Prasad

[jira] [Updated] (EAGLE-104) Fix the unit test TestHDFSSecuritylogParser

[Prasad Mujumdar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Mujumdar updated EAGLE-104:
--
Attachment: EAGLE-104.1.patch

> Fix the unit test TestHDFSSecuritylogParser  
> -
>
> Key: EAGLE-104
> URL: https://issues.apache.org/jira/browse/EAGLE-104
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Prasad Mujumdar
> Attachments: EAGLE-104.1.patch
>
>
> The test fails with following error
> {noformat}
> java.lang.StringIndexOutOfBoundsException">
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at
> java.lang.String.substring(String.java:1911) at
> org.apache.eagle.security.util.LogParseUtil.parseUserFromUGI(LogParseUtil.java:39)
> at
> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parseAttr(HDFSSecurityLogParser.java:78)
> at
> org.apache.eagle.security.securitylog.parse.HDFSSecurityLogParser.parse(HDFSSecurityLogParser.java:52)
> at
> org.apache.eagle.security.TestHDFSSecuritylogParser.test(TestHDFSSecuritylogParser.java:36)
> {noformat}
> Looks like the problem is that the UGI parsing method is not handling the 
> simple authentication scenario where user name is not a kerberos principal. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [Jenkins Plugin Required] Could you please help install "Embeddable Build Status Plugin" to the Jenkins servers?

[Andrew Bayer]

Please open INFRA JIRAs for this sort of thing.

On Monday, December 28, 2015, Michael Wu  wrote:

> Hi jenkins-admin team,
>
> I'm a contributor of incubator-eagle project and we are using
> builds.apache.org to build CI jobs for the project. Recently, an
> interesting Jenkins plugin attracted our appeals and was considered helpful
> for all CI jobs linked with github repos to set build status icon in the
> main pages, its name is "Embeddable Build Status Plugin", whose official
> WIKI page is at:
> https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin
> .
>
> Could you please help evaluate the plugin and install it on servers if
> it's worthy doing? Thanks.
>
> Michael
>

[jira] [Commented] (EAGLE-84) Create scripts for merging PRs automatically

[Michael Wu (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072834#comment-15072834
 ] 

Michael Wu commented on EAGLE-84:
-

Progress: ave opened pr #42 for review, not including unit test checking logic, 
but the script has already been a useable version.

Plan: the integration of Github & CI is under way, and I will update the script 
once I'm aware enough of the logic of checking unit test results.

> Create scripts for merging PRs automatically
> 
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as 
> good-to-merge, people are willing to merge it with scripts to go through 
> necessary steps automatically, and can form the message of final aggregated 
> commit in a unified format. To achieve this, we are attempted to create the 
> script.
> As discussed, the format of message should be like below (ignore the lines 
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Requesting contributor access to Jira

[Zhang, Edward (GDI Hadoop)]

Hi Prasad,

Added you to contributor access, thanks for being interested in that.

thanks
Edward

On 12/28/15, 1:34, "Prasad Mujumdar"  wrote:

>Hello,
>
>  I would be interested in contributing to the project. Requesting
>contributor access to the Jira so that I can assign tickets to myself.
>
>thanks
>Prasad

[jira] [Created] (EAGLE-105) add test cases for state recovery in stream join, partitions, event table etc.

[Edward Zhang (JIRA)]

Edward Zhang created EAGLE-105:
--

 Summary: add test cases for state recovery in stream join, 
partitions, event table etc.
 Key: EAGLE-105
 URL: https://issues.apache.org/jira/browse/EAGLE-105
 Project: Eagle
  Issue Type: Improvement
Reporter: Edward Zhang
Assignee: Edward Zhang
Priority: Minor


stream join, partitions, and event tables are features Eagle will use, we need 
test if fault tolerance(state store and recover) can be successful under those 
cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[PR Review Request] could any one please help review pr #45?

[Michael Wu]

Hi team,

I've just opened the PR https://github.com/apache/incubator-eagle/pull/45
for updating README.md with the CI Build Status Icon. Could any one please
help review it? Thanks.

To see the effect of this change, you can refer to
https://github.com/anyway1021/incubator-eagle/blob/add_status_to_readme/README.md,
or take a look at the screenshot of it in the attachment.

Michael

[jira] [Closed] (EAGLE-107) Build Status Icon has been enabled for our github repo, please apply it to readme.md

[Hao Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hao Chen closed EAGLE-107.
--

> Build Status Icon has been enabled for our github repo, please apply it to 
> readme.md
> 
>
> Key: EAGLE-107
> URL: https://issues.apache.org/jira/browse/EAGLE-107
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Michael Wu
>Assignee: Hao Chen
>
> As requested, the Build Status Icon is eligible for our project. We need to 
> add it to readme.md of the project.
> Status links are at:
> https://builds.apache.org/job/incubator-eagle-pr-reviewer/badge/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-107 add CI Build Status Icon u...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/45


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-106) UI use same chart component

[Jilin, Jiang (JIRA)]

Jilin, Jiang created EAGLE-106:
--

 Summary: UI use same chart component
 Key: EAGLE-106
 URL: https://issues.apache.org/jira/browse/EAGLE-106
 Project: Eagle
  Issue Type: Improvement
Reporter: Jilin, Jiang
Assignee: Jilin, Jiang
Priority: Minor


Currently chart in policy & user profile page using flot which is none-update 
more than 1 year. Some of the chart feature need addtional code effort. Replace 
it with nvd3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-106) UI use same chart component

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073446#comment-15073446
 ] 

ASF GitHub Bot commented on EAGLE-106:
--

Github user zombieJ commented on the pull request:

https://github.com/apache/incubator-eagle/pull/44#issuecomment-167711979
  
This is dev page. Add cleanup commit to remove it.


> UI use same chart component
> ---
>
> Key: EAGLE-106
> URL: https://issues.apache.org/jira/browse/EAGLE-106
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Jilin, Jiang
>Assignee: Jilin, Jiang
>Priority: Minor
>
> Currently chart in policy & user profile page using flot which is none-update 
> more than 1 year. Some of the chart feature need addtional code effort. 
> Replace it with nvd3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (EAGLE-102) ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make the status visible in Readme.md of incubator-eagle.git

[Michael Wu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/EAGLE-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Wu resolved EAGLE-102.
--
Resolution: Fixed

> ask jenkins-admin's help to setup "Embeddable Build Status Plugin" and make 
> the status visible in Readme.md of incubator-eagle.git
> --
>
> Key: EAGLE-102
> URL: https://issues.apache.org/jira/browse/EAGLE-102
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Michael Wu
>
> reference url of the plugin: 
> https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-84 create first version of aut...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/42#issuecomment-167714573
  
Please use python-2.7 instead of python-3.*


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: [EAGLE-100] Add hadoop jmx collector...

[qingwen220]

Github user qingwen220 closed the pull request at:

https://github.com/apache/incubator-eagle/pull/41


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-100) provide tools to collect hadoop jmx metrics

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073421#comment-15073421
 ] 

ASF GitHub Bot commented on EAGLE-100:
--

GitHub user qingwen220 opened a pull request:

https://github.com/apache/incubator-eagle/pull/46

EAGLE-100 Provide tools to collect hadoop jmx metrics 

https://issues.apache.org/jira/browse/EAGLE-100

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-100

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit 315f555ab394c3d3e6767412323e713a2bd40334
Author: Zhao, Qingwen 
Date:   2015-12-28T10:00:29Z

add hadoop jmx collector scripts

commit 54f5dc76643aa914c57c5c6675b4637e2d908026
Author: Zhao, Qingwen 
Date:   2015-12-29T03:20:06Z

add license

commit c76e68e66d5994d68a8e325a71a4fffe61fcb54c
Author: Zhao, Qingwen 
Date:   2015-12-29T03:25:36Z

update README




> provide tools to collect hadoop jmx metrics
> ---
>
> Key: EAGLE-100
> URL: https://issues.apache.org/jira/browse/EAGLE-100
> Project: Eagle
>  Issue Type: New Feature
>Reporter: Zhao, Qingwen
>Priority: Critical
>
> Provide scripts to collect Hadoop jmx metrics and evently sent these metrics 
> to stdout or Kafka.
> A user can easily run these scrips by crontab 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-100 Provide tools to collect h...

[qingwen220]

GitHub user qingwen220 opened a pull request:

https://github.com/apache/incubator-eagle/pull/46

EAGLE-100 Provide tools to collect hadoop jmx metrics 

https://issues.apache.org/jira/browse/EAGLE-100

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qingwen220/incubator-eagle EAGLE-100

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit 315f555ab394c3d3e6767412323e713a2bd40334
Author: Zhao, Qingwen 
Date:   2015-12-28T10:00:29Z

add hadoop jmx collector scripts

commit 54f5dc76643aa914c57c5c6675b4637e2d908026
Author: Zhao, Qingwen 
Date:   2015-12-29T03:20:06Z

add license

commit c76e68e66d5994d68a8e325a71a4fffe61fcb54c
Author: Zhao, Qingwen 
Date:   2015-12-29T03:25:36Z

update README




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: EAGLE-107 add CI Build Status Icon u...

[haoch]

Github user haoch commented on the pull request:

https://github.com/apache/incubator-eagle/pull/45#issuecomment-167711589
  
LGTM. Nice integration.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: EAGLE-78 add configuration requireme...

[qinzhaokun]

GitHub user qinzhaokun opened a pull request:

https://github.com/apache/incubator-eagle/pull/47

EAGLE-78 add configuration requirement for docker

https://issues.apache.org/jira/browse/EAGLE-78

update docker README.md 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/qinzhaokun/incubator-eagle EAGLE-78

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/47.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #47


commit 0f76d2810e2d705e82bfedab4546640c53db6223
Author: qinzhaokun 
Date:   2015-12-29T05:19:37Z

EAGLE-78 add configuration requirement for docker




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-84) Create scripts for merging PRs automatically

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073529#comment-15073529
 ] 

ASF GitHub Bot commented on EAGLE-84:
-

Github user anyway1021 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/42#issuecomment-167723365
  
Sure, Hao, that's a good suggestion and the old name was not defined as the
final one, i'll change these things and add commits to the PR.

On Tue, Dec 29, 2015 at 11:57 AM, Hao Chen  wrote:

> And how do you think rename to script to a more meaningful name say
> merge_pull_request.py instead of auto_merge.py? Because the script is
> actually executed manually but not automatically.
>
> —
> Reply to this email directly or view it on GitHub
> 
> .
>



> Create scripts for merging PRs automatically
> 
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as 
> good-to-merge, people are willing to merge it with scripts to go through 
> necessary steps automatically, and can form the message of final aggregated 
> commit in a unified format. To achieve this, we are attempted to create the 
> script.
> As discussed, the format of message should be like below (ignore the lines 
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-eagle pull request: EAGLE-84 create first version of aut...

[anyway1021]

GitHub user anyway1021 reopened a pull request:

https://github.com/apache/incubator-eagle/pull/42

EAGLE-84 create first version of auto_merge.py under folder eagle-dev

This version doesn't include the logic of checking unit test results 
reported by CI jobs. The purposes of this pull request are:
1. create sub-directory of "eagle-dev" in the project's root directory to 
contain dev related tools or scripts.
2. contribute this first version so that people can use it instead of 
manually scripting jobs to merge, edit, commit and push.
3. let this script receive widely review.

The integration of Github & CI is under way, and I will update this script 
once I'm aware enough of the verification logic for unit test results, soon.

Any code review and suggestion will be appreciated.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anyway1021/incubator-eagle 
auto_merge_python_script

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/42.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #42


commit 4f36ef15243ffc30ff30cbc893f3388ea8f27685
Author: ziwu 
Date:   2015-12-28T15:32:24Z

create first version of auto_merge.py under folder eagle-dev




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: EAGLE-84 create first version of aut...

[anyway1021]

Github user anyway1021 closed the pull request at:

https://github.com/apache/incubator-eagle/pull/42


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-eagle pull request: EAGLE-84 create first version of aut...

[anyway1021]

Github user anyway1021 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/42#issuecomment-167688948
  
This is a copy of an experimentation execution log of the script, which is 
hoped to help reviewers (git-repo-url, ticket-id are mocked, not 
apache/incubator-eagle):
 START PROCESSING 
INF: query pr information from github...
INF: will use "am_eagle_remote" as a remote name to operate
INF: looking up comments from github...
INF: verified: this pr is reviewed by ['anyway1021'] and finally approved 
by ['anyway1021'], it's good to merge
INF: querying email address for reviewers' account from github...
INF: downloading 17.patch from github...
IPT: please input the description of the merge, which will be regarded as a 
part of the final commit message
( to start new lines,  to finish inputting):
recover 
INF: committed to local repository on branch 
operating_branch_1451350746196985, the commit history now looks like: 
new ->  * commit 643dc13d5560eae734ea1e9ac166d68adf363113 (HEAD, 
operating_branch_1451350746196985)
| Author: ziwu 
| Date:   Tue Dec 29 08:59:39 2015 +0800
| 
| EAGLE-31 recover toString() of Address.java
| recover
| 
| https://issues.apache.org/jira/browse/EAGLE-31
| 
| Author: @anyway1021 
| Reviewer(s): @anyway1021 
| 
| Closes #17.
|  
old ->  * commit 2a935badad668b97de7c8e8a9150786c88fabb8d 
(am_eagle_remote/master)
| Author: ziwu 
| Date:   Mon Dec 28 22:58:14 2015 +0800
| 
| EAGLE-31 add street1 info to toString() of Address.java
| ddaabb
| 
| https://issues.apache.org/jira/browse/EAGLE-31
| 
| Author: @anyway1021 
| Reviewer(s): @anyway1021 
| 
| Closes #16.
* commit ..
IPT: shall we push commit <643dc13d5560eae734ea1e9ac166d68adf363113> to 
remote ?
():y
INF: pushing to remote repository...
INF: pull request <17> has been applied and pushed to remote 
 of repository 

INF: if you're going to continue with any forked repository, please update 
it accordingly
INF: Bye.
 ENDED PROCESSING 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-84) Create scripts for merging PRs automatically

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073294#comment-15073294
 ] 

ASF GitHub Bot commented on EAGLE-84:
-

GitHub user anyway1021 reopened a pull request:

https://github.com/apache/incubator-eagle/pull/42

EAGLE-84 create first version of auto_merge.py under folder eagle-dev

This version doesn't include the logic of checking unit test results 
reported by CI jobs. The purposes of this pull request are:
1. create sub-directory of "eagle-dev" in the project's root directory to 
contain dev related tools or scripts.
2. contribute this first version so that people can use it instead of 
manually scripting jobs to merge, edit, commit and push.
3. let this script receive widely review.

The integration of Github & CI is under way, and I will update this script 
once I'm aware enough of the verification logic for unit test results, soon.

Any code review and suggestion will be appreciated.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anyway1021/incubator-eagle 
auto_merge_python_script

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/42.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #42


commit 4f36ef15243ffc30ff30cbc893f3388ea8f27685
Author: ziwu 
Date:   2015-12-28T15:32:24Z

create first version of auto_merge.py under folder eagle-dev




> Create scripts for merging PRs automatically
> 
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as 
> good-to-merge, people are willing to merge it with scripts to go through 
> necessary steps automatically, and can form the message of final aggregated 
> commit in a unified format. To achieve this, we are attempted to create the 
> script.
> As discussed, the format of message should be like below (ignore the lines 
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-84) Create scripts for merging PRs automatically

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073331#comment-15073331
 ] 

ASF GitHub Bot commented on EAGLE-84:
-

Github user anyway1021 commented on the pull request:

https://github.com/apache/incubator-eagle/pull/42#issuecomment-167688948
  
This is a copy of an experimentation execution log of the script, which is 
hoped to help reviewers (git-repo-url, ticket-id are mocked, not 
apache/incubator-eagle):
 START PROCESSING 
INF: query pr information from github...
INF: will use "am_eagle_remote" as a remote name to operate
INF: looking up comments from github...
INF: verified: this pr is reviewed by ['anyway1021'] and finally approved 
by ['anyway1021'], it's good to merge
INF: querying email address for reviewers' account from github...
INF: downloading 17.patch from github...
IPT: please input the description of the merge, which will be regarded as a 
part of the final commit message
( to start new lines,  to finish inputting):
recover 
INF: committed to local repository on branch 
operating_branch_1451350746196985, the commit history now looks like: 
new ->  * commit 643dc13d5560eae734ea1e9ac166d68adf363113 (HEAD, 
operating_branch_1451350746196985)
| Author: ziwu 
| Date:   Tue Dec 29 08:59:39 2015 +0800
| 
| EAGLE-31 recover toString() of Address.java
| recover
| 
| https://issues.apache.org/jira/browse/EAGLE-31
| 
| Author: @anyway1021 
| Reviewer(s): @anyway1021 
| 
| Closes #17.
|  
old ->  * commit 2a935badad668b97de7c8e8a9150786c88fabb8d 
(am_eagle_remote/master)
| Author: ziwu 
| Date:   Mon Dec 28 22:58:14 2015 +0800
| 
| EAGLE-31 add street1 info to toString() of Address.java
| ddaabb
| 
| https://issues.apache.org/jira/browse/EAGLE-31
| 
| Author: @anyway1021 
| Reviewer(s): @anyway1021 
| 
| Closes #16.
* commit ..
IPT: shall we push commit <643dc13d5560eae734ea1e9ac166d68adf363113> to 
remote ?
():y
INF: pushing to remote repository...
INF: pull request <17> has been applied and pushed to remote 
 of repository 

INF: if you're going to continue with any forked repository, please update 
it accordingly
INF: Bye.
 ENDED PROCESSING 



> Create scripts for merging PRs automatically
> 
>
> Key: EAGLE-84
> URL: https://issues.apache.org/jira/browse/EAGLE-84
> Project: Eagle
>  Issue Type: Task
>Reporter: Michael Wu
>Assignee: Hao Chen
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> While a pull request gets passed the testing steps, and is verified as 
> good-to-merge, people are willing to merge it with scripts to go through 
> necessary steps automatically, and can form the message of final aggregated 
> commit in a unified format. To achieve this, we are attempted to create the 
> script.
> As discussed, the format of message should be like below (ignore the lines 
> consisted of asterisks):
> **
> EAGLE-${ticket_number} ${ticket_title}
> ${ticket_url}
> Author: ${commiter}
> Reviewer: ${reviewer}
> Closes #${pr_number} from ${do_person}
> **



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (EAGLE-108) a tool tests performace between mongodb3.0 and couchDB1.6.1

[Malie (JIRA)]

Malie created EAGLE-108:
---

 Summary:  a tool   tests performace between mongodb3.0 and 
couchDB1.6.1
 Key: EAGLE-108
 URL: https://issues.apache.org/jira/browse/EAGLE-108
 Project: Eagle
  Issue Type: Improvement
Reporter: Malie






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-108) a tool tests performace between mongodb3.0 and couchDB1.6.1

[Malie (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073545#comment-15073545
 ] 

Malie commented on EAGLE-108:
-

Hi，guys  recenly my  leader need a performance test on couchDB but  through 
google I fond so little information about couchDB  especially performance  
could you support some third-part tools
to do this test,thanks~

>  a tool   tests performace between mongodb3.0 and couchDB1.6.1
> --
>
> Key: EAGLE-108
> URL: https://issues.apache.org/jira/browse/EAGLE-108
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Malie
>  Labels: eagle
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (EAGLE-108) a tool tests performace between mongodb3.0 and couchDB1.6.1

[Su Ralph (JIRA)]

[ 
https://issues.apache.org/jira/browse/EAGLE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073607#comment-15073607
 ] 

Su Ralph commented on EAGLE-108:


I think this is not related to eagle project. By the name, it seems related to 
http://couchdb.apache.org/. 

>  a tool   tests performace between mongodb3.0 and couchDB1.6.1
> --
>
> Key: EAGLE-108
> URL: https://issues.apache.org/jira/browse/EAGLE-108
> Project: Eagle
>  Issue Type: Improvement
>Reporter: Malie
>  Labels: eagle
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [bug]eagle docker in mac

[覃兆坤]

Hi Edward:
Docker in Window ox is running well after I increased processor number
in my virtualbox. Thank you for finding this bug. Storm related port has
been mapped (8744), the hdfs related ports will be mapped soon.

Thanks

2015-12-25 15:15 GMT+08:00 覃兆坤 :

> I am very glad to hear eagle docker can be run in Mac OX. I reset VM 's
> memory (about 48G), but it still exists problem (Hive metastore stall
> error), I will continue to follow eagle docker in Windows and map more
> ports to host. Thanks, Edward.
>
> 2015-12-25 13:42 GMT+08:00 Zhang, Edward (GDI Hadoop) :
>
>> I found the reason for hanging is we should assign enough memory/cpu to vm
>> in mac OX, otherwise hadoop related processes like hbase is not able to be
>> started.
>>
>> we should suggest user assign 6G memory and >4 cpus for VM in mac ox.
>>
>> Also I would suggest we export hdfs console port, storm related port to
>> host machine.
>>
>> Anything else is very smooth!
>>
>> Thanks
>> Edward
>>
>> On 12/23/15, 22:47, "覃兆坤"  wrote:
>>
>> >In your terminal, use command: "docker exec -it sandbox bash" to go into
>> >container.
>> >
>> >2015-12-24 14:37 GMT+08:00 Zhang, Edward (GDI Hadoop) > >:
>> >
>> >> In Ambari, not all components are correctly started up, so I manually
>> >> started region server. But hive, kafka, storm may still are not live.
>> >>
>> >> But looks I can’t attach myself into docker container, so I could not
>> >>know
>> >> why it is failing starting eagle service.
>> >>
>> >> Are you able to attach to ambari container?
>> >>
>> >> On 12/23/15, 22:34, "覃兆坤"  wrote:
>> >>
>> >> >Hi:
>> >> >I am working to deploy eagle docker in Windows/Mac. I discover a
>> >> >problem in Windows. The Hive Metastore component can not start. Maybe
>> >>the
>> >> >same situation happens in Mac. Now you can access ambari UI, so can
>> you
>> >> >check whether the ambari UI shows all the components were installed
>> >> >successfully(hdfs,hbase,hive,kafka,storm). If the installation
>> >>failed
>> >> >in Hive Metastore start, I think the same problem in Windows and Mac.
>> I
>> >> >will try to follow this.
>> >> >
>> >> >Thanks
>> >> >Zhaokun
>> >> >
>> >> >2015-12-24 14:12 GMT+08:00 Chen, Hao :
>> >> >
>> >> >> I think it should because docker runtime under MacOSX/Windows is
>> >>using
>> >> >> delegate architecture but not like native LXC container under Linux
>> >>OS,
>> >> >> which may cause some problem like network/ip, etc.
>> >> >>
>> >> >> Docker Proxy Client under Windows/MacOSX  -> VirtualBox VM[Docker
>> >> >> Instances Inside VM]
>> >> >>
>> >> >> Zhaokun is helping investigate the problem.
>> >> >>
>> >> >> Thanks,
>> >> >> Hao
>> >> >>
>> >> >>
>> >> >> On 12/24/15, 1:20 PM, "Zhang, Edward (GDI Hadoop)"
>> >>
>> >> >> wrote:
>> >> >>
>> >> >> >Hi,
>> >> >> >
>> >> >> >Based on https://hub.docker.com/r/apacheeagle/sandbox/ I can’t run
>> >> >> docker well in mac, there are multiple issues:
>> >> >> >
>> >> >> >1) the 2nd docker run hangs forever in starting eagle service.
>> >> >> >
>> >> >> >2) the 1st docker run can start up ambari, and I can access ambari
>> >>UI,
>> >> >> but I can’t access other ports for example 60010 which is for hbase
>> >> >>master
>> >> >> info port
>> >> >> >
>> >> >> >Thanks
>> >> >> >Edward
>> >> >>
>> >>
>> >>
>>
>>
>