Last call for changes for 0.98.11 is afternoon of 3/2 PST.
On Wed, Feb 25, 2015 at 2:27 PM, Andrew Purtell apurt...@apache.org wrote:
We already have 79 committed changes for it, looks like.
Please let me know if you have any concerns.
--
Best regards,
- Andy
Problems worthy of
stack created HBASE-13125:
-
Summary: Purge hbase.bucketcache.sizes from the refguide; no such
config (should be hbase.bucketcache.size?)
Key: HBASE-13125
URL: https://issues.apache.org/jira/browse/HBASE-13125
Sean Busbey created HBASE-13126:
---
Summary: Clean up API for unintended methods within non-private
classes.
Key: HBASE-13126
URL: https://issues.apache.org/jira/browse/HBASE-13126
Project: HBase
I don't think we have enough release managers or enough bandwidth as a
community to evaluate RC's for a monthly minor release cycle. My
understanding was that we'd continue doing patch releases on the monthly
cycle (RM's willing) and spin minor releases as we have new RM's volunteer.
I don't think
Hey folks!
Apologies if I've overlooked this getting discussed already. Do we have a
goal release cadence for minor versions out of branch-1?
My first gut reaction is that it should essentially match the cadence we've
been aiming at for the 0.98 line. That would mean attempting to match
monthly,
stack created HBASE-13127:
-
Summary: Add timeouts on all tests so less zombie sightings
Key: HBASE-13127
URL: https://issues.apache.org/jira/browse/HBASE-13127
Project: HBase
Issue Type: Improvement
I am planning on sticking to monthly release candidates for the 1.0.x
series of releases. The patches are somewhat controlled, so testing should
not be a huge effort.
However, 1.x series are expected to contain new features, and much more
change (1.1 already contains some big features on top of
Victoria created HBASE-13128:
Summary: Make HBCK's lock file retry creation and deletion
Key: HBASE-13128
URL: https://issues.apache.org/jira/browse/HBASE-13128
Project: HBase
Issue Type:
In hbase shell code, the following *HMasterCommandLine#startMaster* code
logic has been in the code forever :-). I just wonder what is the logic
behind it why it is the case for the error message (shell will not be
able to find this ZK quorum).
- start zookeeper cluster and return the active ZK