[jira] [Created] (HBASE-17842) Reference book - HBase application integration test is not correct
Iraj Hedayati created HBASE-17842: - Summary: Reference book - HBase application integration test is not correct Key: HBASE-17842 URL: https://issues.apache.org/jira/browse/HBASE-17842 Project: HBase Issue Type: Bug Components: documentation Reporter: Iraj Hedayati Priority: Critical The directions in the following section are not correct. https://archive.cloudera.com/cdh5/cdh/5/hbase-1.2.0-cdh5.8.0/book.html#_integration_testing_with_an_hbase_mini_cluster It is pointing to HBase 0.98.3 and `HBaseTestingUtility` can not be resolved in 1.2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Successful: hbase.apache.org HTML Checker
Successful If successful, the HTML and link-checking report for http://hbase.apache.org is available at https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/88/artifact/link_report/index.html. If failed, see https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/88/console.
Re: How threads interact with each other in HBase
The attachment can be found in the following URL: http://pages.cs.wisc.edu/~suli/hbase.pdf Sorry for the inconvenience... On Mon, Mar 27, 2017 at 8:25 PM, Ted Yuwrote: > Again, attachment didn't come thru. > > Is it possible to formulate as google doc ? > > Thanks > > On Mon, Mar 27, 2017 at 6:19 PM, 杨苏立 Yang Su Li > wrote: > > > Hi, > > > > I am a graduate student working on scheduling on storage systems, and we > > are interested in how different threads in HBase interact with each other > > and how it might affect scheduling. > > > > I have written down my understanding on how HBase/HDFS works based on its > > current thread architecture (attached). I am wondering if the developers > of > > HBase could take a look at it and let me know if anything is incorrect or > > inaccurate, or if I have missed anything. > > > > Thanks a lot for your help! > > > > On Wed, Mar 22, 2017 at 3:39 PM, 杨苏立 Yang Su Li > > wrote: > > > >> Hi, > >> > >> I am a graduate student working on scheduling on storage systems, and we > >> are interested in how different threads in HBase interact with each > other > >> and how it might affect scheduling. > >> > >> I have written down my understanding on how HBase/HDFS works based on > its > >> current thread architecture (attached). I am wondering if the > developers of > >> HBase could take a look at it and let me know if anything is incorrect > or > >> inaccurate, or if I have missed anything. > >> > >> Thanks a lot for your help! > >> > >> -- > >> Suli Yang > >> > >> Department of Physics > >> University of Wisconsin Madison > >> > >> 4257 Chamberlin Hall > >> Madison WI 53703 > >> > >> > > > > > > -- > > Suli Yang > > > > Department of Physics > > University of Wisconsin Madison > > > > 4257 Chamberlin Hall > > Madison WI 53703 > > > > > -- Suli Yang Department of Physics University of Wisconsin Madison 4257 Chamberlin Hall Madison WI 53703
[jira] [Resolved] (HBASE-17841) ServerCrashProcedure is not triggered when meta server with unflushed edits is aborted
[ https://issues.apache.org/jira/browse/HBASE-17841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved HBASE-17841. Resolution: Cannot Reproduce The sample test didn't reflect setup for master branch where master hosts meta region. > ServerCrashProcedure is not triggered when meta server with unflushed edits > is aborted > -- > > Key: HBASE-17841 > URL: https://issues.apache.org/jira/browse/HBASE-17841 > Project: HBase > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Ted Yu > Attachments: 17841.tst > > > When writing unit test for HBASE-17287, I noticed that the wait for master to > come down after hdfs enters safe mode times out (where meta server still has > unflushed edits). > The same test in branch-1 passes fine. > Looking at > org.apache.hadoop.hbase.master.procedure.TestSafemodeBringsDownMaster-output.txt > , I don't see occurrence of ServerCrashProcedure. > While in branch-1, there is something similar to the following: > {code} > at org.apache.hadoop.hdfs.DFSClient.rename(DFSClient.java:1661) > at > org.apache.hadoop.hdfs.DistributedFileSystem.rename(DistributedFileSystem.java:525) > at > org.apache.hadoop.hbase.master.MasterFileSystem.getLogDirs(MasterFileSystem.java:364) > at > org.apache.hadoop.hbase.master.MasterFileSystem.splitLog(MasterFileSystem.java:429) > at > org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:343) > at > org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:334) > at > org.apache.hadoop.hbase.master.procedure.ServerCrashProcedure.processMeta(ServerCrashProcedure.java:351) > at > org.apache.hadoop.hbase.master.procedure.ServerCrashProcedure.executeFromState(ServerCrashProcedure.java:239) > at > org.apache.hadoop.hbase.master.procedure.ServerCrashProcedure.executeFromState(ServerCrashProcedure.java:73) > at > org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:139) > at > org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:506) > at > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1152) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: How threads interact with each other in HBase
Again, attachment didn't come thru. Is it possible to formulate as google doc ? Thanks On Mon, Mar 27, 2017 at 6:19 PM, 杨苏立 Yang Su Liwrote: > Hi, > > I am a graduate student working on scheduling on storage systems, and we > are interested in how different threads in HBase interact with each other > and how it might affect scheduling. > > I have written down my understanding on how HBase/HDFS works based on its > current thread architecture (attached). I am wondering if the developers of > HBase could take a look at it and let me know if anything is incorrect or > inaccurate, or if I have missed anything. > > Thanks a lot for your help! > > On Wed, Mar 22, 2017 at 3:39 PM, 杨苏立 Yang Su Li > wrote: > >> Hi, >> >> I am a graduate student working on scheduling on storage systems, and we >> are interested in how different threads in HBase interact with each other >> and how it might affect scheduling. >> >> I have written down my understanding on how HBase/HDFS works based on its >> current thread architecture (attached). I am wondering if the developers of >> HBase could take a look at it and let me know if anything is incorrect or >> inaccurate, or if I have missed anything. >> >> Thanks a lot for your help! >> >> -- >> Suli Yang >> >> Department of Physics >> University of Wisconsin Madison >> >> 4257 Chamberlin Hall >> Madison WI 53703 >> >> > > > -- > Suli Yang > > Department of Physics > University of Wisconsin Madison > > 4257 Chamberlin Hall > Madison WI 53703 > >
Re: How threads interact with each other in HBase
Hi, I am a graduate student working on scheduling on storage systems, and we are interested in how different threads in HBase interact with each other and how it might affect scheduling. I have written down my understanding on how HBase/HDFS works based on its current thread architecture (attached). I am wondering if the developers of HBase could take a look at it and let me know if anything is incorrect or inaccurate, or if I have missed anything. Thanks a lot for your help! On Wed, Mar 22, 2017 at 3:39 PM, 杨苏立 Yang Su Liwrote: > Hi, > > I am a graduate student working on scheduling on storage systems, and we > are interested in how different threads in HBase interact with each other > and how it might affect scheduling. > > I have written down my understanding on how HBase/HDFS works based on its > current thread architecture (attached). I am wondering if the developers of > HBase could take a look at it and let me know if anything is incorrect or > inaccurate, or if I have missed anything. > > Thanks a lot for your help! > > -- > Suli Yang > > Department of Physics > University of Wisconsin Madison > > 4257 Chamberlin Hall > Madison WI 53703 > > -- Suli Yang Department of Physics University of Wisconsin Madison 4257 Chamberlin Hall Madison WI 53703
Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Congrats and welcome! Jerry
[jira] [Created] (HBASE-17841) ServerCrashProcedure is not triggered when meta server with unflushed edits is aborted
Ted Yu created HBASE-17841: -- Summary: ServerCrashProcedure is not triggered when meta server with unflushed edits is aborted Key: HBASE-17841 URL: https://issues.apache.org/jira/browse/HBASE-17841 Project: HBase Issue Type: Bug Affects Versions: 2.0 Reporter: Ted Yu When writing unit test for HBASE-17287, I noticed that the wait for master to come down after hdfs enters safe mode times out (where meta server still has unflushed edits). The same test in branch-1 passes fine. Looking at org.apache.hadoop.hbase.master.procedure.TestSafemodeBringsDownMaster-output.txt , I don't see occurrence of ServerCrashProcedure. While in branch-1, there is something similar to the following: {code} at org.apache.hadoop.hdfs.DFSClient.rename(DFSClient.java:1661) at org.apache.hadoop.hdfs.DistributedFileSystem.rename(DistributedFileSystem.java:525) at org.apache.hadoop.hbase.master.MasterFileSystem.getLogDirs(MasterFileSystem.java:364) at org.apache.hadoop.hbase.master.MasterFileSystem.splitLog(MasterFileSystem.java:429) at org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:343) at org.apache.hadoop.hbase.master.MasterFileSystem.splitMetaLog(MasterFileSystem.java:334) at org.apache.hadoop.hbase.master.procedure.ServerCrashProcedure.processMeta(ServerCrashProcedure.java:351) at org.apache.hadoop.hbase.master.procedure.ServerCrashProcedure.executeFromState(ServerCrashProcedure.java:239) at org.apache.hadoop.hbase.master.procedure.ServerCrashProcedure.executeFromState(ServerCrashProcedure.java:73) at org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:139) at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:506) at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1152) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17840) Update book
Josh Elser created HBASE-17840: -- Summary: Update book Key: HBASE-17840 URL: https://issues.apache.org/jira/browse/HBASE-17840 Project: HBase Issue Type: Sub-task Reporter: Josh Elser Assignee: Josh Elser Need to update the book to include the new feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Successful: HBase Generate Website
Build status: Successful If successful, the website and docs have been generated. To update the live site, follow the instructions below. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around permanently, you can skip the clone step. git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git cd hbase-site wget -O- https://builds.apache.org/job/hbase_generate_website/546/artifact/website.patch.zip | funzip > 4b62a52ebcf401d872e6872cf25bdb4556758983.patch git fetch git checkout -b asf-site-4b62a52ebcf401d872e6872cf25bdb4556758983 origin/asf-site git am --whitespace=fix 4b62a52ebcf401d872e6872cf25bdb4556758983.patch At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local asf-site-4b62a52ebcf401d872e6872cf25bdb4556758983 branch. There are lots of spurious changes, such as timestamps and CSS styles in tables, so a generic git diff is not very useful. To see a list of files that have been added, deleted, renamed, changed type, or are otherwise interesting, use the following command: git diff --name-status --diff-filter=ADCRTXUB origin/asf-site To see only files that had 100 or more lines changed: git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}' When you are satisfied, publish your changes to origin/asf-site using these commands: git commit --allow-empty -m "Empty commit" # to work around a current ASF INFRA bug git push origin asf-site-4b62a52ebcf401d872e6872cf25bdb4556758983:asf-site git checkout asf-site git branch -D asf-site-4b62a52ebcf401d872e6872cf25bdb4556758983 Changes take a couple of minutes to be propagated. You can verify whether they have been propagated by looking at the Last Published date at the bottom of http://hbase.apache.org/. It should match the date in the index.html on the asf-site branch in Git. As a courtesy- reply-all to this email to let other committers know you pushed the site. If failed, see https://builds.apache.org/job/hbase_generate_website/546/console
[jira] [Resolved] (HBASE-17830) [C++] Test Util support for standlone HBase instance
[ https://issues.apache.org/jira/browse/HBASE-17830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar resolved HBASE-17830. --- Resolution: Fixed Fix Version/s: HBASE-14850 Pushed this to branch. Thanks Sudeep. > [C++] Test Util support for standlone HBase instance > > > Key: HBASE-17830 > URL: https://issues.apache.org/jira/browse/HBASE-17830 > Project: HBase > Issue Type: Sub-task >Reporter: Sudeep Sunthankar >Assignee: Sudeep Sunthankar > Fix For: HBASE-14850 > > Attachments: HBASE-17830.HBASE-14850.v1.patch > > > Running standalone instance was removed from TestUtil after introduction of > mini cluster. We are re-introducing methods to run a standalone instance if > reqd. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Successful: HBase Generate Website
Build status: Successful If successful, the website and docs have been generated. To update the live site, follow the instructions below. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around permanently, you can skip the clone step. git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git cd hbase-site wget -O- https://builds.apache.org/job/hbase_generate_website/545/artifact/website.patch.zip | funzip > 85fda44179c0afba74f52944ae9bb5a38266678c.patch git fetch git checkout -b asf-site-85fda44179c0afba74f52944ae9bb5a38266678c origin/asf-site git am --whitespace=fix 85fda44179c0afba74f52944ae9bb5a38266678c.patch At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local asf-site-85fda44179c0afba74f52944ae9bb5a38266678c branch. There are lots of spurious changes, such as timestamps and CSS styles in tables, so a generic git diff is not very useful. To see a list of files that have been added, deleted, renamed, changed type, or are otherwise interesting, use the following command: git diff --name-status --diff-filter=ADCRTXUB origin/asf-site To see only files that had 100 or more lines changed: git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}' When you are satisfied, publish your changes to origin/asf-site using these commands: git commit --allow-empty -m "Empty commit" # to work around a current ASF INFRA bug git push origin asf-site-85fda44179c0afba74f52944ae9bb5a38266678c:asf-site git checkout asf-site git branch -D asf-site-85fda44179c0afba74f52944ae9bb5a38266678c Changes take a couple of minutes to be propagated. You can verify whether they have been propagated by looking at the Last Published date at the bottom of http://hbase.apache.org/. It should match the date in the index.html on the asf-site branch in Git. As a courtesy- reply-all to this email to let other committers know you pushed the site. If failed, see https://builds.apache.org/job/hbase_generate_website/545/console
Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Congrats and welcome. Enis On Mon, Mar 27, 2017 at 9:23 AM, Stephen Jiangwrote: > Great! Congratulations and welcome to the team! > > Thanks > Stephen > > On Mon, Mar 27, 2017 at 8:53 AM, Andrew Purtell > wrote: > > > Congratulations and welcome! > > > > > On Mar 27, 2017, at 5:37 AM, ramkrishna vasudevan < > > ramkrishna.s.vasude...@gmail.com> wrote: > > > > > > Hi All > > > > > > Welcome Anastasia Braginsky, one more female committer to HBase. She > has > > > been active now for a while with her Compacting memstore feature and > she > > > along with Eshcar have done lot of talks in various meetups and > HBaseCon > > on > > > their feature. > > > > > > Welcome onboard and looking forward to work with you Anastasia !!! > > > > > > Regards > > > Ram > > >
Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Great! Congratulations and welcome to the team! Thanks Stephen On Mon, Mar 27, 2017 at 8:53 AM, Andrew Purtellwrote: > Congratulations and welcome! > > > On Mar 27, 2017, at 5:37 AM, ramkrishna vasudevan < > ramkrishna.s.vasude...@gmail.com> wrote: > > > > Hi All > > > > Welcome Anastasia Braginsky, one more female committer to HBase. She has > > been active now for a while with her Compacting memstore feature and she > > along with Eshcar have done lot of talks in various meetups and HBaseCon > on > > their feature. > > > > Welcome onboard and looking forward to work with you Anastasia !!! > > > > Regards > > Ram >
Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Congratulations and welcome! > On Mar 27, 2017, at 5:37 AM, ramkrishna vasudevan >wrote: > > Hi All > > Welcome Anastasia Braginsky, one more female committer to HBase. She has > been active now for a while with her Compacting memstore feature and she > along with Eshcar have done lot of talks in various meetups and HBaseCon on > their feature. > > Welcome onboard and looking forward to work with you Anastasia !!! > > Regards > Ram
Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Congrats Anastasia! On Mon, Mar 27, 2017 at 7:37 AM, ramkrishna vasudevanwrote: > Hi All > > Welcome Anastasia Braginsky, one more female committer to HBase. She has > been active now for a while with her Compacting memstore feature and she > along with Eshcar have done lot of talks in various meetups and HBaseCon on > their feature. > > Welcome onboard and looking forward to work with you Anastasia !!! > > Regards > Ram
Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Congrats and Welcome Anastasia!
Successful: HBase Generate Website
Build status: Successful If successful, the website and docs have been generated. To update the live site, follow the instructions below. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around permanently, you can skip the clone step. git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git cd hbase-site wget -O- https://builds.apache.org/job/hbase_generate_website/544/artifact/website.patch.zip | funzip > c77e2135db07b6417f5fea4577c2c7ae8d6d7008.patch git fetch git checkout -b asf-site-c77e2135db07b6417f5fea4577c2c7ae8d6d7008 origin/asf-site git am --whitespace=fix c77e2135db07b6417f5fea4577c2c7ae8d6d7008.patch At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local asf-site-c77e2135db07b6417f5fea4577c2c7ae8d6d7008 branch. There are lots of spurious changes, such as timestamps and CSS styles in tables, so a generic git diff is not very useful. To see a list of files that have been added, deleted, renamed, changed type, or are otherwise interesting, use the following command: git diff --name-status --diff-filter=ADCRTXUB origin/asf-site To see only files that had 100 or more lines changed: git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}' When you are satisfied, publish your changes to origin/asf-site using these commands: git commit --allow-empty -m "Empty commit" # to work around a current ASF INFRA bug git push origin asf-site-c77e2135db07b6417f5fea4577c2c7ae8d6d7008:asf-site git checkout asf-site git branch -D asf-site-c77e2135db07b6417f5fea4577c2c7ae8d6d7008 Changes take a couple of minutes to be propagated. You can verify whether they have been propagated by looking at the Last Published date at the bottom of http://hbase.apache.org/. It should match the date in the index.html on the asf-site branch in Git. As a courtesy- reply-all to this email to let other committers know you pushed the site. If failed, see https://builds.apache.org/job/hbase_generate_website/544/console
Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Congrats and Welcome! Best Regards, Yu On 27 March 2017 at 20:57, ashish singhiwrote: > Congrats and Welcome! > > -Original Message- > From: ramkrishna vasudevan [mailto:ramkrishna.s.vasude...@gmail.com] > Sent: 27 March 2017 18:08 > To: dev@hbase.apache.org; u...@hbase.apache.org > Subject: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky > > Hi All > > Welcome Anastasia Braginsky, one more female committer to HBase. She has > been active now for a while with her Compacting memstore feature and she > along with Eshcar have done lot of talks in various meetups and HBaseCon on > their feature. > > Welcome onboard and looking forward to work with you Anastasia !!! > > Regards > Ram >
[jira] [Created] (HBASE-17839) "Data Model" section: Table 1 has only 5 data rows instead 6.
Evgeny Kincharov created HBASE-17839: Summary: "Data Model" section: Table 1 has only 5 data rows instead 6. Key: HBASE-17839 URL: https://issues.apache.org/jira/browse/HBASE-17839 Project: HBase Issue Type: Bug Components: documentation Affects Versions: 2.0.0 Reporter: Evgeny Kincharov Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.15#6346)
RE: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Congrats and Welcome! -Original Message- From: ramkrishna vasudevan [mailto:ramkrishna.s.vasude...@gmail.com] Sent: 27 March 2017 18:08 To: dev@hbase.apache.org; u...@hbase.apache.org Subject: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky Hi All Welcome Anastasia Braginsky, one more female committer to HBase. She has been active now for a while with her Compacting memstore feature and she along with Eshcar have done lot of talks in various meetups and HBaseCon on their feature. Welcome onboard and looking forward to work with you Anastasia !!! Regards Ram
Successful: HBase Generate Website
Build status: Successful If successful, the website and docs have been generated. To update the live site, follow the instructions below. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around permanently, you can skip the clone step. git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git cd hbase-site wget -O- https://builds.apache.org/job/hbase_generate_website/543/artifact/website.patch.zip | funzip > 04fc455037c3aa03e28c43aa2ca0668278501863.patch git fetch git checkout -b asf-site-04fc455037c3aa03e28c43aa2ca0668278501863 origin/asf-site git am --whitespace=fix 04fc455037c3aa03e28c43aa2ca0668278501863.patch At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local asf-site-04fc455037c3aa03e28c43aa2ca0668278501863 branch. There are lots of spurious changes, such as timestamps and CSS styles in tables, so a generic git diff is not very useful. To see a list of files that have been added, deleted, renamed, changed type, or are otherwise interesting, use the following command: git diff --name-status --diff-filter=ADCRTXUB origin/asf-site To see only files that had 100 or more lines changed: git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}' When you are satisfied, publish your changes to origin/asf-site using these commands: git commit --allow-empty -m "Empty commit" # to work around a current ASF INFRA bug git push origin asf-site-04fc455037c3aa03e28c43aa2ca0668278501863:asf-site git checkout asf-site git branch -D asf-site-04fc455037c3aa03e28c43aa2ca0668278501863 Changes take a couple of minutes to be propagated. You can verify whether they have been propagated by looking at the Last Published date at the bottom of http://hbase.apache.org/. It should match the date in the index.html on the asf-site branch in Git. As a courtesy- reply-all to this email to let other committers know you pushed the site. If failed, see https://builds.apache.org/job/hbase_generate_website/543/console
Re: [ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Congrats and Welcome Anastasia ! -Anoop- On Mon, Mar 27, 2017 at 6:07 PM, ramkrishna vasudevanwrote: > Hi All > > Welcome Anastasia Braginsky, one more female committer to HBase. She has > been active now for a while with her Compacting memstore feature and she > along with Eshcar have done lot of talks in various meetups and HBaseCon on > their feature. > > Welcome onboard and looking forward to work with you Anastasia !!! > > Regards > Ram
[ANNOUNCE] - Welcome our new HBase committer Anastasia Braginsky
Hi All Welcome Anastasia Braginsky, one more female committer to HBase. She has been active now for a while with her Compacting memstore feature and she along with Eshcar have done lot of talks in various meetups and HBaseCon on their feature. Welcome onboard and looking forward to work with you Anastasia !!! Regards Ram
[jira] [Resolved] (HBASE-17700) Release 1.2.5
[ https://issues.apache.org/jira/browse/HBASE-17700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-17700. - Resolution: Fixed Announcement email sent to user@hbase, announce@apache, and dev@hbase. > Release 1.2.5 > - > > Key: HBASE-17700 > URL: https://issues.apache.org/jira/browse/HBASE-17700 > Project: HBase > Issue Type: Task > Components: community >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 1.2.5 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[ANNOUNCE] Apache HBase 1.2.5 is now available for download
The HBase team is happy to announce the immediate availability of Apache HBase 1.2.5. Apache HBase is an open-source, distributed, versioned, non-relational database. Apache HBase gives you low latency random access to billions of rows with millions of columns atop non-specialized hardware. To learn more about HBase, see https://hbase.apache.org/. HBase 1.2.5 is the latest maintenance release in the HBase 1.2 line, continuing on the theme of bringing a stable, reliable database to the Hadoop and NoSQL communities. This release includes over 50 resolved issues since the 1.2.4 release. Incompatibilities: * HBASE-17725 There is an incompatible change to the LimitedPrivate API 'RpcServiceInterface'. Apache Phoenix is not impacted. Critical fixes include: * HBASE-17069 RegionServer writes invalid META entries for split daughters in some circumstances * HBASE-17044 Fix merge failed before creating merged region leaves meta inconsistent * HBASE-17206 FSHLog may roll a new writer successfully with unflushed entries * HBASE-16765 New SteppingRegionSplitPolicy, avoid too aggressive spread of regions for small tables. The full list of issues can be found in the CHANGES.txt file included in the release and online at: https://s.apache.org/hbase-1.2.5-jira-releasenotes Download through an ASF mirror near you: https://www.apache.org/dyn/closer.lua/hbase/1.2.5 The relevant checksums files are available at: https://www.apache.org/dist/hbase/1.2.5/hbase-1.2.5-src.tar.gz.mds https://www.apache.org/dist/hbase/1.2.5/hbase-1.2.5-bin.tar.gz.mds Project member signature keys can be found at https://www.apache.org/dist/hbase/KEYS PGP signatures are available at: https://www.apache.org/dist/hbase/1.2.5/hbase-1.2.5-src.tar.gz.asc https://www.apache.org/dist/hbase/1.2.5/hbase-1.2.5-bin.tar.gz.asc For instructions on verifying ASF release downloads, please see https://www.apache.org/dyn/closer.cgi#verify Question, comments, and problems are always welcome at: dev@hbase.apache.org. Cheers, The HBase Dev Team
[jira] [Created] (HBASE-17838) Replace fixed Executor Threads with dynamic thread pool
Janos Gub created HBASE-17838: - Summary: Replace fixed Executor Threads with dynamic thread pool Key: HBASE-17838 URL: https://issues.apache.org/jira/browse/HBASE-17838 Project: HBase Issue Type: Sub-task Reporter: Janos Gub Assignee: Janos Gub -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17837) Backport HBASE-15314 to branch-1.3
ramkrishna.s.vasudevan created HBASE-17837: -- Summary: Backport HBASE-15314 to branch-1.3 Key: HBASE-17837 URL: https://issues.apache.org/jira/browse/HBASE-17837 Project: HBase Issue Type: Improvement Components: BucketCache Affects Versions: 1.3.0 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 1.3.1 Backport of HBASE-15314. -- This message was sent by Atlassian JIRA (v6.3.15#6346)