On 9/11/17 11:52 PM, Stack wrote:
On Mon, Sep 11, 2017 at 11:07 AM, Vladimir Rodionov <[email protected]>
wrote:
<snip/>
My plan is to finish HBASE-17825 (further performance optimizations). This
will cut down number of MR jobs during incremental backup
from 2*N to 2 (N - number of tables). That will probably take 2-3 more
days
Unless you have this patch ready to go already, could I convince you to
temporarily pause work on HBASE-17825 to take up the 3 points you've
outlined immediately below?
We can treat the optimization as a one-off instead of lumping it in with
the B&R feature at-large.
Then:
1. Address remaining two sub-tasks in HBASE-15227
2. Update Release notes for all relevant B&R JIRAs
3. Work on doc
After that we can call it feature full complete. Taking into account the
vast amount of efforts
spent on this feature (including QA testing) I would say that we are
probably quite close to GA right now, but only
after real testing is done (I do not anticipate significant issues, except
probably correct failure handling).
On a feature itself. We provide tools to fully automate backup and restore
tasks: create backup (full and incremental), restore
from image, delete backups, merge backups, history, history per table,
backup set management.
Hopefully, my write up addresses at least some of your concerns.
Thanks for updating us (community) w/ status. Completion of HA seems
important as is result of the scale testing.
As we're quickly approaching that beta-1 mark, I think it would be in
our combined best-interest to knock out what we have identified as
blockers. While these items aren't "significant" (read-as: not feature
work), they are still risks to the beta "train". We should prioritize
de-risking ourselves as much as possible.
After we finish that up (or in parallel), we can look at getting some
scale testing done. Let me spin out another thread to discuss the
concrete details on that one.
- Josh
