Github user joshelser commented on the issue:
https://github.com/apache/accumulo/pull/272
The description of this change makes me wonder if this is intended as a
band-aid. It reads as those the root issue is that the Master orphans
migrations (which causes problems in the balancer). A
Github user ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
I do not believe we have orphaned migrations (that would be a bug). Our
problem is migrations that hang or should I say take a very long time (perhaps
hours) because the tablet being migrated is i
Github user joshelser commented on the issue:
https://github.com/apache/accumulo/pull/272
> Our problem is migrations that hang or should I say take a very long time
(perhaps hours) because the tablet being migrated is in the process of being
compacted.
Ahh, ok. Thanks for cl
Github user mjwall commented on the issue:
https://github.com/apache/accumulo/pull/272
@ivakegg, I am seeing a similar issue where migrations are not happening
but it is not compactions hold them up. Still investigating, but it leads me
ask if this should be configurable. I fear thi
Github user ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
It is configurable via HOST_BALANCER_OUTSTANDING_MIGRATIONS_KEY
---
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 mjwall commented on the issue:
https://github.com/apache/accumulo/pull/272
ah, so if I set that 0 it is old behavior? Thanks @ivakegg
---
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
Github user ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
Correct
---
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 f
Github user mjwall commented on the issue:
https://github.com/apache/accumulo/pull/272
Awesome, so perhaps that can be the default instead of 500? I may have
more to add if I ever figure out what I am seeing elsewhere.
---
If your project is set up for it, you can reply to this emai
Github user ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
Ok, I can do that. However this has proven to work very well so it seems a
shame to deliver this feature disabled.
---
If your project is set up for it, you can reply to this email and have your
Github user mjwall commented on the issue:
https://github.com/apache/accumulo/pull/272
Well, it is proven to work in your case which I think is compactions. So
when the compaction finishes, the tablet eventually migrates. Is that
accurate? I am thinking my issue is different and th
Github user dlmarion commented on the issue:
https://github.com/apache/accumulo/pull/272
Agreed that the default should be the old behavior in the 1.x releases. We
can change the behavior in the 2.x release line and it should be noted in the
2.0 release notes.
---
If your project is
Github user dlmarion commented on the issue:
https://github.com/apache/accumulo/pull/272
Latest commit causing build to fail with test failure at:
HostRegexTableLoadBalancerReconfigurationTest.testConfigurationChanges:83
expected:<5> but was:<0>
---
If your project is set up
Github user ctubbsii commented on the issue:
https://github.com/apache/accumulo/pull/272
Haven't looked at the content of the PR yet, but one initial observation:
please follow git log message formatting conventions separating title/subject
from body. Here's [one summary][1] of those
Github user ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
@ctubbsii OK, I reworked the git comments on all of my pull requests
---
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
Github user ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
OK, I am going to attempt to merge this tomorrow unless anybody has more
comments
---
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 ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
Merged into 1.8 branch and merging up into master (2.0)
---
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 joshelser commented on the issue:
https://github.com/apache/accumulo/pull/272
@ivakegg next time (If you are unaware of it, sorry if you are already),
the following is a nice little trick to clean things up for you upon merge :)
https://help.github.com/articles/clo
Github user ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
@joshelser Thanks...that happens to be exactly what I did.
---
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 h
Github user joshelser commented on the issue:
https://github.com/apache/accumulo/pull/272
lol, i'm sorry -- I meant to send you
https://help.github.com/articles/closing-issues-using-keywords/ :)
---
If your project is set up for it, you can reply to this email and have your
reply app
Github user ivakegg commented on the issue:
https://github.com/apache/accumulo/pull/272
I also did that in the commit message, however it did not close
automatically for me. I am guessing this is because this pull request is a
request to merge into the mirror at https://github.com/ap
20 matches
Mail list logo
