[GitHub] storm issue #1736: STORM-1446 [Storm SQL] Compile the Calcite logical plan t...

2016-10-26 Thread HeartSaVioR 
Github user HeartSaVioR commented on the issue:

https://github.com/apache/storm/pull/1736
  
Reflect STORM-2072 : STORM-1446 now also addresses STORM-2073.


---
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] storm issue #1664: STORM-2073 [Storm SQL] Reduce multi-steps on visitProject...

2016-10-26 Thread HeartSaVioR 
Github user HeartSaVioR commented on the issue:

https://github.com/apache/storm/pull/1664
  
Closing this in favor of STORM-1446 and also STORM-2148. This is applied to 
STORM-1446.


---
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] storm pull request #1664: STORM-2073 [Storm SQL] Reduce multi-steps on visit...

2016-10-26 Thread HeartSaVioR 
Github user HeartSaVioR closed the pull request at:

https://github.com/apache/storm/pull/1664


---
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] storm issue #1697: STORM-2018: Supervisor V2

2016-10-26 Thread HeartSaVioR 
Github user HeartSaVioR commented on the issue:

https://github.com/apache/storm/pull/1697
  
@revans2 @srdo 
I'm even OK if we file an issue regarding intermittent race condition for 
local cluster and merge this now, since the race condition of Supervisor in 1.x 
is much critical. It even occurs on clustered environment.


---
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] storm pull request #1726: STORM-2139: Let ShellBolts and ShellSpouts run wit...

2016-10-26 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/storm/pull/1726


---
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] storm issue #1726: STORM-2139: Let ShellBolts and ShellSpouts run with scrip...

2016-10-26 Thread HeartSaVioR 
Github user HeartSaVioR commented on the issue:

https://github.com/apache/storm/pull/1726
  
+1 Thanks for adding the documentation @revans2 .


---
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] storm issue #1697: STORM-2018: Supervisor V2

2016-10-26 Thread revans2 
Github user revans2 commented on the issue:

https://github.com/apache/storm/pull/1697
  
OK so going through the code in both cases it looks like the only way that 
can happen is if the workers is somehow being shut down multiple times.  My 
guess is that because the slots are on different threads there is a race now 
between shutting down a worker through the slot and shutting down the worker 
through the cluster shutting down.

I'll look into reproducing it.  @srdo is there any way you can share your 
test case with us?  It would make my job a lot simpler of trying to reproduce 
and fix it.  


---
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] storm issue #1697: STORM-2018: Supervisor V2

2016-10-26 Thread srdo 
Github user srdo commented on the issue:

https://github.com/apache/storm/pull/1697
  
I seem to be getting a few new errors when running some of our own unit 
tests with this branch. The exceptions are intermittent.

``` 
java.lang.NullPointerException
at 
org.apache.storm.utils.DisruptorQueue$FlusherPool.stop(DisruptorQueue.java:110)
at 
org.apache.storm.utils.DisruptorQueue$Flusher.close(DisruptorQueue.java:293)
at 
org.apache.storm.utils.DisruptorQueue.haltWithInterrupt(DisruptorQueue.java:410)
at 
org.apache.storm.disruptor$halt_with_interrupt_BANG_.invoke(disruptor.clj:77)
at 
org.apache.storm.daemon.executor$mk_executor$reify__4923.shutdown(executor.clj:412)
at sun.reflect.GeneratedMethodAccessor303.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
at clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
at 
org.apache.storm.daemon.worker$fn__5550$exec_fn__1372__auto__$reify__5552$shutdown_STAR___5572.invoke(worker.clj:668)
at 
org.apache.storm.daemon.worker$fn__5550$exec_fn__1372__auto__$reify$reify__5598.shutdown(worker.clj:706)
at 
org.apache.storm.ProcessSimulator.killProcess(ProcessSimulator.java:66)
at 
org.apache.storm.ProcessSimulator.killAllProcesses(ProcessSimulator.java:79)
at 
org.apache.storm.testing$kill_local_storm_cluster.invoke(testing.clj:207)
at org.apache.storm.testing4j$_withLocalCluster.invoke(testing4j.clj:93)
at org.apache.storm.Testing.withLocalCluster(Unknown Source)
```

and this kind of error
```
java.lang.IllegalStateException: Timer is not active
at org.apache.storm.timer$check_active_BANG_.invoke(timer.clj:87)
at org.apache.storm.timer$cancel_timer.invoke(timer.clj:120)
at 
org.apache.storm.daemon.worker$fn__5550$exec_fn__1372__auto__$reify__5552$shutdown_STAR___5572.invoke(worker.clj:682)
at 
org.apache.storm.daemon.worker$fn__5550$exec_fn__1372__auto__$reify$reify__5598.shutdown(worker.clj:706)
at 
org.apache.storm.ProcessSimulator.killProcess(ProcessSimulator.java:66)
at 
org.apache.storm.ProcessSimulator.killAllProcesses(ProcessSimulator.java:79)
at 
org.apache.storm.testing$kill_local_storm_cluster.invoke(testing.clj:207)
at org.apache.storm.testing4j$_withLocalCluster.invoke(testing4j.clj:93)
at org.apache.storm.Testing.withLocalCluster(Unknown Source)
```

Our tests are running Storm in local mode with no time simulation. I've 
tried running the same tests on 1.x-branch, and these don't seem to occur there.


---
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] storm issue #1744: STORM-1276: line for line translation of nimbus to java

2016-10-26 Thread revans2 
Github user revans2 commented on the issue:

https://github.com/apache/storm/pull/1744
  
@dossett if you want to build the branch and do some manual testing with 
your own topologies especially looking at the UI that would be helpful.  I did 
it, but only with word count, and I looked at the UI, but I don't know how 
exhaustive it was.  So any help you can give would be great.


---
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: Storm UI does not load

2016-10-26 Thread Alessandro Bellina 
Serkan
I think the screenshot would be useful. Mind filing a JIRA with the details?
This would help:- what version of chrome/firefox?- what page(s)?- output from 
the developer console.. if you have a line number/file that is really useful
I ran 1.0.2 UI locally and submitted a topology but was not able to reproduce 
the JS error in Chrome.
Thanks
Alessandro 

On Tuesday, October 25, 2016 6:44 PM, Serkan Uzunbaz  
wrote:
 

 Storm 1.0.2.

-Serkan

On Tue, Oct 25, 2016 at 4:26 PM, P. Taylor Goetz  wrote:

> What Storm version are you on?
>
> -Taylor
>
> > On Oct 25, 2016, at 7:01 PM, Serkan Uzunbaz  wrote:
> >
> > Hi all,
> > I am having a similar issue to the one in this old thread. I am having
> the issue in Firefox and clearing the cache did not work for me. I also
> tried in Chrome and the same thing happens there too.
> >
> > The issue is intermittent but I can trigger it after a few refresh of
> the Storm UI. Restarting the ui process (core) fixes the issue temporarily,
> then after a few refresh it happens again.
> >
> > The error in the firefox dev tools console is "SyntaxError: JSON.parse:
> unexpected end of data at line 1 column 1 of the JSON data".
> >
> > I am attaching the screenshots for the stuck UI and the error I get from
> the firefox dev tools console.
> >
> > Any suggestions?
> >
> > Thanks,
> > -Serkan
> >
> >> On Fri, Sep 4, 2015 at 4:33 AM, Matthias J. Sax 
> wrote:
> >> Clearing the cache did the trick! Thanks
> >>
> >> -Matthias
> >>
> >> On 09/03/2015 11:54 PM, 임정택 wrote:
> >> > Hi, Matthias.
> >> >
> >> > Could you clear Firefox cache and try again?
> >> > I met same issue from Chrome when I switch Storm's version from
> >> > 0.10.0-beta1 to 0.9.5 or opposite, and resolved that issue by clearing
> >> > cache.
> >> > If it doesn't work, how about checking any errors from Firefox
> developer
> >> > tool or Firebug and report to dev mailing list?
> >> >
> >> > Thanks,
> >> > Jungtaek Lim (HeartSaVioR)
> >> >
> >> > 2015-09-02 20:44 GMT+09:00 Matthias J. Sax <
> mj...@informatik.hu-berlin.de>:
> >> >
> >> >> Hi,
> >> >>
> >> >> I am running Debian Jessy in my laptop. Up to now I never had
> problems
> >> >> to access Storm UI via Iceweasel (ie, Debian's Firefox). But now,
> the UI
> >> >> does not load completely. It displays "Loading summary..." and the
> >> >> background is shaded. The cluster summary on top of the page is not
> >> >> rendered correctly. See attached screenshot.
> >> >>
> >> >> The UI loads without problems using Opera.
> >> >>
> >> >> I am building Storm from the sources using the current master version
> >> >> (0.11.0-SNAPSHOT). I just rebased. The last commit is
> >> >>
> >> >>> commit 154e9ec55deb4eea8fca8554e4d3b224bf337834
> >> >>
> >> >> I am not sure what the cause of the problem might be, but I do
> install
> >> >> available OS updates regularly. I guess that an update changed
> >> >> something. (Maybe an upgrade to a new version of Iceweasel?) The
> >> >> currently installed version is 31.8.0.
> >> >>
> >> >> Maybe anyone can reproduce the problem and have a look into it? For
> now,
> >> >> I just use Opera. So for me, it's not urgent.
> >> >>
> >> >>
> >> >> -Matthias
> >> >>
> >> >
> >> >
> >> >
> >>
> >
>

[GitHub] storm issue #1697: STORM-2018: Supervisor V2

2016-10-26 Thread revans2 
Github user revans2 commented on the issue:

https://github.com/apache/storm/pull/1697
  
@HeartSaVioR good catch, I thought I had deleted it.


---
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] storm issue #1744: STORM-1276: line for line translation of nimbus to java

2016-10-26 Thread dossett 
Github user dossett commented on the issue:

https://github.com/apache/storm/pull/1744
  
I don't know enough about nimbus or clojure to vote on this PR, but this is 
an exciting change!


---
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] storm issue #1719: [STORM-1057] Add throughput metrics to spouts/bolts and d...

2016-10-26 Thread wangli1426 
Github user wangli1426 commented on the issue:

https://github.com/apache/storm/pull/1719
  
Any comment?


---
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.
---