The release passes:
+1 (binding):
- James Sirota
- David Lyle
- Ryan Merriman
- Casey Stella
+1 (non-binding):
- Justin Leet
That's what this fix was for:
https://github.com/apache/incubator-metron/pull/422. I realize it is
getting deprecated, but would have preferred to have something actually
working before we deprecate. But alas...
On Sat, Feb 25, 2017 at 10:42 AM, David Lyle wrote:
> I'm
16GB. It's a MBP from a few years back. I'm getting the same result as most
it seems, currently oversubscribed but doable with care, works way better
with the Ansible/Ambari integration that I'm doing for METRON-671.
-D...
On Sat, Feb 25, 2017 at 2:13 PM, Matt Foley wrote:
>
David, how much RAM do you have in the test system where you run full dev?
On 2/25/17, 8:46 AM, "David Lyle" wrote:
+1 (binding)
Checked signatures
Tests passed
Full dev ran sucessfully-ish (bit more below, tl;dr- it's ugly, but much
better after
+1 (binding)
Checked signatures
Tests passed
Full dev ran sucessfully-ish (bit more below, tl;dr- it's ugly, but much
better after METRON-671)
Data flowed into the index/dashboard/hdfs
On full-dev: Monit got into a state where it started killing topologies
because the Storm cli was non-responsive
I'm running it up now. I don't think it should affect the release, but it's
extremely important that full-dev work. It's how quick-dev is created. Any
notion that it's been deprecated is incorrect.
Fwiw, I've been working with it for the last few weeks as part of
METRON-671 and it's been
I see this with full dev on my laptop pretty much every time.
I think it is a resource issue. I see not enough memory errors trying to
start things.
On February 25, 2017 at 09:15:15, Ryan Merriman (merrim...@gmail.com) wrote:
When I go to Ambari to ensure the services are all up, HDFS is
When I go to Ambari to ensure the services are all up, HDFS is down. I tried
it 4 or 5 times and got the same result each time. I've seen others validate
with quick dev so I assumed full dev was not used anymore. I'll spin it up
this morning and get a more detailed error.
Is anyone else
What exactly are the errors that you saw, Ryan?
On Sat, Feb 25, 2017 at 07:31 David Lyle wrote:
> Is there any reason full dev shouldn't be working?
>
> On Fri, Feb 24, 2017 at 9:19 PM, Casey Stella wrote:
>
> > Sounds like a good idea to me; thanks
Is there any reason full dev shouldn't be working?
On Fri, Feb 24, 2017 at 9:19 PM, Casey Stella wrote:
> Sounds like a good idea to me; thanks Ryan!
> On Fri, Feb 24, 2017 at 21:11 Ryan Merriman wrote:
>
> > +1 binding
> >
> > Verified the signature
>
Sounds like a good idea to me; thanks Ryan!
On Fri, Feb 24, 2017 at 21:11 Ryan Merriman wrote:
> +1 binding
>
> Verified the signature
> Passed maven tests
> Started quick-dev, verified data in ES, kibana, and checked the topologies
> for errors (bro topology has parsing
+1 binding
Verified the signature
Passed maven tests
Started quick-dev, verified data in ES, kibana, and checked the topologies
for errors (bro topology has parsing errors but I think a couple bad
messages in bro data set is normal)
Tested REPL
RPMs built fine
The recommended build validation
+1 (non-binding)
Verified signature
Ran build and tests in maven
Ran up in quick-dev and saw data flow through topologies into the UI
Ensured the REPL spun up and performed some basic tasks
Built rpms
Justin
On Thu, Feb 23, 2017 at 11:18 AM, Casey Stella wrote:
> This is a
This is a call to vote on releasing Apache Metron 0.3.1-RC5 incubating
Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.1-RC5-incubating/CHANGES
The tag/commit to be voted upon is apache-metron-0.3.1-rc5-incubating:
14 matches
Mail list logo