Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/803#issuecomment-148811510
I see with present changes, when I performed the unit test, netty
```test-basic``` and ```test-large-msg``` work fine but ```test-batch``` fails
if we go over 1000
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/803#issuecomment-148789458
I see I should be updating netty_unit_test.clj to prevent the Travis CI
build failures. I shall push an update soon.
---
If your project is set up for it, you can
GitHub user bourneagain opened a pull request:
https://github.com/apache/storm/pull/803
STORM-1071 Task Message format to include source task id
As part of gathering inputs for Resource Aware Scheduler, understanding the
tuple network characteristics between tasks would be helpful
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/768#issuecomment-144833931
There seems to be a problem with workers dying if the topology is left to
run for long time. I shall debug and open a new pull request after merging with
master
Github user bourneagain closed the pull request at:
https://github.com/apache/storm/pull/768
---
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 bourneagain opened a pull request:
https://github.com/apache/storm/pull/768
STORM-1071 : Task Message format to include source task id.
As part of gathering inputs for Resource Aware Scheduler, understanding the
tuple network characteristics between tasks would be
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/608#issuecomment-132722067
*** PLEASE DO NOT MERGE THIS YET
More information @ https://issues.apache.org/jira/browse/STORM-919.
---
If your project is set up for it, you can reply
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/608#issuecomment-127623505
I will revert the changes to Thrift generated files and update the pull
request. Also I have updated details on how we plan to use these metrics @
https
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/632#issuecomment-122483857
Thanks for the comments, I understand the implication now and have changed
the code accordingly.
---
If your project is set up for it, you can reply to this email
GitHub user bourneagain opened a pull request:
https://github.com/apache/storm/pull/632
STORM-918 Storm CLI could validate arguments/print usage
Storm commands that mandate proper args to be passed would now throw
the function's doc string as help rather than exiting out
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/593#issuecomment-121281726
Thanks @HeartSaVioR .We can have this merged to master whenever we feel
appropriate.
---
If your project is set up for it, you can reply to this email and have
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-120938865
Thank you @HeartSaVioR
---
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
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-120450816
@HeartSaVioR Thanks. Can this be merged into the master now?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/593#issuecomment-118856776
I am working on few more review comments presently and shall update as soon
as its available for further review. Thanks!
---
If your project is set up for it, you
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/608#issuecomment-118634483
Thanks @lazyval . I shall keep that in mind going forward. For review we
can omit all those under the "generated" directory.
---
If your project is set
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-118633914
Thanks @HeartSaVioR . I apologize for the mistake. I have now removed the
local debug I had put on during testing.
---
If your project is set up for it, you can
Github user bourneagain commented on a diff in the pull request:
https://github.com/apache/storm/pull/575#discussion_r33894593
--- Diff: storm-core/src/jvm/backtype/storm/utils/ShellProcess.java ---
@@ -48,8 +50,31 @@ public ShellProcess(String[] command
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-118387380
Thanks @HeartSaVioR . I have fixed the imports issue and tested on local
machine to see it working fine. I shall keep a note of this in future. Thanks.
---
If your
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-11990
Thanks Derek for the comments. I have now pushed in the changes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user bourneagain opened a pull request:
https://github.com/apache/storm/pull/608
STORM-919 Gathering worker and supervisor process information (CPU/Memory)
- Changes to the worker and supervisor heartbeats to carry the system stats
( CPU util % and JVM memory stats in KB
GitHub user bourneagain opened a pull request:
https://github.com/apache/storm/pull/593
STORM-67 Provide API for spouts to know how many pending messages there are
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bourneagain
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-51124
Thanks HeartSavior. I have cleaned up the commit history now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-110366648
The changes to ShellSpout have been committed now.
---
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 bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-109361408
Thanks HeartSaVioR. Yes we can apply this to ShellSpout as well. I will do
the changes shortly.
---
If your project is set up for it, you can reply to this email
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/575#issuecomment-108958705
The build failure seems to be only with JDK 7 during the
**storm.kafka.TridentKafkaTest**
` [main] ERROR kafka.producer.async.DefaultEventHandler - Failed
GitHub user bourneagain opened a pull request:
https://github.com/apache/storm/pull/575
STORM-160 Allow ShellBolt to set env vars (particularly PATH)
Support to allow ShellBolt to set environment variables
Example :
WordCountTopology.javaâ¨builder.setBolt("
26 matches
Mail list logo
