Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/933
@mmiklavc - the special cut has a larger swap volume than the standard
image. It also is customized to what Metron required at the time to run. That's
pretty much it. If that's still desirable
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/784
+1 by inspection.
---
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
@justinleet (or anyone really), I'd like to push this today, still good?
---
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
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
@justinleet - this seems better. The change is to not error when the rest
service is unavailable but use that as an indication that the topologies are
stopped. The rest is code formatting because
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
Oh yeah, thanks for clarifying, @anandsubbu - I'm not going to change the
'happy path' logic, so when the UI is up, it will work the way it did prior.
---
If your project is set up for it, you
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
I'm starting to think the best approach would to assume the service is
stopped if we can't get to the ui (which we kind of do anyway because of how
status works).
Anybody absolutely hate
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/680
Thanks @justinleet - I'm going to hold off on this, @anandsubbu did some
additional testing and it didn't actually solve the problem. :(
---
If your project is set up for it, you can reply
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/678
+1 by inspection. Good stuff, much improved, thanks.
---
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 dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/481
My test environment is being funky, I'm +1 by inspection- thanks for the
work, please don't let me hold you up any more.
---
If your project is set up for it, you can reply to this email
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/481
@mattf-horton - sorry about the hurry up and wait. I'll run this up
tomorrow. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/481
Awesome! I can run it up on a live system and see what's what. Thanks!
---
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
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/481
@mattf-horton - Can I offer some help getting back to this? Is a pretty
important fix.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/627
+1 (inspection). Nice one, Otto, thanks. Just bumped into this yesterday.
---
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
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/614
+1. Used this with a largish instance, worked well, thanks!
---
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
Github user dlyle65535 commented on a diff in the pull request:
https://github.com/apache/metron/pull/581#discussion_r118778981
--- Diff: metron-interface/metron-config/scripts/package.json ---
@@ -9,7 +9,8 @@
"http-proxy-middleware": "0.17.4",
GitHub user dlyle65535 opened a pull request:
https://github.com/apache/incubator-metron/pull/576
METRON-945: Resolve merge conflict in metron.spec
## Contributor Comments
This changeset will allow the rpm build to complete. Currently, master will
fail trying to build the rpms
GitHub user dlyle65535 opened a pull request:
https://github.com/apache/incubator-metron/pull/574
METRON-934: Component and task id are missing in the indexing topology Hdfs
file names.
## Contributor Comments
Prior to this changeset, all files written to hdfs will have
GitHub user dlyle65535 opened a pull request:
https://github.com/apache/incubator-metron/pull/563
METRON-840: All "ambari_*" hosts need to have a /localrepo folder
## Contributor Comments
Fixes broken EC2 deployment. With the default config, each host running
needs
GitHub user dlyle65535 opened a pull request:
https://github.com/apache/incubator-metron/pull/561
METRON-913: Create IP Report in Zeppelin
## Contributor Comments
For a given IP address, produces a report of:
* Most Frequent Connections (Yaf, defaults to 24 hours
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/552
Ditto. +1, thanks Otto!
---
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
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/459
I think you're suffering from the same intermittent issues we have on
master. Concur that you didn't add anything that obviously would create a
problem and you may have helped. Maybe
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/538
+1 - pulled in the dependency changes, deleted my .m2 cache and the build
ran as expected. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user dlyle65535 commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/544#discussion_r112950226
--- Diff: metron-deployment/vagrant/full-dev-platform/README.md ---
@@ -24,35 +26,38 @@ Any platform that supports these tools is suitable
Github user dlyle65535 commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/543#discussion_r112808661
--- Diff: metron-deployment/packaging/docker/rpm-docker/pom.xml ---
@@ -227,4 +183,97
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/538
Also @mmiklavc, please remember if the intended effect was to make the rpm
build happen after everything else completed then install + pom dependencies
didn't work. If you take a close
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/538
In fact, having given it additional thought, the dependency mechanism is a
way of saying "hey Maven, make sure you pull those artifacts into our .m2
cache" which is
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/540
You shouldn't have to build Metron prior to running 'vagrant up', the
Ansible provisioner does that. Following these instructions, you'll actually
build Metron twice for each build
27 matches
Mail list logo
