Yi Mei created HBASE-21783:
--
Summary: Support allow exceed user/table/ns rpc throttle quota if
region server has available quota
Key: HBASE-21783
URL: https://issues.apache.org/jira/browse/HBASE-21783
I think we can drop the support of 2.7.x and 2.8.x when releasing 2.2.0 and
1.5.0?
And is it the time to change our default building profile from hadoop2 to
hadoop3?
Andrew Purtell 于2019年1月25日周五 上午11:22写道：
> We could see what 2.9.2 looks like in terms of suitability and stability.
> Is there
Wellington Chevreuil created HBASE-21784:
Summary: Dump replication queue should show list of wal files
ordered chronologically
Key: HBASE-21784
URL: https://issues.apache.org/jira/browse/HBASE-21784
I don't think we can drop support like that for minors per our compatibility
guidelines. I don't know how many run 2.7 or 2.8 in production. We use 2.7 so
for our own sake I'm -1 on this proposal. However we could change the default
2.x version we build against to 2.9.2. Shall we discuss that ?
yep! I agree that would be consistent with the previous consensus
position if that's what we want to do.
I'll try to take a look at the state of 2.8 and 2.9 and see if I can
answer your earlier question about "why not just go to for minimum 2.9
instead of 2.8?"
On Fri, Jan 25, 2019 at 1:22 PM
By that rationale, for 1.6.0, we could look at setting the minimum Hadoop
version to 2.8. I almost have 1.5.0 out the door and Hadoop hasn't
concluded the 2.7 EOL discussion yet.
On Fri, Jan 25, 2019 at 11:08 AM Sean Busbey wrote:
> it's dangerous to change our default build to be something
it's dangerous to change our default build to be something other than
the oldest version we claim works because devs are less likely to
notice when they make use of some new feature Hadoop added. It would
help with what we ship in convenience packages, provided we do some
reasonable testing of
+1
Earlier this came up as a need for cancelling individual procedures. The
capability to cancel a procedure was removed from the procedure framework
because it is hard to do reliably in all cases. It should at least be
possible to cancel and remove procedures that have not executed yet but are
in
Sergey Shelukhin created HBASE-21785:
Summary: master reports open regions as RITs and also messes up
rit age metric
Key: HBASE-21785
URL: https://issues.apache.org/jira/browse/HBASE-21785
I think one thing that is needed for HBCK2 for AMv2 is to be able to delete
single procedures from store.
We are evaluating master (whose assignment is very similar to branch-2) right
now and I have to delete proc WAL pretty much every day because some
procedure(s) are in bad state, but
that's already present, see the README for the "bypass" command:
https://github.com/apache/hbase-operator-tools/tree/master/hbase-hbck2
On Fri, Jan 25, 2019 at 3:40 PM Sergey Shelukhin
wrote:
>
> I think one thing that is needed for HBCK2 for AMv2 is to be able to delete
> single procedures
Sergey Shelukhin created HBASE-21786:
Summary: RIT for a region without a lock can mess up the RIT that
has the lock
Key: HBASE-21786
URL: https://issues.apache.org/jira/browse/HBASE-21786
Sergey Shelukhin created HBASE-21788:
Summary: OpenRegionProcedure (after recovery?) is unreliable and
needs to be improved
Key: HBASE-21788
URL: https://issues.apache.org/jira/browse/HBASE-21788
Sergey Shelukhin created HBASE-21787:
Summary: proc WAL replaces a RIT that holds a lock with a RIT that
doesn't
Key: HBASE-21787
URL: https://issues.apache.org/jira/browse/HBASE-21787
Project:
14 matches
Mail list logo
