I totally agree, especially with the performance improvements in it.
Thanks,
Bobby
On Tue, Jan 22, 2019 at 12:40 AM Roshan Naik
wrote:
> Now that 2.0 has all the votes it needs to move forward, maybe a good
> time to think of some blogs to go with this long awaited release.
> Some potential
I wanted to give everyone a heads up that I have taken a new job at Nvidia
and my day to day work, though still a bit up in the air, is not likely to
concentrate on Storm as much as it did before. I am still around and will
still try to participate as much as I can, but you may need to explicitly
+1 I built the code from the git tag and all the unit tests passed. I also
ran some manual tests.
Thanks,
Bobby
On Wed, Jan 9, 2019 at 11:01 AM P. Taylor Goetz wrote:
> This is a call to vote on releasing Apache Storm 1.1.4 (rc1)
>
> Full list of changes in this release:
>
>
> https://dist.ap
I am happy to announce that Govind Menon has just been added as the latest
Committer and PMC member to the Apache Storm Project. Please join me in
congratulating him on this and thanking him for his contributions so far.
Thanks,
Bobby Evans
+1 built from the tag. All the unit tests passed and I ran some manual
tests as well.
Thanks,
Bobby
On Wed, Jan 9, 2019 at 1:16 AM Julien Nioche
wrote:
> Non-binding +1. Launched a Storm cluster in pseudo distributed mode and
> successfully ran a StormCrawler topology.
>
> Thanks
>
> Julien
+1 built from the git tag. Ran all of the unit tests and ran some manual
tests they all passed.
Thanks,
Bobby
On Tue, Jan 8, 2019 at 6:30 PM Xin Wang wrote:
> +1
>
> Built it and ran all of the tests. Everything passed.
>
> -Xin
>
> Kishorkumar Patil 于2019年1月9日周三 上午5:08写道：
>
> > +1
> >
> >
I think all of the blockers are in now. Please take a look and hopefully,
we can get a release out soon.
Thanks,
Bobby
On Fri, Dec 14, 2018 at 9:02 AM Bobby Evans wrote:
> Sorry I was out at a conference for the past week, and have been heads down
> on a different project for a while
Sorry I was out at a conference for the past week, and have been heads down
on a different project for a while before that. I'll respond to the JIRA.
I am happy to let it go in.
Thanks,
Bobby
On Thu, Dec 13, 2018 at 1:07 PM Stig Rohde Døssing
wrote:
> I think STORM-2990/3279 is ready. Bobby h
Ashwin,
Attachments don't come through on the mailing lists. Could you try putting
them in gist or something like that?
Thanks,
Bobby
On Fri, Nov 16, 2018 at 12:36 PM Ashwin Siddharth
wrote:
> Hi ,
>
> Regarding Storm Build,
>
> 1)Please refer to the attachment below , I am getting a Failure
).
For the other stuff if you find more issues we can move it to a different
thread and work through them.
Thanks,
Bobby
On Mon, Oct 22, 2018 at 9:23 AM Bobby Evans wrote:
> I'll look at upgrading that version of http client too.
>
> On Mon, Oct 22, 2018 at 9:15 AM Julien Nioche <
&
t; org.apache.http.impl.client.HttpClientBuilder.setConnectionManagerShared(Z)Lorg/apache/http/impl/client/HttpClientBuilder;
>
> Thanks
>
> Julien
>
> On Fri, 19 Oct 2018 at 17:26, Bobby Evans wrote:
>
> > Sorry I should clarify a bit.
> >
> > `storm local` wil
what you want to depend on for the majority of your
topology.
The ZK issue is new to me We have done a lot in local mode and not seen
that as an issue. If you can help me reproduce it I am happy to try and
debug it to see what is happening.
Thanks,
Bobby
On Fri, Oct 19, 2018 at 11:21 AM Bobby
It is shaded in storm 2.x, but we split the classpath up, so what you want
to depend on is storm-client only. I see you are pulling in storm-core and
a few other things that are not shaded, because they are only used by the
daemons, not the clients.
On Fri, Oct 19, 2018 at 10:55 AM Julien Nioche
+1 I checked out the code form the label.
Built it and ran all of the tests. Everything passed.
I ran some small tests on a single node cluster and they all passed. Also
did some performance tests and they look good too.
Thanks,
Bobby
On Tue, Oct 16, 2018 at 2:48 PM P. Taylor Goetz wrote:
Taylor,
I think we have everything merged that was blocking the last 2.0.0
release. If you have time please take a look at doing another one.
Thanks,
Bobby
iewer works, and that there were no errors in the
> > logs.
> > Verified the signature and SHA512 for the source and binary tars.
> >
> > We should consider deleting the md5 files, Apache's release policy
> > recommends against including them in a release
> &g
+1
built and ran all of the unit tests from the tag.
Ran some small perf tests on a single node cluster. Things look really
good there.
On a side note our CI pipeline has been running and passing builds very
close to this release too. (we are following master currently) and it is
looking good.
+1
Sounds good to me
On Mon, Oct 8, 2018 at 2:50 PM Derek Dagit wrote:
> Currently there are over 150 open pull requests on the Apache Storm GitHub
> project. Over 100 of these have not been modified in 2018.
>
> It seems we are unlikely to handle each one of these without significant
> effort
-Taylor
>
> > On Oct 8, 2018, at 9:44 AM, Bobby Evans wrote:
> >
> > Taylor,
> >
> > All of the blockers are now merged into master. I think we are ready to
> do
> > another release. Just so you know I marked all of the JIRAs that were
> > merged
> > > > https://issues.apache.org/jira/browse/STORM-3235
> > > > https://github.com/apache/storm/pull/2850
> > > >
> > > > -Kishor
> > > >
> > > > On Tue, Sep 25, 2018 at 8:04 PM P. Taylor Goetz
> > > wrote:
> > >
Taylor
>
> > On Sep 25, 2018, at 1:56 PM, Bobby Evans wrote:
> >
> > Just FYI Taylor I just merged in 3 JIRA to the master branch and will
> > probably merge in the fix for the UI that Govind mentioned, but all of
> them
> > would be okay to go into 2.0.0 as well.
Just FYI Taylor I just merged in 3 JIRA to the master branch and will
probably merge in the fix for the UI that Govind mentioned, but all of them
would be okay to go into 2.0.0 as well. Since this RC looks like it is not
going to pass if you want to move the tag up on the master branch, that
would
+1 I rebuilt the code from the git tag and all of the unit/integration
tests passed. I also ran a single node cluster with both some simple
functionality and performance tests and everything looked good.
On a side note we just deployed a version based off of the same code as
2.0.0 to staging (thi
There is a Hadoop Contributor Meetup at Oath/Yahoo on Monday in Sunnyvale CA
https://www.meetup.com/Hadoop-Contributors/events/254012512/
This is short notice and we tend to be distributed very geographically as
an open source project, but I am going to be there and if anyone wants to
show up to
I just merged in the last outstanding JIRA/pull request. I think we are
good for a 2.0.0 RC.
Thanks,
Bobby
On Wed, Sep 19, 2018 at 12:33 PM Bobby Evans wrote:
> Sounds good.
>
> I just filed https://issues.apache.org/jira/browse/STORM-3230 and I'll be
> putting up a pull r
’ll slog through it.
>
> -Taylor
>
> > On Sep 18, 2018, at 10:46 AM, Bobby Evans wrote:
> >
> > Great work everyone. We are really close on this. We have everything in
> > except for https://github.com/apache/storm/pull/2719, but there has
> been no
> >
candidates in the past and
done all of the votes for them. If you want to continue the trend that is
fine with me, but if not I am happy to do it, but I might have to bug you
to be sure I do it all correctly.
On Mon, Sep 17, 2018 at 9:13 AM Bobby Evans wrote:
> I think we are really close on t
t; >> > > >
> > >> > > > On Mon, Sep 10, 2018 at 2:24 PM, P. Taylor Goetz <
> > ptgo...@gmail.com
> > >> >
> > >> > > wrote:
> > >> > > >
> > >> > > > > I agree, and lookin
please respond to this with the JIRA number. I would like to
set a goal/tentative date of Sep 17th (one week from today) to put together
a release candidate for a 2.0.0 release, and unless there are major
blockers that show up I think we can do it.
Thanks,
Bobby Evans
p.s. I don't want to c
+1 I built from the git tag, all the unit tests passed. I ran a single
node cluster and everything worked for my small unit tests.
Thanks,
bobby
On Wed, May 23, 2018 at 3:54 PM Jungtaek Lim wrote:
> REMINDER: The vote has been opened from 6 days ago, and still has only two
> binding +1s. Plea
+1
I built it from source. All the unit tests passed and I ran a few manual
tests on a single node cluster.
Thanks,
Bobby
On Thu, May 17, 2018 at 3:00 PM P. Taylor Goetz wrote:
> This is a call to vote on releasing Apache Storm 1.2.2 (rc3)
>
> Full list of changes in this release:
>
>
> http
+1
I built from the git tag, ran all of the unit tests launched a single node
cluster and ran a few simple tests on it.
On Thu, May 3, 2018 at 12:21 PM P. Taylor Goetz wrote:
> This is a call to vote on releasing Apache Storm 1.1.3 (rc1)
>
> Full list of changes in this release:
>
>
> https://d
+1 I built it from the tag (e001672cf0ea59fe6989b563fb6bbb450fe8e7e5) since
the tag did move recently.
I ran all the unit tests, I started a single node cluster and ran some
manual tests.
Thanks,
Bobby
On Thu, May 3, 2018 at 12:18 PM P. Taylor Goetz wrote:
> CORRECTION: The Nexus staging repo
Please Join with me in welcoming Ethan Li as the newest Apache Storm
committer and PMC member.
Great work!
Sorry for the late reply. Congrats and thanks for all of your great work
for the community Erik.
Thanks again,
Bobby
On Sun, Feb 25, 2018 at 10:45 PM Aaron Niskodé-Dossett
wrote:
> Congrats, Erik, well deserved!
> On Sun, Feb 25, 2018 at 10:27 PM Satish Duggana
> wrote:
>
> > Congrats and We
Sorry for the late reply.
I am 100% in favor of shading again for very common dependencies. The big
issue is around how do we do this cleanly? I like the way flink does it.
That can help with some of the issues we see with IDEs, but we just need to
be very careful with transitive dependencies wh
Yes that is something that we are working on, especially around the
resource aware scheduler. We have added in a new metrics path to have CPU
and Memory usage reported to nimbus. We plan to extend this to other
metrics in the future and then start working on how to properly do
elasticity.
Thanks
+1
I built from source all of the unit tests passed and some basic integration
tests passed too.
On Sat, Feb 10, 2018 at 12:00 PM Alexandre Vermeerbergen <
avermeerber...@gmail.com> wrote:
> Hello,
>
> +1 (non binding)
>
> Details: I almost got nuts when applying storm-kafka-client-1.2.0 RC4
> t
obby, let’s leave it there and continue with the RC.
>
> Thanks for pointing that out Bobby.
>
> -Taylor
>
> > On Feb 9, 2018, at 4:07 PM, Bobby Evans wrote:
> >
> > Actually it is set properly. Do NOT change it. It works just fine the
> way
> > it is.
>
-SNAPSHOT.jar
org.apache.storm.tuple.Fields
org.apache.storm.tuple.Fields:private static final long
serialVersionUID = -3377931843059975424L;
This is the same version that we set it to as a part of the change.
- Bobby
On Fri, Feb 9, 2018 at 3:00 PM Bobby Evans wrote:
> Fields changing will ca
+1 I built the code from the git tag, ran all the unit tests (which passed
the first time), and ran some tests on a single node cluster.
It all looked good.
- Bobby
On Thu, Feb 8, 2018 at 1:22 PM P. Taylor Goetz wrote:
> This is a call to vote on releasing Apache Storm 1.0.6 (rc3)
>
> Full lis
+1 I built from the tag and did some basic tests on a single node cluster.
I am disappointed that it took me 7 times to get all of the unit tests to
pass for the build, but I don't think it should block a release.
- Bobby
On Thu, Feb 8, 2018 at 11:48 AM P. Taylor Goetz wrote:
> This is a call
I agree about decoupling storm-kafka from storm core for releases.
We put them together initially because we wanted storm to come with
batteries included. We have made some major changes to storm over the
years and it has been good to have kafka integration, along with a lot of
other integration,
Algoby,
When you say transfer queue, which queue do you mean exactly. In storm
there are a lot of queues currently and they sometimes have confusing names.
There is the receive queue, which holds tuples to be processed by a
specific executor. Then there is the send queue, or some times called t
The name comes from the name of the main class being executed. For the ui
it is coming from clojure and is core. The only way I know to change it is
to change the name of that class, which we probably will do when we finally
translate it to java.
You could also use -i to get the full package nam
s/icla.pdf)
> > > is that it's probably not okay to take someone else's commits along
> with
> > > your own, squash them and submit the whole thing under your own name.
> > Point
> > > 7 mentions how to submit on behalf of others.
> > >
>
I totally agree. If you have reached out to an author and there has been
no response for either a bug fix or a feature that you want, then feel free
to take it over. Just be polite about it and make sure it is clear to
everyone what you are doing.
-
Bobby
On Wed, Sep 13, 2017 at 11:19 PM Jungta
u.
>
> Best regards,
> /Gayashan
>
> On Tue, Sep 12, 2017 at 12:26 AM, Bobby Evans
> wrote:
>
> > A lot of that depends on the version of storm you have, and it is not a
> use
> > case that we have played around with too much.
> >
> > Just looking at a f
A lot of that depends on the version of storm you have, and it is not a use
case that we have played around with too much.
Just looking at a few of our production clusters the CPU usage is very
small (but trying to determine what the CPU usage on a raspberry pi arm
chip when all you have is the us
Under 2.x LocalCluster is much more fully featured and you can set daemon
configs using the LocalCluster.Builder.withDaemonConf. But for all other
versions of storm the only way to change things like the daemon conf are
through the clojure API, which I assume you don't want to use.
So sorry but n
7일 (월) 오후 10:52, Bobby Evans 님이 작성:
> Please don't remove the .md docs from the storm repo. Those docs document
> the current build. Things that are common and almost never change we can
> move to a separate repo. But things that change from one release to
> another should stay, be
(수) 오전 8:09, Jungtaek Lim 님이 작성:
>
>> FYI: I just take a step to this, but blocked at creating git repository
>> in reporeq.apache.org.
>>
>> Just filed https://issues.apache.org/jira/browse/INFRA-14765. In that
>> issue I also asked how to serve website with non-main
ks near other
(bolt/spout) tasks, would it effect the performance?
thanks again for your answer.
On Tue, Aug 1, 2017 at 6:20 PM Bobby Evans
wrote:
> By default there are no `_eventlogger` tasks. To have this feature
> enabled you need to turn it on by setting topology.eventlogger.executo
I am not completely sure why that was a requirement. I know internally we have
removed it, not sure if we pushed that change back or not yet. On newer
versions of storm 1.0.3+ that have the rewritten supervisor that check is
invalid and you should be able to remove the check and just update th
from how quickly we can have
multiple contributors pick new areas of the code and quickly expand on it. This
is easier to achieve with good documentation, clean, modular code, and good
unit testing that allows for quickly trying things out.
Hugo
> On Aug 2, 2017, at 7:46 AM, Bobby Eva
d for adding New features,
> > config
> > changes or backward-incompatible changes. Don't require
> > adding a KIP for bug-fixes. Devs who wants to add any
> > features will write up a wiki which has JIRA link, mailing
> > list discussion link and outline the Motiva
eed to shade for now if we don't
plan to upgrade to 4.x: package name differs) is in my list.
Would be better to initiate poll or discussion with separate thread?
- Jungtaek Lim (HeartSaVioR)
2017년 7월 20일 (목) 오전 2:27, Bobby Evans
mailto:ev...@yahoo-inc.com.invalid>>님이 작성:
I am fine with
t 9:39 AM, Bobby Evans wrote:
>
> Rebuilding everything each time is sadly necessary as currently the
> header/footer for all of the content is inline in each page. So if we add a
> new release every page changes. To fix this we would have to change the
> header to dynamicall
By default there are no `_eventlogger` tasks. To have this feature enabled you
need to turn it on by setting topology.eventlogger.executors to a positive
number. Ackers are on by default, but can be disabled by setting the number of
topology.acker.executors to 0. You should respect these when
Rebuilding everything each time is sadly necessary as currently the
header/footer for all of the content is inline in each page. So if we add a
new release every page changes. To fix this we would have to change the header
to dynamically include the HTML from another file that gets updated on
need to be very conscientious about updating JIRA as
necessary.
-Taylor
> On Jul 31, 2017, at 10:06 AM, Bobby Evans wrote:
>
> I am happy to switch as soon as someone has a working alternative. The big
> thing in my opinion is giving end users a clear list of all of the changes
&
It should be possible to make this work, but it is not going to be simple. The
real issue is the format of the orc file. It is not one record at a time, like
CSV or other supported formats are. Sadly this is currently an assumption with
the AbstractHdfsBolt.
https://github.com/apache/storm/bl
I am happy to switch as soon as someone has a working alternative. The big
thing in my opinion is giving end users a clear list of all of the changes that
went into a release so they can review it for themselves. However we do it is
fine with me as the current changelog file leaves a lot to be
+1
I am fine with moving to git, but I would like it to be a different repo.
Our current repo is at least 160MB already (which is a lot to download) but
nothing compared the the web site that has lots and lots of things checked in
(I estimate it at about 1.5GB on an older version I have locally)
iscussion with separate thread?
- Jungtaek Lim (HeartSaVioR)
2017년 7월 20일 (목) 오전 2:27, Bobby Evans 님이 작성:
> I am fine with a separate project for relocated dependencies (or even just
> separate packages, you do a maven install of them and not include them in
> the IDE at all). Shading still
+1 built from source (v1.1.1 41bfea87b1a002565333bd18a06d766af1ca3816) Ran all
of the unit tests and some manual tests.
- Bobby
On Thursday, July 27, 2017, 1:38:46 PM CDT, P. Taylor Goetz
wrote:
This is a call to vote on releasing Apache Storm 1.1.1 (rc2)
Full list of changes in this rele
worker.childops is the default value that is set by the system administrator in
storm.yaml on each of the supervisor nodes. topology.worker.childopts is what
you set in your topology conf if you want to add something more to the command
line.
- Bobby
On Tuesday, July 25, 2017, 11:50:04 PM C
We could do a 1.1.2 release sooner if needed. Technically any committer can
call for a release at any point in time. If there is a reason to do a release
(like an important fix for a critical component) then we can do it.
- Bobby
On Tuesday, July 25, 2017, 1:48:07 PM CDT, Alexandre Vermeerb
I built from source (v1.1.1 88f0b8a45553ea960164fab18c736a5cdbae8e58) ran all
of the unit tests and ran some manual tests.
I am +1 on the release.
- Bobby
On Tuesday, July 25, 2017, 11:14:14 AM CDT, Kishorkumar Patil
wrote:
I built and ran some manual tests.
+1 to release this package.
-
I built from source (v1.0.4 a5e1c154b5b2ae74fd78bf10d4c130afb1ad4513), ran all
of the unit tests, and ran a few manual tests on my laptop.
I am +1 on the release.
- Bobby
On Tuesday, July 25, 2017, 6:27:18 AM CDT, Stig Rohde Døssing
wrote:
The linked changelog (https://git-wip-us.apache.org
ter.
- Jungtaek Lim (HeartSaVioR)
2017년 7월 20일 (목) 오후 11:30, Bobby Evans 님이 작성:
> Moving to the dev mailing list as it is more than just the PMC that
> provides support for storm.
>
>
> - Bobby
>
>
>
> On Wednesday, July 19, 2017, 6:27:12 PM CDT, Hugo Louro <
> hmclo
Moving to the dev mailing list as it is more than just the PMC that provides
support for storm.
- Bobby
On Wednesday, July 19, 2017, 6:27:12 PM CDT, Hugo Louro
wrote:
The first question is, do we want to provide chat support? It has the pro of
being more interactive, but the con of making
against LICENSEs to repackage
> shade & relocated artifacts to Maven.
>
> Thanks,
> Jungtaek Lim (HeartSaVioR)
>
> 2017년 3월 29일 (수) 오후 10:42, Bobby Evans 님이 작성:
>
> I am fine with those changes so long as we finish the separation of worker
> and daemon classpaths. Othe
Welcome
- Bobby
On Saturday, July 15, 2017, 8:01:47 PM CDT, Matthias J. Sax
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Congrats!
On 7/14/17 6:17 PM, Xin Wang wrote:
> Congrats Stig!
>
> - Xin
>
> 2017-07-15 9:13 GMT+08:00 Satish Duggana
> :
>
>> Congrats Stig!
>>
>> ~Satish.
you point me to any Storm documentation which makes a comment on preferable
failure rates. I was suggesting if we can offer the user an optimization
through clean API, the user will be free to decide on the rationale of
using it.
On Tue, Jul 11, 2017 at 12:06 AM, Bobby Evans
wrote:
> I'm n
I'm not sure what assumptions you want to make that this is preventing, or why
they would be helpful.
- Bobby
On Monday, July 10, 2017, 12:14:53 PM CDT, chandan singh
wrote:
Hi Stig & Bobby
Thanks for confirming my understanding.
1) Ensuring that calls to nexTuple(), ack() and fail() are
For #2 it is a question of what do you optimize for. Storm typically assumes
that failures should be rare so we optimize for that. We keep the minimal
information around to be able to replay the message, but not a lot more. If
you are getting lots of failures, you really should be more concer
You are going to need to look at the logs for your topology and the logs for
the drpc server to see if there is anything in there that indicates what is
happening.
- Bobby
On Wednesday, June 28, 2017, 11:21:14 PM CDT, sam mohel
wrote:
I submitted topology in local without any problem , but
17년 6월 24일 (토) 오전 5:19, P. Taylor Goetz 님이 작성:
> > >
> > >> Bobby/Jungtaek,
> > >>
> > >> Are you saying you want to forego the 1.2 “metrics_v2” release and
> include
> > >> it only in 2.0? (I ask because that work is already based on
>
like that work
go out soon.
If we go with option 1, I would want to see a 2.0 release (even if it’s a
“beta” or “preview) before putting the 1.x line into maintenance mode.
-Taylor
> On Jun 23, 2017, at 9:51 AM, Bobby Evans wrote:
>
> I see 2 ways to address this.
> 1) We
> (And that's what I would want to.)
> >
> > If we would really want to have 1.2.0, I suggest that we make the
> 1.1.1
> > version correct right now rather than after releasing 1.1.1. We also
> > merged
> > non-bugfix things to 1.x-branch but that's
Each bolt/spout has 2 threads of their own. In one thread the bolt/spout
executes on. A second thread then batches/routes the tuples where they need to
go. This may be putting them in the input queue for another bolt/spout in the
current worker or putting them on a queue to be sent to a diffe
In practice I am OK with the change, as it does not impact any of the end user
facing configs. The incompatibility is for administrators, which I think is
fine. I am not convinced of some of the design choices, but those can be
discussed on the JIRA.
- Bobby
On Thursday, June 15, 2017, 1:3
Turn on garbage collection logging on your workers. We have found that GC is
typically the culprit in cases like this. A large stop the world GC happens
which makes all threads wait for it so the heartbeats time out and things get
rescheduled.
Once you know it is GC then you need to take a loo
Can you please explain how KIP currently works and how you would like to see
something similar in storm?
If we make the process more formal we will probably have less people
contributing, but we will probably have better overall patches. It is a
balancing act and having never used KIP I would l
I would love to see the metrics V2 code come out sooner rather than later. +1.
My biggest blocker for a 1.x release is
https://github.com/apache/storm/pull/2142 Even though the pull request says it
is minor it showed that we messed up pushing back some changes for pacemaker to
open source (the
As this is for a change going into 2.x I totally agree lets just change the
API. If we really want to do a good job we can also have a pull request in the
1.x version that adds in the new API and deprecates the old one, so users are
not caught off guard as much.
- Bobby
On Sunday, May 21, 20
First of all I am not an expert on trident. I understand it at a high level,
but I have not done too much with the internals of it. And yes we are all in
agreement that the documentation for trident is quite bad. It was something
that Nathan finished just before he left Twitter so a lot of th
17 at 1:58 PM, Bobby Evans
wrote:
> This looks like something odd is happening with leader election. The
> exception looks like it is caused by trying to read a NimbusSummary for the
> leader but not being able to find it. So it could mean that a leader is
> elected and is then crashin
This looks like something odd is happening with leader election. The exception
looks like it is caused by trying to read a NimbusSummary for the leader but
not being able to find it. So it could mean that a leader is elected and is
then crashing quickly enough that the other node when it tries
a 0.9.x or 0.10.x topology will not be compatible with a 1.x cluster. We
changed the package names from backtype to org.apache in between the two. So
even though the client can talk to the nimbus through thrift the topology will
not run, with exceptions like you saw. The best solution is to u
instead of 100)
Thanks,
Arun
On 5/2/17, 12:32 AM, "Bobby Evans" wrote:
>Just a reminder to everyone that voting ends on Wednesday.
>
>
>- Bobby
>
>On Friday, April 28, 2017, 1:33:37 PM CDT, Kishorkumar Patil
> wrote:
>[1] Google Java Style Guide&l
Taylor, are you still working on the BEAM impl? If so could you use Kamal's
help at all?
- Bobby
On Thursday, April 27, 2017, 1:32:44 PM CDT, Kamal Bhatt
wrote:Hello,
I am a developer interested to work on Storm tasks based on Java Streaming
API and/or supporting storm as a runtime for apa
ich is described as java but with 2 spaces instead of 4.
> Thanks,
> -- Kyle
>
> On Thursday, April 27, 2017, 3:51:25 AM CDT, Julien Nioche <
> lists.digitalpeb...@gmail.com> wrote:Non-binding : [1 ] Google Java Style
> Guide
>
> On 26 April 2017 at 19:50, Bobby Evans
I forgot to mention that we will have the vote run for 7 days just to give
everyone a chance that wants to vote. So it will close Wednesday May 5th.
- Bobby
On Wednesday, April 26, 2017, 1:50:56 PM CDT, Bobby Evans
wrote:We would like to adopt a code style
standard for Apache Storm
er.xml>
(sorry all I could find was an eclipse XML config)
[ 3 ] Hadoop style<https://wiki.apache.org/hadoop/CodeReviewChecklist> which is
described as java but with 2 spaces instead of 4.
[ ] Other (Please specify)
- Bobby
On Wednesday, April 26, 2017, 1:50:56 PM CDT, Bobby Evans
wrot
We would like to adopt a code style standard for Apache Storm. Please rank the
following with 1 being the most desired and 4 being the least desired (5 if you
have a write in choice). This is not an official vote as per the ByLaws, but
we will probably go with whichever wins the most 1 votes (
I really don't care what style we use so long as we have one and it is
enforced. Checkstyle is highly configurable so just about any style we pick we
can enforce with it. Most Java IDEs that I know of either use the checkstyle
format itself or at least support a checkstyle plugin to let you kn
No there is currently no way to do this with the default strategy. You can
write your own resource aware strategy to place the workers differently though.
You just need to write a class that implements IStrategy. It can also be
selected on a per topology basis.
The main reason for doing thi
That is a little hard to tell. It looks like your ZK server crashed and was
not relaunched.
- Bobby
On Friday, April 7, 2017, 1:35:43 AM CDT, xx wrote:hi,
everyone! Lylian for your help!I'm running a storm cluster.I have a
nimbus,zookeeper,kafka server, and a supervisor in one node.Further
1 - 100 of 469 matches
Mail list logo
