[jira] [Resolved] (HBASE-22749) Distributed MOB compactions

[ https://issues.apache.org/jira/browse/HBASE-22749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-22749. --- Resolution: Fixed > Distributed MOB compacti

[jira] [Resolved] (HBASE-24101) Correct snapshot handling

[ https://issues.apache.org/jira/browse/HBASE-24101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-24101. --- Resolution: Not A Problem > Correct snapshot handl

Re: [DISCUSS] New User Experience and Data Durability Guarantees on LocalFileSystem (HBASE-24086)

This should work for locally attached storage for sure. On Wed, Apr 15, 2020 at 3:52 PM Vladimir Rodionov wrote: > FileOutputStream.getFileChannel().force(true) will get all durability we > need. Just a simple code change? > > > On Wed, Apr 15, 2020 at 12:32 PM Andrew P

Re: [DISCUSS] New User Experience and Data Durability Guarantees on LocalFileSystem (HBASE-24086)

FileOutputStream.getFileChannel().force(true) will get all durability we need. Just a simple code change? On Wed, Apr 15, 2020 at 12:32 PM Andrew Purtell wrote: > This thread talks of “durability” via filesystem characteristics but also > for single system quick Start type deployments. For

Re: [DISCUSS] Arrange Events for 10-year Anniversary

2020 - 10 = 2010. As far as I remember I joined HBase community in 2009 :) and I am pretty sure that Mr. Stack did it even earlier. Best regards, Vlad On Wed, Apr 15, 2020 at 5:57 AM Yu Li wrote: > Dear all, > > Since our project has reached its 10th birthday, and 10 years is definitely > a

[jira] [Created] (HBASE-24101) Correct snapshot handling

Vladimir Rodionov created HBASE-24101: - Summary: Correct snapshot handling Key: HBASE-24101 URL: https://issues.apache.org/jira/browse/HBASE-24101 Project: HBase Issue Type: Sub-task

[jira] [Reopened] (HBASE-22749) Distributed MOB compactions

[ https://issues.apache.org/jira/browse/HBASE-22749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov reopened HBASE-22749: --- Reopening this umbrella to address correct snapshot handling > Distributed

[jira] [Resolved] (HBASE-23363) MobCompactionChore takes a long time to complete once job

[ https://issues.apache.org/jira/browse/HBASE-23363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-23363. --- Resolution: Won't Fix HBASE-22749 has introduced distributed MOB compaction, which

[jira] [Resolved] (HBASE-23840) Revert optimized IO back to general compaction during upgrade/migration process

[ https://issues.apache.org/jira/browse/HBASE-23840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-23840. --- Resolution: Fixed > Revert optimized IO back to general compaction during upgr

[jira] [Created] (HBASE-23840) Revert optimized IO backt to general compaction during upgrade/migration process

Vladimir Rodionov created HBASE-23840: - Summary: Revert optimized IO backt to general compaction during upgrade/migration process Key: HBASE-23840 URL: https://issues.apache.org/jira/browse/HBASE-23840

[jira] [Created] (HBASE-23724) Change code in StoreFileInfo to use regex matcher for mob files.

Vladimir Rodionov created HBASE-23724: - Summary: Change code in StoreFileInfo to use regex matcher for mob files. Key: HBASE-23724 URL: https://issues.apache.org/jira/browse/HBASE-23724 Project

[jira] [Created] (HBASE-23723) Add tests for MOB compaction on a table created from snapshot

Vladimir Rodionov created HBASE-23723: - Summary: Add tests for MOB compaction on a table created from snapshot Key: HBASE-23723 URL: https://issues.apache.org/jira/browse/HBASE-23723 Project

[jira] [Created] (HBASE-23571) Handle CompactType.MOB correctly

Vladimir Rodionov created HBASE-23571: - Summary: Handle CompactType.MOB correctly Key: HBASE-23571 URL: https://issues.apache.org/jira/browse/HBASE-23571 Project: HBase Issue Type: Sub

[jira] [Resolved] (HBASE-23189) Finalize I/O optimized MOB compaction

[ https://issues.apache.org/jira/browse/HBASE-23189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-23189. --- Resolution: Fixed > Finalize I/O optimized MOB compact

[jira] [Resolved] (HBASE-23267) Test case for MOB compaction in a regular mode.

[ https://issues.apache.org/jira/browse/HBASE-23267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-23267. --- Resolution: Fixed Resolved. Pushed to the parent's PR branch. > Test case for

[jira] [Created] (HBASE-23267) Test case for MOB compaction in a regular mode.

Vladimir Rodionov created HBASE-23267: - Summary: Test case for MOB compaction in a regular mode. Key: HBASE-23267 URL: https://issues.apache.org/jira/browse/HBASE-23267 Project: HBase

[jira] [Resolved] (HBASE-23266) Test case for MOB compaction in a region's batch mode.

[ https://issues.apache.org/jira/browse/HBASE-23266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-23266. --- Resolution: Fixed Resolved. Pushed change to parent's PR branch. > Test c

[jira] [Created] (HBASE-23266) Test case for MOB compaction in a region's batch mode.

Vladimir Rodionov created HBASE-23266: - Summary: Test case for MOB compaction in a region's batch mode. Key: HBASE-23266 URL: https://issues.apache.org/jira/browse/HBASE-23266 Project: HBase

[jira] [Resolved] (HBASE-23188) MobFileCleanerChore test case

[ https://issues.apache.org/jira/browse/HBASE-23188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-23188. --- Resolution: Fixed Resolved. Pushed to parent PR branch. > MobFileCleanerChore t

[jira] [Resolved] (HBASE-23190) Convert MobCompactionTest into integration test

[ https://issues.apache.org/jira/browse/HBASE-23190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-23190. --- Resolution: Fixed Resolved in a last parent PR commit (11/5). > Conv

[jira] [Resolved] (HBASE-23209) Simplify logic in DefaultMobStoreCompactor

[ https://issues.apache.org/jira/browse/HBASE-23209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-23209. --- Resolution: Fixed > Simplify logic in DefaultMobStoreCompac

[jira] [Created] (HBASE-23209) Simplify logic in DefaultMobStoreCompactor

Vladimir Rodionov created HBASE-23209: - Summary: Simplify logic in DefaultMobStoreCompactor Key: HBASE-23209 URL: https://issues.apache.org/jira/browse/HBASE-23209 Project: HBase Issue

[jira] [Created] (HBASE-23198) Documentation and release notes

Vladimir Rodionov created HBASE-23198: - Summary: Documentation and release notes Key: HBASE-23198 URL: https://issues.apache.org/jira/browse/HBASE-23198 Project: HBase Issue Type: Sub

[jira] [Created] (HBASE-23190) Convert MobCompactionTest into integration test

Vladimir Rodionov created HBASE-23190: - Summary: Convert MobCompactionTest into integration test Key: HBASE-23190 URL: https://issues.apache.org/jira/browse/HBASE-23190 Project: HBase

[jira] [Created] (HBASE-23189) Finalize generational compaction

Vladimir Rodionov created HBASE-23189: - Summary: Finalize generational compaction Key: HBASE-23189 URL: https://issues.apache.org/jira/browse/HBASE-23189 Project: HBase Issue Type: Sub

[jira] [Created] (HBASE-23188) MobFileCleanerChore test case

Vladimir Rodionov created HBASE-23188: - Summary: MobFileCleanerChore test case Key: HBASE-23188 URL: https://issues.apache.org/jira/browse/HBASE-23188 Project: HBase Issue Type: Sub-task

Re: [DISCUSS] Limiting gitbox PR email

No, good idea. -Vlad On Sat, Sep 28, 2019 at 10:17 AM Nick Dimiduk wrote: > Heya, > > I would like our dev@ subscription to gitbox notifications to match that > of > our JIRA notifications — just open, close of issues. Right now we’re > getting every comment. Like JIRA, users are able to

[jira] [Resolved] (HBASE-22826) Wrong FS: recovered.edits goes to wrong file system

[ https://issues.apache.org/jira/browse/HBASE-22826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-22826. --- Resolution: Won't Fix > Wrong FS: recovered.edits goes to wrong file sys

[jira] [Created] (HBASE-22826) Wrong FS: recovered.edits goes to wrong file system

Vladimir Rodionov created HBASE-22826: - Summary: Wrong FS: recovered.edits goes to wrong file system Key: HBASE-22826 URL: https://issues.apache.org/jira/browse/HBASE-22826 Project: HBase

[jira] [Created] (HBASE-22749) HBase MOB 2.0

Vladimir Rodionov created HBASE-22749: - Summary: HBase MOB 2.0 Key: HBASE-22749 URL: https://issues.apache.org/jira/browse/HBASE-22749 Project: HBase Issue Type: New Feature

Re: Can we remove OfflineMetaRepair in the master branch and branch-2+?

+1. It has always been obscure tool. On Wed, Jul 10, 2019 at 8:47 PM Toshihiro Suzuki wrote: > Hi folks! > > I think we no longer support OfflineMetaRepair in HBase-2.x and it has a > critical bug that breaks the meta data: > https://issues.apache.org/jira/browse/HBASE-21665 > > Actually, I

[jira] [Resolved] (HBASE-22205) Backport HBASE-21688 to 1.3+ branches

[ https://issues.apache.org/jira/browse/HBASE-22205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-22205. --- Resolution: Not A Problem > Backport HBASE-21688 to 1.3+ branc

[jira] [Created] (HBASE-22205) Backport HBASE-21688 to 1.3+ branches

Vladimir Rodionov created HBASE-22205: - Summary: Backport HBASE-21688 to 1.3+ branches Key: HBASE-22205 URL: https://issues.apache.org/jira/browse/HBASE-22205 Project: HBase Issue Type

Re: GetAndPut

Interesting. If CheckAndPut succeeds, then you know the value and no need for Get, right? Only if it fail, you want to know current value if CheckAndPut fails? Can you elaborate on your use case, Jean-Marc? -Vlad On Mon, Mar 25, 2019 at 11:54 AM Jean-Marc Spaggiari < jean-m...@spaggiari.org>

[jira] [Created] (HBASE-22075) Potential data loss when MOB compaction fails

Vladimir Rodionov created HBASE-22075: - Summary: Potential data loss when MOB compaction fails Key: HBASE-22075 URL: https://issues.apache.org/jira/browse/HBASE-22075 Project: HBase

[jira] [Resolved] (HBASE-21936) Disable split/merge of a table during snapshot

[ https://issues.apache.org/jira/browse/HBASE-21936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-21936. --- Resolution: Invalid > Disable split/merge of a table during snaps

[jira] [Created] (HBASE-21936) Disable split/merge of a table before taking snapshot

Vladimir Rodionov created HBASE-21936: - Summary: Disable split/merge of a table before taking snapshot Key: HBASE-21936 URL: https://issues.apache.org/jira/browse/HBASE-21936 Project: HBase

[jira] [Reopened] (HBASE-21688) Address WAL filesystem issues

[ https://issues.apache.org/jira/browse/HBASE-21688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov reopened HBASE-21688: --- Opened for amendment. > Address WAL filesystem iss

[jira] [Resolved] (HBASE-21457) BackupUtils#getWALFilesOlderThan refers to wrong FileSystem

[ https://issues.apache.org/jira/browse/HBASE-21457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-21457. --- Resolution: Fixed > BackupUtils#getWALFilesOlderThan refers to wrong FileSys

[jira] [Created] (HBASE-21688) Address WAL filesystem issues

Vladimir Rodionov created HBASE-21688: - Summary: Address WAL filesystem issues Key: HBASE-21688 URL: https://issues.apache.org/jira/browse/HBASE-21688 Project: HBase Issue Type: Bug

[jira] [Reopened] (HBASE-21457) BackupUtils#getWALFilesOlderThan refers to wrong FileSystem

[ https://issues.apache.org/jira/browse/HBASE-21457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov reopened HBASE-21457: --- Opened for addendum. > BackupUtils#getWALFilesOlderThan refers to wrong FileSys

Re: if changing the RingBuffer to priority Based Queue cause correctness issue in HBase?

Should be handled in RPC queues first, before mutation op reaches RingBuffer, I think. But to answer your question: the only guarantee HBase provide (promises) is strictly consistent writes and atomicity for a single row mutation. No, won't break anything. Permutations of mutations in an execution

[jira] [Created] (HBASE-21219) Hbase incremental backup fails with null pointer exception

Vladimir Rodionov created HBASE-21219: - Summary: Hbase incremental backup fails with null pointer exception Key: HBASE-21219 URL: https://issues.apache.org/jira/browse/HBASE-21219 Project: HBase

Re: Rough notes from dev meetup, day after hbaseconasia 2018, saturday morning

C* fares much better with their (very limited) CQL than HBase with its advanced Phoenix. Just saying. My 2c -Vlad On Mon, Aug 20, 2018 at 12:06 PM, Andrew Purtell wrote: > It would be helpful if someone could forward the relevant bits of Phoenix > discussion to the Phoenix dev list. One

[jira] [Created] (HBASE-21077) MR job launched by hbase incremental backup command failed with FileNotFoundException

Vladimir Rodionov created HBASE-21077: - Summary: MR job launched by hbase incremental backup command failed with FileNotFoundException Key: HBASE-21077 URL: https://issues.apache.org/jira/browse/HBASE-21077

[jira] [Created] (HBASE-20729) B BackupLogCleaner must ignore ProcV2 WAL files

Vladimir Rodionov created HBASE-20729: - Summary: B BackupLogCleaner must ignore ProcV2 WAL files Key: HBASE-20729 URL: https://issues.apache.org/jira/browse/HBASE-20729 Project: HBase

[jira] [Created] (HBASE-20631) B: Merge command enhancements

Vladimir Rodionov created HBASE-20631: - Summary: B: Merge command enhancements Key: HBASE-20631 URL: https://issues.apache.org/jira/browse/HBASE-20631 Project: HBase Issue Type: New

[jira] [Created] (HBASE-20630) B: Delete command enhancements

Vladimir Rodionov created HBASE-20630: - Summary: B: Delete command enhancements Key: HBASE-20630 URL: https://issues.apache.org/jira/browse/HBASE-20630 Project: HBase Issue Type: New

[jira] [Created] (HBASE-20547) Restore from backup will fail if done from a different file system

Vladimir Rodionov created HBASE-20547: - Summary: Restore from backup will fail if done from a different file system Key: HBASE-20547 URL: https://issues.apache.org/jira/browse/HBASE-20547 Project

[jira] [Resolved] (HBASE-15227) HBase Backup Phase 3: Fault tolerance (client/server) support

[ https://issues.apache.org/jira/browse/HBASE-15227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-15227. --- Resolution: Fixed Done. > HBase Backup Phase 3: Fault tolerance (client/ser

[jira] [Created] (HBASE-19969) Improve FT in merge operation

Vladimir Rodionov created HBASE-19969: - Summary: Improve FT in merge operation Key: HBASE-19969 URL: https://issues.apache.org/jira/browse/HBASE-19969 Project: HBase Issue Type: Sub-task

[jira] [Created] (HBASE-19568) Restore of HBase table using incremental backup doesn't restore rows from an earlier incremental backup

Vladimir Rodionov created HBASE-19568: - Summary: Restore of HBase table using incremental backup doesn't restore rows from an earlier incremental backup Key: HBASE-19568 URL: https://issues.apache.org/jira

Re: [DISCUSS] Plan to avoid backup/restore removal from 2.0

at 10:30 AM, Mike Drob <md...@apache.org> wrote: > The list is what Josh proposed in the original email to the list. > > What is the JIRA for #3? > > On Fri, Dec 1, 2017 at 12:20 PM, Vladimir Rodionov <vladrodio...@gmail.com > > > wrote: > > > Where did yo

Re: [DISCUSS] Plan to avoid backup/restore removal from 2.0

Nope, Mike. Fortunately, 99% of a FT code will remains after introducing concurrent sessions support Just two lines will be changed: TakeSnapshot -> BeginTX, RestoreSnapshot -> RollbackTx -Vlad On Thu, Nov 30, 2017 at 7:20 PM, Mike Drob wrote: > Bringing this thread up

[jira] [Reopened] (HBASE-16391) Multiple backup/restore sessions support

[ https://issues.apache.org/jira/browse/HBASE-16391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov reopened HBASE-16391: --- Assignee: Vladimir Rodionov > Multiple backup/restore sessions supp

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

>> CompletableFuture more and more in our code base, but at least before >>jdk8u131 there is a performance regression for CompletableFuture. The performance regression is 2x, so this should be something else On Tue, Nov 28, 2017 at 6:49 PM, 宾莉金（binlijin） wrote: >

Re: [DISCUSS] Performance degradation in master (compared to 2-alpha-1)

I do not know if this is related, but test suite for backup now runs 57 min on master. It used to run under 34 -Vlad On Tue, Nov 28, 2017 at 9:16 AM, Mike Drob wrote: > Eshcar - do you have time to try the other alpha releases and see where > exactly we introduced the

Re: Any Eclipse users among devs?

Sure I will try, Josh -Vlad On Thu, Nov 16, 2017 at 10:57 AM, Josh Elser wrote: > I still use Eclipse for most of my development and have been fighting it > being broken for branch-2 (ironically, as a result of some "fixes" I made > previously). > > Anyone with a setup who

Re: [DISCUSS] Plan to avoid backup/restore removal from 2.0

Thanks, Mike We will take a look. -Vlad On Mon, Nov 13, 2017 at 11:45 AM, Mike Drob wrote: > Sure, I don't think there are any issue with sharing this publicly, since > the code has only gone out in alpha releases. > > The suspect lines in IncrementalTableBackupClient are

Re: [DISCUSS] Plan to avoid backup/restore removal from 2.0

Yes, you are correct, Sean :) On Mon, Nov 13, 2017 at 10:16 AM, Sean Busbey <bus...@apache.org> wrote: > On Mon, Nov 13, 2017 at 11:46 AM, Vladimir Rodionov > <vladrodio...@gmail.com> wrote: > >>>Is there a high-level overview of what the feature should b

Re: [DISCUSS] Plan to avoid backup/restore removal from 2.0

>>Is there a high-level overview of what the feature should be able to do in >>hbase-2? (The issue HBASE-14414 has a bunch of issues hanging off it. It >>is hard to get an overview). Yes, it is in hbase book, Michael. HBASE-16754 >>Is there >>anything on what user can expect in terms of size

[jira] [Resolved] (HBASE-17133) Backup documentation update

[ https://issues.apache.org/jira/browse/HBASE-17133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-17133. --- Resolution: Duplicate Duplicate of HBASE-16574 > Backup documentation upd

[jira] [Created] (HBASE-19211) B: update configuration string in BackupRestoreConstants

Vladimir Rodionov created HBASE-19211: - Summary: B: update configuration string in BackupRestoreConstants Key: HBASE-19211 URL: https://issues.apache.org/jira/browse/HBASE-19211 Project: HBase

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

On doc, We have great doc attached to HBASE-7912 (unfortunately, it is a little bit obsolete now) On Thu, Nov 2, 2017 at 10:31 AM, Vladimir Rodionov <vladrodio...@gmail.com> wrote: > >>To be clear, I wasn't listing requirements. I was having trouble with > the > >&g

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

rephrase my statement: "I do not see how we can perform correct verification ..." On Thu, Nov 2, 2017 at 9:20 AM, Stack <st...@duboce.net> wrote: > On Thu, Nov 2, 2017 at 5:51 AM, Josh Elser <els...@apache.org> wrote: > > > On 11/1/17 11:33 PM, Stack wro

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

restore feature > yet, could you help me out on getting a foothold? > > Which of these Backup/Restore options is it we're specifically talking > about: > > http://hbase.apache.org/book.html#ops.backup > > > > On Wed, Nov 1, 2017 at 1:33 PM, Vladimir Rodionov > &l

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

ing anything in (5) will be counter-productive. > > I'd appreciate if the summary is followed by opinions, and not mixed > > together. > > > > Just a suggestion which can help you get right attention. > > Thanks. > > > > -- Appy > > > > > > > &g

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

gt; >> On Wed, Nov 1, 2017 at 12:25 PM, Vladimir Rodionov<vladrodio...@gmail.com >> > >> wrote: >> >> 1. HBASE-19104 - 19109 >>> >>> None of them are basic, Stack. These requests came from SF after >>> discussion >>> we had with

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

onducted independent testing and found no > issues with a functionality to my best knowledge." > > That's not true, we found issues and filed JIRAs. As to how significant > they are or not, I defer to the JIRAs for discussion. > > > On Wed, Nov 1, 2017 at 12:17 PM, Vladimir Rodionov <vla

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

quot;backup" 3. We make no assumptions on assignment order of these tables. As for real scale testing and documentation , we still have time before 2.0GA. Can't be blocker IMO On Wed, Nov 1, 2017 at 12:17 PM, Vladimir Rodionov <vladrodio...@gmail.com> wrote: > >>I dont' w

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

>>I dont' want to get drawn into another unfriendly argument, but this is >>simply not true. We filed a bunch of JIRAs including one with serious >>concerns about scalability. Can you explain please how did you guys manage to file multiple JIRAs (trivials mostly) without testing backup/restore?

[jira] [Created] (HBASE-19149) Improve backup/restore progress indicator

Vladimir Rodionov created HBASE-19149: - Summary: Improve backup/restore progress indicator Key: HBASE-19149 URL: https://issues.apache.org/jira/browse/HBASE-19149 Project: HBase Issue

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

>> hbase-backup: Not done and it doesn't look like it will be done for beta-1. >>It can come in later in a 2.1 or 3.0 when it is finished. That is not correct. All blockers have been resolved, the last one has a patch which is ready to be commited. Salesforce team has conducted independent

[jira] [Created] (HBASE-19006) Fix TestIncrementalBackupWithBulkLoad under hadoop3

Vladimir Rodionov created HBASE-19006: - Summary: Fix TestIncrementalBackupWithBulkLoad under hadoop3 Key: HBASE-19006 URL: https://issues.apache.org/jira/browse/HBASE-19006 Project: HBase

[jira] [Created] (HBASE-18975) B hadoop3 incompatibility

Vladimir Rodionov created HBASE-18975: - Summary: B hadoop3 incompatibility Key: HBASE-18975 URL: https://issues.apache.org/jira/browse/HBASE-18975 Project: HBase Issue Type: Bug

[jira] [Created] (HBASE-18892) B testing

Vladimir Rodionov created HBASE-18892: - Summary: B testing Key: HBASE-18892 URL: https://issues.apache.org/jira/browse/HBASE-18892 Project: HBase Issue Type: Umbrella

Re: [DISCUSS] Becoming a Committer

umber of commits, LOC changed, number of > JIRAs, and such. If you are such a paid professional, sure, it's no problem > for you, but you're already getting paid to be here. > > > On Wed, Sep 20, 2017 at 3:57 PM, Vladimir Rodionov <vladrodio...@gmail.com > > > ​ ​ > wrote: >

Re: [DISCUSS] Becoming a Committer

approach with almost no room for power abuse -Vlad On Wed, Sep 20, 2017 at 3:57 PM, Vladimir Rodionov <vladrodio...@gmail.com> wrote: > Any subjective criteria, such as "acting like a committer" open wide room > for а power abuse of PMC members. > > My 2c > &

Re: [DISCUSS] Becoming a Committer

Any subjective criteria, such as "acting like a committer" open wide room for а power abuse of PMC members. My 2c -Vlad On Wed, Sep 20, 2017 at 3:05 PM, Andrew Purtell wrote: > By the way I think "act like a committer and you'll become a committer" is > pretty good advice

[jira] [Created] (HBASE-18843) Add DistCp support to incremental backup with bulk loading

Vladimir Rodionov created HBASE-18843: - Summary: Add DistCp support to incremental backup with bulk loading Key: HBASE-18843 URL: https://issues.apache.org/jira/browse/HBASE-18843 Project: HBase

[jira] [Reopened] (HBASE-14417) Incremental backup and bulk loading

[ https://issues.apache.org/jira/browse/HBASE-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov reopened HBASE-14417: --- Assignee: Vladimir Rodionov (was: Ted Yu) > Incremental backup and bulk load

Re: [DISCUSS] Plan for Distributed testing of Backup and Restore

g/apache/hadoop/hbase/ > IntegrationTestBackupRestore.java > > On Tue, Sep 12, 2017 at 11:25 AM, Vladimir Rodionov < > vladrodio...@gmail.com> > wrote: > > > >> Vlad: I'm obviously curious to see what you think about this stuff, in > > addition to what you alrea

Re: [DISCUSS] Plan for Distributed testing of Backup and Restore

>> Vlad: I'm obviously curious to see what you think about this stuff, in addition to what you already had in mind :) Yes, I think that we need a test tool similar to ITBLL. Btw, making backup working in challenging conditions was not a goal of FT design, correct failure handling was a goal. On

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

* I would feel quite dejected if some feature I spent a year+ working > on (*not* making assertions on my perception of quality) was removed > from the release line it was expected to land. > > > S > > > > On Sep 8, 2017 10:59 PM, "Vladimir Rodionov" <vladrodio...

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

ings need doing first. > > > On Sep 9, 2017, at 5:25 PM, Vladimir Rodionov <vladrodio...@gmail.com> > wrote: > > >>> but the impression we have is it is unfinished and untested. > > To make a conclusion that "feature is not finished and tested" you have

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

IMHO is for the developers of this feature to complete those > unfinished JIRAs, especially concerning resilience to failures. > > > > On Sep 9, 2017, at 4:11 PM, Vladimir Rodionov <vladrodio...@gmail.com> > wrote: > > > > Hmm, the next on your list (of kicked out

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

into a release. Unless > the work is done to convince me that backup/restore is more than a lump of > code and a few unit tests that can pass on some fellows laptop, I am going > to kick it out of branch-2. Let the feature harden more in master branch > before it ships in a release.

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

>> Have I grasped the state of things correctly, Vlad? Josh, the only thing which is still pending is doc update. All other features are good to have but not a blockers for 2.0 release. -Vlad On Fri, Sep 8, 2017 at 10:42 PM, Vladimir Rodionov <vladrodio...@gmail.com> wrote: >

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

>> What testing and at what >> scale has testing been done? Do we have have that for other features? On Fri, Sep 8, 2017 at 10:41 PM, Vladimir Rodionov <vladrodio...@gmail.com> wrote: > >> It asks: "How do I figure what of backup/restore feature is going to

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

summaries: "Add nonce support to TableBackupProcedure, BackupID must > include backup set name, ...". The last comment in that issue is from July. > It asks: "How do I figure what of backup/restore feature is going to be in > hbase-2.0.0? Thanks Vladimir Rodionov > <

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

All blockers have been resolved. Some remaining JIRAs are good to have but are not a blockers On Fri, Sep 8, 2017 at 1:59 PM, Vladimir Rodionov <vladrodio...@gmail.com> wrote: > HBASE-14414 > > On Fri, Sep 8, 2017 at 1:14 PM, Stack <st...@duboce.net> wrote: > >> Wh

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

> > Thanks, > S > > > > On Wed, Nov 23, 2016 at 8:52 AM, Stack <st...@duboce.net> wrote: > > > On Tue, Nov 22, 2016 at 6:48 PM, Stack <st...@duboce.net> wrote: > > > >> On Tue, Nov 22, 2016 at 3:17 PM, Vladimir Rodionov < > >>

[jira] [Created] (HBASE-18646) [Backup] LogRollMasterProcedureManager: make procedure timeout, thread pool size configurable

Vladimir Rodionov created HBASE-18646: - Summary: [Backup] LogRollMasterProcedureManager: make procedure timeout, thread pool size configurable Key: HBASE-18646 URL: https://issues.apache.org/jira/browse/HBASE

Re: Bug in FIFOCompactionPolicy pre-checks?

Yes, file a JIRA, Lars I will take a look -Vlad On Thu, Aug 3, 2017 at 11:41 PM, Lars George wrote: > Hi, > > See https://issues.apache.org/jira/browse/HBASE-14468 > > It adds this check to {{HMaster.checkCompactionPolicy()}}: > > {code} > // 1. Check TTL > if

[jira] [Resolved] (HBASE-7912) HBase Backup/Restore Based on HBase Snapshot

[ https://issues.apache.org/jira/browse/HBASE-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-7912. -- Resolution: Fixed Closing this one. Refer to https://issues.apache.org/jira/browse

[jira] [Created] (HBASE-18425) Fix TestMasterFailover

Vladimir Rodionov created HBASE-18425: - Summary: Fix TestMasterFailover Key: HBASE-18425 URL: https://issues.apache.org/jira/browse/HBASE-18425 Project: HBase Issue Type: Sub-task

[jira] [Created] (HBASE-18424) Fix TestAsyncTableGetMultiThreaded

Vladimir Rodionov created HBASE-18424: - Summary: Fix TestAsyncTableGetMultiThreaded Key: HBASE-18424 URL: https://issues.apache.org/jira/browse/HBASE-18424 Project: HBase Issue Type: Sub

[jira] [Created] (HBASE-18423) Fix TestMetaWithReplicas

Vladimir Rodionov created HBASE-18423: - Summary: Fix TestMetaWithReplicas Key: HBASE-18423 URL: https://issues.apache.org/jira/browse/HBASE-18423 Project: HBase Issue Type: Sub-task

[jira] [Created] (HBASE-18422) Fix TestRegionRebalancing

Vladimir Rodionov created HBASE-18422: - Summary: Fix TestRegionRebalancing Key: HBASE-18422 URL: https://issues.apache.org/jira/browse/HBASE-18422 Project: HBase Issue Type: Sub-task

[jira] [Reopened] (HBASE-16458) Shorten backup / restore test execution time

[ https://issues.apache.org/jira/browse/HBASE-16458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov reopened HBASE-16458: --- > Shorten backup / restore test execution t

  1   2   3   4   5   6   7   >