[jira] [Created] (EAGLE-463) One App type may be run as multiple instances in one site
Edward Zhang created EAGLE-463: -- Summary: One App type may be run as multiple instances in one site Key: EAGLE-463 URL: https://issues.apache.org/jira/browse/EAGLE-463 Project: Eagle Issue Type: Improvement Affects Versions: v0.5.0 Reporter: Edward Zhang Assignee: Edward Zhang Fix For: v0.5.0 Today in one site, one app type can be run only as one instance. In some scenarios, one application code can be run with multiple instances, for example to deal with different topics. One typical example is JMX metric application can be for namenode, datanode , resource manager etc. They are all the same type of applications, i.e. code logic with different configurations for example topic for data sources -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #343: clean eagle-data-process
GitHub user yonzhang opened a pull request: https://github.com/apache/incubator-eagle/pull/343 clean eagle-data-process clean unused classes in favor of new app framework You can merge this pull request into a Git repository by running: $ git pull https://github.com/yonzhang/incubator-eagle develop Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/343.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 #343 commit e58d3b71749454bb6aa8e908931f4900fb9ef23c Author: yonzhang Date: 2016-08-14T07:17:17Z clean up eagle-policy-base commit d5a1827109ba12d2e682917f7b452250ddb88eeb Author: yonzhang Date: 2016-08-14T23:53:08Z clean eagle-data-process --- 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. ---
Re: Heads up for Eagle 0.5 in develop branch
That's good. we need a new introduction/tutorial and documentation for eagle 0.5 when existing cases are ported to new arch. On Sat, Aug 13, 2016 at 8:12 AM, Edward Zhang wrote: > Hi Eagle Community, > > There are some on-going significant changes in Eagle 0.5 regarding code > structure and features. These changes happen in develop branch, so we see > many PRs recently. > > One heads up is those changes may break the existing way of you running an > Eagle application. It needs one week or so to make all applications to run > in a new way consistently. > > Those significant changes are as follows: > > 1. Alert engine is decoupled into a separate component. Before Eagle 0.5, > application uses alert engine as a java library. In Eagle 0.5, Alert engine > becomes a multi-tenant platform where data from different applications can > potentially go into one single (or multiple) storm topology to be evaluated > based on some CEP rules. Also, Alert engine will support correlation of > different streams of events by declaring multiple input streams in one > policy. > > This decoupling brings extra benefit e.g. any data in Kafka can go to alert > engine directly for alerting purposing without having to write code if the > data in Kafka is already ready for setting up rule. > > 2. Application configuration and lifecycle management. Before Eagle 0.5, > application is one storm topology which we use local configuration file to > manage, start, stop in a linux box. But Eagle in production normally > consists of many topologies which process different type of data sources. > Operational cost is very big without Eagle to manage those applications' > configuration and lifecycle. > > In Eagle 0.5, application constitutes 2 parts, i.e. managed storm topology > and web resources. Both parts need configurations and those configurations > are managed by Eagle API. By this way, operations can start/stop/status > check storm topology remotely and manage multiple sites(datacenter) in one > organization. > > Another benefit of application management is that it is very easy to > onboard a new Eagle monitoring application because processing(topology) and > web(UI/API) are both managed by Eagle platform. > > 3. More features. Besides existing security features, Eagle community has > integrated more Hadoop monitoring related features into Eagle, including > Hadoop running job, history job, Yarn queue, JMX metrics, Namenode log, GC > log, bad node check etc. > > Because of #1 and #2, Eagle platform now becomes more open and friendly to > add any new monitoring features. > > Thanks > Edward >
Re: Could you grant me the access to upload eagle's artifacts to maven repository?
Hi Jake,
Could you please help on this case? There are some required dependencies
blocked. Thanks.
Michael
On Thu, Aug 11, 2016 at 11:20 AM, Michael Wu wrote:
> Hi Jake,
>
> Tickets created:
> https://issues.apache.org/jira/browse/INFRA-12409
> https://issues.apache.org/jira/browse/INFRA-12410
>
> Thanks for helping it out.
>
> Michael
>
>
> On Tue, Aug 9, 2016 at 12:00 AM, Jake Farrell wrote:
>
>> Your user will have to get added to nexus, can you please put in an infra
>> ticket for this
>>
>> -Jake
>>
>> On Sun, Aug 7, 2016 at 11:35 PM, Michael Wu wrote:
>>
>> > Hi there,
>> >
>> > My apache account is "mw".
>> >
>> > I was trying to use
>> >
>> > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_PASSPHR
>> ASE}
>> > deploy
>> >
>> > to upload eagle's jars to https://repository.apache.org/
>> > service/local/staging/deploy/maven2, but it always returned 400 error,
>> as
>> > below fragment:
>> >
>> > [ERROR] Failed to execute goal org.apache.maven.plugins:
>> > maven-deploy-plugin:2.8.1:deploy (default-deploy) on project
>> eagle-parent:
>> > Failed to deploy artifacts: Could not transfer artifact
>> > org.apache.eagle:eagle-parent:pom:0.4.0-incubating from/to
>> > apache.releases.https (https://repository.apache.
>> > org/service/local/staging/
>> > deploy/maven2): Failed to transfer file: https://repository.apache.org/
>> > service/local/staging/deploy/maven2/org/apache/eagle/eagle-
>> > parent/0.4.0-incubating/eagle-parent-0.4.0-incubating.pom. Return code
>> is:
>> > 400, ReasonPhrase: Bad Request. -> [Help 1]
>> >
>> >
>> > Could you instruct me, whether it's caused by the lack of access to the
>> > repository and could anyone help grant me the access? Thanks.
>> >
>> > Michael
>> >
>>
>
>
Re: Could you grant me the access to upload eagle's artifacts to maven repository?
Michael,
Your best bet is to ping infra. If email doesn't work, hopping on to
hipchat with them may work.
http://www.apache.org/dev/infra-contact
John
On Sun, Aug 14, 2016 at 10:15 PM Michael Wu wrote:
> Hi Jake,
>
> Could you please help on this case? There are some required dependencies
> blocked. Thanks.
>
> Michael
>
> On Thu, Aug 11, 2016 at 11:20 AM, Michael Wu wrote:
>
> > Hi Jake,
> >
> > Tickets created:
> > https://issues.apache.org/jira/browse/INFRA-12409
> > https://issues.apache.org/jira/browse/INFRA-12410
> >
> > Thanks for helping it out.
> >
> > Michael
> >
> >
> > On Tue, Aug 9, 2016 at 12:00 AM, Jake Farrell
> wrote:
> >
> >> Your user will have to get added to nexus, can you please put in an
> infra
> >> ticket for this
> >>
> >> -Jake
> >>
> >> On Sun, Aug 7, 2016 at 11:35 PM, Michael Wu wrote:
> >>
> >> > Hi there,
> >> >
> >> > My apache account is "mw".
> >> >
> >> > I was trying to use
> >> >
> >> > $> mvn -Papache-release -DskipTests -Dgpg.passphrase=${GPG_PASSPHR
> >> ASE}
> >> > deploy
> >> >
> >> > to upload eagle's jars to https://repository.apache.org/
> >> > service/local/staging/deploy/maven2, but it always returned 400 error,
> >> as
> >> > below fragment:
> >> >
> >> > [ERROR] Failed to execute goal org.apache.maven.plugins:
> >> > maven-deploy-plugin:2.8.1:deploy (default-deploy) on project
> >> eagle-parent:
> >> > Failed to deploy artifacts: Could not transfer artifact
> >> > org.apache.eagle:eagle-parent:pom:0.4.0-incubating from/to
> >> > apache.releases.https (https://repository.apache.
> >> > org/service/local/staging/
> >> > deploy/maven2): Failed to transfer file:
> https://repository.apache.org/
> >> > service/local/staging/deploy/maven2/org/apache/eagle/eagle-
> >> > parent/0.4.0-incubating/eagle-parent-0.4.0-incubating.pom. Return code
> >> is:
> >> > 400, ReasonPhrase: Bad Request. -> [Help 1]
> >> >
> >> >
> >> > Could you instruct me, whether it's caused by the lack of access to
> the
> >> > repository and could anyone help grant me the access? Thanks.
> >> >
> >> > Michael
> >> >
> >>
> >
> >
>
[GitHub] incubator-eagle pull request #344: EAGLE-421: JMX Metric APP use new applica...
GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/344 EAGLE-421: JMX Metric APP use new application framework Remove the topology code since JMX app could be done in new alert engine directly. You can merge this pull request into a Git repository by running: $ git pull https://github.com/RalphSu/incubator-eagle develop Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/344.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 #344 commit 1517c132658408952e790e27565496b9587da06b Author: Ralph, Su Date: 2016-08-15T03:28:56Z EAGLE-421: JMX Metric APP use new application framework Remove the topology code since JMX app could be done in new alert engine directly. --- 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-421) JMX Metric APP use new application framework
[ https://issues.apache.org/jira/browse/EAGLE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420583#comment-15420583 ] ASF GitHub Bot commented on EAGLE-421: -- GitHub user RalphSu opened a pull request: https://github.com/apache/incubator-eagle/pull/344 EAGLE-421: JMX Metric APP use new application framework Remove the topology code since JMX app could be done in new alert engine directly. You can merge this pull request into a Git repository by running: $ git pull https://github.com/RalphSu/incubator-eagle develop Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/344.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 #344 commit 1517c132658408952e790e27565496b9587da06b Author: Ralph, Su Date: 2016-08-15T03:28:56Z EAGLE-421: JMX Metric APP use new application framework Remove the topology code since JMX app could be done in new alert engine directly. > JMX Metric APP use new application framework > > > Key: EAGLE-421 > URL: https://issues.apache.org/jira/browse/EAGLE-421 > Project: Eagle > Issue Type: Bug >Affects Versions: v0.5.0 >Reporter: Su Ralph >Assignee: Su Ralph > Fix For: v0.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-464) StateCheck: multiple stage of definition in single policy
Su Ralph created EAGLE-464: -- Summary: StateCheck: multiple stage of definition in single policy Key: EAGLE-464 URL: https://issues.apache.org/jira/browse/EAGLE-464 Project: Eagle Issue Type: New Feature Affects Versions: v0.5.0 Reporter: Su Ralph Assignee: Su Ralph Fix For: v0.5.0 The requirement of alert state and transition comes from two real customer needs. Alert de-duplication "IMO, eagle should do state checks for all services. Eagle should not alert in the first attempt itself. Instead it should change the state to SOFT for 2 tries and then if it is the same state, change the state to HARD and then send the alert." - Aroop Currently, eagle's alert engine(and also that of UMP) use a simple deduplication spec of time based redundancy check(dedupIntervalMin of Publishment). This deduplication is not flexible to reflect the need of alerts. There are common requests like to hold a alert/policy state (basically a alert state is policy state on given partition value, more in latter), and trigger alert when the state changed. This state change manner could be > Same alert trigger again in M time interval > N alerts in given M time interval. NOTE: on here, in this de-duplication mode, there is no required change of the policy itself. Alert policy define on transition One example of the missingblock policy we met(only alert when missingblock number changes). There is more general case with minor difference, given a metric (or a field of a given stream), define value range, where each range indicate different state. Etc. for perfmon.latency.avg.perpool, define value range state as metric value range state alert trigger perfmon.latency.avg.perpool.5min3000 - UnlimitedFATAL always (every 5min until FATAL fixed or alert muted explictly) 1000 - 3000 CRITICALon dual transition 100 - 1000 WARNon dual transition 10 - 50 NORMAL on worse transition 0-10GOODon worse transition Then the alert should be trigger during the state changed expect for FATAL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #345: EAGLE-411 Refactor hbase related unit tes...
GitHub user chitin opened a pull request: https://github.com/apache/incubator-eagle/pull/345 EAGLE-411 Refactor hbase related unit test cases with mockito and min⦠- Delete "zookeeper.znode.parent" and "hbase.master.ipc.address" in HbaseTestingUtility configuration. - Support the Hbase UT which based the class to pass in meanful time https://issues.apache.org/jira/browse/EAGLE-411 You can merge this pull request into a Git repository by running: $ git pull https://github.com/chitin/incubator-eagle hbasetest-EAGLE411 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/345.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 #345 commit 7ba676a117c03c39d0bd1db759574a53a07eb06e Author: chitin Date: 2016-08-15T03:31:42Z EAGLE-411 Refactor hbase related unit test cases with mockito and mini-hbase -Delete "zookeeper.znode.parent" and "hbase.master.ipc.address" in HbaseTestingUtility configuration. -Support the Hbase UT which based the class to pass in meanful time https://issues.apache.org/jira/browse/EAGLE-411 --- 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-411) Refactor hbase related unit test cases with mockito and mini-hbase
[ https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420587#comment-15420587 ] ASF GitHub Bot commented on EAGLE-411: -- GitHub user chitin opened a pull request: https://github.com/apache/incubator-eagle/pull/345 EAGLE-411 Refactor hbase related unit test cases with mockito and min… - Delete "zookeeper.znode.parent" and "hbase.master.ipc.address" in HbaseTestingUtility configuration. - Support the Hbase UT which based the class to pass in meanful time https://issues.apache.org/jira/browse/EAGLE-411 You can merge this pull request into a Git repository by running: $ git pull https://github.com/chitin/incubator-eagle hbasetest-EAGLE411 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-eagle/pull/345.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 #345 commit 7ba676a117c03c39d0bd1db759574a53a07eb06e Author: chitin Date: 2016-08-15T03:31:42Z EAGLE-411 Refactor hbase related unit test cases with mockito and mini-hbase -Delete "zookeeper.znode.parent" and "hbase.master.ipc.address" in HbaseTestingUtility configuration. -Support the Hbase UT which based the class to pass in meanful time https://issues.apache.org/jira/browse/EAGLE-411 > Refactor hbase related unit test cases with mockito and mini-hbase > -- > > Key: EAGLE-411 > URL: https://issues.apache.org/jira/browse/EAGLE-411 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0, v0.4.0 >Reporter: Hao Chen >Assignee: Chang chen > Labels: unit-test > Fix For: v0.5.0 > > > Current implementation is really not stable which cause unit test like > TestHBaseLogReader2 unable to pass in meanful time, we need a better version. > https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-embed/eagle-embed-hbase/src/main/java/org/apache/eagle/service/hbase/EmbeddedHbase.java > http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #345: EAGLE-411 Refactor hbase related unit tes...
Github user chitin closed the pull request at: https://github.com/apache/incubator-eagle/pull/345 --- 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-411) Refactor hbase related unit test cases with mockito and mini-hbase
[ https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420592#comment-15420592 ] ASF GitHub Bot commented on EAGLE-411: -- Github user chitin closed the pull request at: https://github.com/apache/incubator-eagle/pull/345 > Refactor hbase related unit test cases with mockito and mini-hbase > -- > > Key: EAGLE-411 > URL: https://issues.apache.org/jira/browse/EAGLE-411 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0, v0.4.0 >Reporter: Hao Chen >Assignee: Chang chen > Labels: unit-test > Fix For: v0.5.0 > > > Current implementation is really not stable which cause unit test like > TestHBaseLogReader2 unable to pass in meanful time, we need a better version. > https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-embed/eagle-embed-hbase/src/main/java/org/apache/eagle/service/hbase/EmbeddedHbase.java > http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #343: clean eagle-data-process
Github user yonzhang commented on the issue: https://github.com/apache/incubator-eagle/pull/343 merged --- 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 #343: clean eagle-data-process
Github user yonzhang closed the pull request at: https://github.com/apache/incubator-eagle/pull/343 --- 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 issue #345: EAGLE-411 Refactor hbase related unit test cases...
Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/345 Thanks for the contribution, could you please make sure the changes could make other test cases using `EmbeddedHbase ` able to pass? --- 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-411) Refactor hbase related unit test cases with mockito and mini-hbase
[ https://issues.apache.org/jira/browse/EAGLE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420606#comment-15420606 ] ASF GitHub Bot commented on EAGLE-411: -- Github user haoch commented on the issue: https://github.com/apache/incubator-eagle/pull/345 Thanks for the contribution, could you please make sure the changes could make other test cases using `EmbeddedHbase ` able to pass? > Refactor hbase related unit test cases with mockito and mini-hbase > -- > > Key: EAGLE-411 > URL: https://issues.apache.org/jira/browse/EAGLE-411 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.3.0, v0.4.0 >Reporter: Hao Chen >Assignee: Chang chen > Labels: unit-test > Fix For: v0.5.0 > > > Current implementation is really not stable which cause unit test like > TestHBaseLogReader2 unable to pass in meanful time, we need a better version. > https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-embed/eagle-embed-hbase/src/main/java/org/apache/eagle/service/hbase/EmbeddedHbase.java > http://blog.cloudera.com/blog/2013/09/how-to-test-hbase-applications-using-popular-tools/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle pull request #322: [EAGLE-435] make coordiantor schedule ope...
Github user garrettlish closed the pull request at: https://github.com/apache/incubator-eagle/pull/322 --- 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-435) Coordiantor schedule operation must be exclusive in distributed deployment
[ https://issues.apache.org/jira/browse/EAGLE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420607#comment-15420607 ] ASF GitHub Bot commented on EAGLE-435: -- Github user garrettlish closed the pull request at: https://github.com/apache/incubator-eagle/pull/322 > Coordiantor schedule operation must be exclusive in distributed deployment > -- > > Key: EAGLE-435 > URL: https://issues.apache.org/jira/browse/EAGLE-435 > Project: Eagle > Issue Type: Improvement >Affects Versions: v0.5.0 >Reporter: Garrett Li >Assignee: Garrett Li > Labels: alert_engine > Fix For: v0.5.0 > > Original Estimate: 24h > Remaining Estimate: 24h > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-eagle issue #213: EAGLE-135 Run Eagle on Spark Streaming
Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/213 Branch-0.4 already released. And we have major change in v0.5. Looks this PR deprecated to me. Can we abandon and close this one? @yonzhang @haoch --- 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-135) Run Eagle in Spark Streaming
[ https://issues.apache.org/jira/browse/EAGLE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420611#comment-15420611 ] ASF GitHub Bot commented on EAGLE-135: -- Github user RalphSu commented on the issue: https://github.com/apache/incubator-eagle/pull/213 Branch-0.4 already released. And we have major change in v0.5. Looks this PR deprecated to me. Can we abandon and close this one? @yonzhang @haoch > Run Eagle in Spark Streaming > > > Key: EAGLE-135 > URL: https://issues.apache.org/jira/browse/EAGLE-135 > Project: Eagle > Issue Type: New Feature >Reporter: Zhaokun Qin >Assignee: Zhaokun Qin >Priority: Minor > Labels: new > > Eagle can run in Storm for now, to achieve Cross-platform feature, Eagle must > run in other streaming process platforms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-465) Hive security monitoring refactor
wujinhu created EAGLE-465: - Summary: Hive security monitoring refactor Key: EAGLE-465 URL: https://issues.apache.org/jira/browse/EAGLE-465 Project: Eagle Issue Type: Improvement Reporter: wujinhu Assignee: wujinhu -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EAGLE-466) TestSerDeserPer failed with Windows Git bash
Zhao, Qingwen created EAGLE-466:
---
Summary: TestSerDeserPer failed with Windows Git bash
Key: EAGLE-466
URL: https://issues.apache.org/jira/browse/EAGLE-466
Project: Eagle
Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Zhao, Qingwen
Assignee: Zhao, Qingwen
Fix For: v0.5.0
{code}
java.io.FileNotFoundException: \tmp\file2.bin (The system cannot find the path
specified)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:101)
at
org.apache.eagle.alert.engine.perf.TestSerDeserPer.testSerDeserPerf2(TestSerDeserPer.java:91)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:253)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
