GitHub user WolfeeTJ opened a pull request:
https://github.com/apache/storm/pull/2206
STORM-2625: reduce uncommitted count when kafka consumer group re-assâ¦
STORM-2625: reduce uncommitted count when kafka consumer group re-assign
partitions
You can merge this pull request into a
I solved it by closed firewall
On Thursday, July 13, 2017, sam mohel wrote:
> I got this error while submitting topology in distributed mode
> [ERROR] Connection timed out for connection string (192.168.1.5:2181) and
timeout (3) / elapsed (30045)
> org.apache.storm.curator.CuratorConnectionLo
Maybe we could try out Gitbox, though every committers should join their
Github accounts to 'apache' group and enable 2FA.
2017년 7월 13일 (목) 오전 8:38, Jungtaek Lim 님이 작성:
> Did we render webpage with asf-site branch? I didn't recognize it.
>
> Yes I meant separate git repository, like 'storm-site'.
Did we render webpage with asf-site branch? I didn't recognize it.
Yes I meant separate git repository, like 'storm-site'. I'm happy I'm not
the only one who feels inconvenient with SVN repo.
Would it better to initiate VOTE for this?
Thanks,
Jungtaek Lim (HeartSaVioR)
2017년 7월 13일 (목) 오전 4:30,
I got this error while submitting topology in distributed mode
[ERROR] Connection timed out for connection string (192.168.1.5:2181) and
timeout (3) / elapsed (30045)
org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode =
ConnectionLoss
at
org.apache.storm.curator.Connection
We were using git before, then a year ago moved back to subversion to implement
versioned documentation [1].
If we do decide to move back to git for this, I would recommend using a
separate git repository so it doesn’t bloat our main code repository. When
generating javadoc for a new version, t
Github user ptgoetz commented on the issue:
https://github.com/apache/storm/pull/2203
> @ptgoetz Suppose we deprecate the built-in metrics, are they deprecated
for public API or also Storm codebase? If we would want latter, we should have
alternative way to collect metrics (maybe int
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2205
+1
---
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
Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2205
+1
---
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
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/2205
Quick Fix: fix storm-cassandra to not exceed current max violation count
This broke the Travis CI builds for other pull requests.
Sure this is the temporary solution, and I filed issues for r
I'd like to bump on this again, since we have a few huge issues for Storm
2.0.0, and this issue is a kind of regression and effectively blocker.
(Please note that current master branch removes shading for some libraries
to make IDE happy.)
At that time I didn't consider option 2 as possible soluti
Hi devs,
I think we discussed moving website repository from SVN to GIT from a long
time ago, and we were OK on that, but action was not taken.
Now I can see number of projects (Spark, Kafka, Beam, maybe more) are using
separate GIT repository for website.
Although we may still need to have versi
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2203
@abellina
Ah no problem. I can see experimental branch from your fork and also pull
request for HBase storage.
Btw, from your status, nimbus is pulling (or some components are pushing,
w
Github user abellina commented on the issue:
https://github.com/apache/storm/pull/2203
This certainly is a bummer. I've been focusing on other projects so I have
been out for a while. Sorry about this.
For the status, we have an interface that gets the metrics from codahale to
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2204
DirectoryCleaner also can be moved to storm-webapp after porting
logviewer-test.clj
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2204
Also removed unused imports from other spots. I hope this is OK.
---
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 do
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/2204
(WIP) STORM-1280 port backtype.storm.daemon.logviewer to java
* port logviewer to Java using Dropwizard
* follow implementation of DRPC Server
* add '/api/v1/' to the logviewer API endp
17 matches
Mail list logo
