Github user tristeng commented on the pull request:
https://github.com/apache/accumulo/pull/74#issuecomment-189065742
Added in IT tests for the new functions, but ran into an interesting error
and am hoping you all can provide me with some insight. I've added the
following test into
(re-sending with [RESULT] in subject)
Christopher wrote:
Vote passed with +6, -0
Please double check the release notes and contribute any fixes/updates as
you have time, as I try to wrap up the rest of the release tasks.
On Thu, Feb 25, 2016 at 4:41 PM Christopher wrote:
Vote passed with +6, -0
Please double check the release notes and contribute any fixes/updates as
you have time, as I try to wrap up the rest of the release tasks.
On Thu, Feb 25, 2016 at 4:41 PM Christopher wrote:
> For what it's worth, I updated ACCUMULO-4150 to reflect
For what it's worth, I updated ACCUMULO-4150 to reflect the fact that I
finally got the tests to pass with a newer version of Hadoop, so I'm
satisfied now. :) That was really bugging me. My +1 stands.
On Thu, Feb 25, 2016 at 12:34 PM Christopher wrote:
> Oh, yes, apologies
Github user tristeng commented on the pull request:
https://github.com/apache/accumulo/pull/74#issuecomment-188987996
Whoops! Didn't even see those...was only looking under the accumulo-proxy
project. Yup, will do. I'll also add in my Python IT file into the
proxy/examples/python
Github user keith-turner commented on the pull request:
https://github.com/apache/accumulo/pull/74#issuecomment-188983450
@tristeng the proxy has fairly comprehensive ITs that excercise most of
its API. There are located in
GitHub user tristeng opened a pull request:
https://github.com/apache/accumulo/pull/74
[ACCUMULO-4147] - Add Accumulo Namespace Operations to Proxy
I've updated the the Accumulo Proxy to support namespace operations
(including the security operations). I have tested all the new
Oh, yes, apologies if I gave that impression. I'm sure we'll figure this
out, and if it is a problem in Accumulo's Kerberos feature (and not
something stupid on my end), I'm sure we're committed to fixing it quickly
and having it in the next bugfix release.
On Thu, Feb 25, 2016 at 12:31 PM Josh
Thanks. I've been doing a bit with the Kerberos stuff (in real
environments) and what is in 1.7.1 seems pretty solid to me. I just
wanted to make sure people didn't avoid it, thinking that it was not stable.
Christopher wrote:
Yeah, that's fine. I'll just reserve judgement for now, and defer
Yeah, that's fine. I'll just reserve judgement for now, and defer to
others, since I don't have time to set up a separate Kerberos environment.
As far as I can tell, the feature works fine, up to a point. I'm just not
sure what to make of this particular test. As you said, though, it's quite
+1
Ran 3 long test on EC2. The env for all 3 test was : Centos 7, JDK 8,
Hadoop 2.6.3, ZK 3.4.6, 1 m3.xlarge leader and 8 d2.xlarge workers
* 24 hr run of CI w/o agitation on EC2. XXB entries verified. Saw
performance issues outlined in comment on ACCUMULO-4146[1]. Info about #
of entries
Welcome to why people say "Kerberos is hard".
I think I said in chat, but increasing the timeout factor is not going
to make that test pass if it can't pass the first time. The MiniKDC the
tests use are not representative of a real KDC. I'd ask that you deploy
Accumulo with Kerberos before
I'm going to +1 myself, but with a reservation:
I had a lot of difficulty getting the Kerberos ITs to pass without timing
out. I was never able to get the KerberosRenewalIT to pass, even after
re-running several times (still trying), and even with a timeout factor of
20. I do not have a strong
+1
* verify signatures / checksums
* verified LICENSE/NOTICE
* source artifact corresponds to referenced commit
* source builds correctly with Oracle JDK 1.7.0_75 / Apache Maven 3.2.2
(couple of transient timeouts in ITs)
On Mon, Feb 22, 2016 at 3:41 PM, Christopher wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/43957/#review120584
---
+ 1
* verified checksums and sigs
* ran accumulo from the 1.7.1 bin download on my laptop
* built from 1.7.1 src download - unit tests and package
* ran -Psunny integration tests
- a trace test on ShellServerIT was funky, but I think it is due to
unfortunate timing, not an actual error
On
16 matches
Mail list logo