[
https://issues.apache.org/jira/browse/HBASE-11963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl resolved HBASE-11963.
---
Resolution: Fixed
Hadoop Flags: Reviewed
Fixed. Thanks [~sukuna...@gmail.com].
> Synch
I agree it would be surprising to have masters running RegionServers and
hosting regions. Maybe we can take that kind of departure for 2.0? (Or even
1.1?) It's not clear what state that will end up in. Default-on features in 1.0
should carry forward and promote stability and familiarity?
> On
I add HBase 0.98.5-hadooo2 dependency into pom.xml, but it says can't find
it in maven repo.
On Sep 13, 2014 10:29 AM, "牛兆捷" wrote:
> If I want to rebuild YCSB specific for hbase 0.98.5-hadoop2, what should I
> do?
>
> --
> *Regards,*
> *Zhaojie*
>
>
Anoop Sam John created HBASE-11971:
--
Summary: [0.98] Deprecate KeyValue based APIs in WALEdit
Key: HBASE-11971
URL: https://issues.apache.org/jira/browse/HBASE-11971
Project: HBase
Issue Typ
[
https://issues.apache.org/jira/browse/HBASE-11805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John resolved HBASE-11805.
Resolution: Fixed
Fix Version/s: (was: 0.98.7)
Release Note:
The KeyValue b
If I want to rebuild YCSB specific for hbase 0.98.5-hadoop2, what should I
do?
--
*Regards,*
*Zhaojie*
Ted Yu created HBASE-11970:
--
Summary: BlockCache would be instantiated when Master doesn't host
regions
Key: HBASE-11970
URL: https://issues.apache.org/jira/browse/HBASE-11970
Project: HBase
Issue
Hyeonjong created HBASE-11969:
-
Summary: 3 Thrift annotated filters for TFilterV2
Key: HBASE-11969
URL: https://issues.apache.org/jira/browse/HBASE-11969
Project: HBase
Issue Type: Sub-task
Jonathan Hsieh created HBASE-11968:
--
Summary: If MOB is enabled, it should make sure hfile v3 is being
used.
Key: HBASE-11968
URL: https://issues.apache.org/jira/browse/HBASE-11968
Project: HBase
+1
md5 is good. Signature checked out but said this:
gpg: Can't check signature: public key not found
... so maybe put yours up in public place?
Thanks for filling out CHANGES.txt with included fixes.
Tried to start up master but failed because old dir in place (HMaster
wouldn't go down on FA
stack created HBASE-11967:
-
Summary: HMaster in standalone won't go down if it gets 'Unhandled
exception'
Key: HBASE-11967
URL: https://issues.apache.org/jira/browse/HBASE-11967
Project: HBase
Issue
On Fri, Sep 12, 2014 at 1:21 PM, Vladimir Rodionov
wrote:
> All row mutate operations in HBase are atomic:
> puts/deletes/increments/appends.
> Atomicity in HBase has the same meaning as in RDBMs exactly - operations
> completes as a whole or does not at all. There is an additional guarantee
> i
All row mutate operations in HBase are atomic: puts/deletes/increments/appends.
Atomicity in HBase has the same meaning as in RDBMs exactly - operations
completes as a whole or does not at all. There is an additional guarantee
in HBase that all reads are ROW - atomic as well - one will never read
Srikanth Srungarapu created HBASE-11966:
---
Summary: Minor error in
TestHRegion.testCheckAndMutate_WithCorrectValue()
Key: HBASE-11966
URL: https://issues.apache.org/jira/browse/HBASE-11966
Projec
On Fri, Sep 12, 2014 at 11:25 AM, Vladimir Rodionov
wrote:
> Michael,
>
> This is not a row-level locking - it is region-wide lock. This is a major
> reason of the following performance problems:
>
>
Pardon my misreading as row-scoping (I'd just come off reading Michael
Segel's note).
> 1) Mu
Vladimir Rodionov created HBASE-11965:
-
Summary: Optimize locking in HRegion
Key: HBASE-11965
URL: https://issues.apache.org/jira/browse/HBASE-11965
Project: HBase
Issue Type: Bug
There is no RLL (row level locking) in HBase , all locks- are region-wide.
This is the issue I am going to address
in a separate JIRA.
Example from HRegion.append
// Lock row
startRegionOperation(Operation.APPEND);
Regards,
-Vladimir
On Fri, Sep 12, 2014 at 11:57 AM, Vladimir Rodionov
According to Bible:
http://hbase.apache.org/acid-semantics.html
HBase declares that all row reads are consistent - partial reads for rows
are not possible.
[
Consistency and Isolation
1. All rows returned via any access API will consist of a complete row
that existed at some point in the t
Michael,
This is not a row-level locking - it is region-wide lock. This is a major
reason of the following performance problems:
1) Multi gets are bad if inside the same region
2) Multiple scanners over the same region are bad
3) Scan during compaction are bad.
I need some input from HBase folk
[
https://issues.apache.org/jira/browse/HBASE-11959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang resolved HBASE-11959.
-
Resolution: Fixed
Fix Version/s: 0.99.1
Hadoop Flags: Reviewed
I tested related tests
On Thu, Sep 11, 2014 at 3:58 PM, Vladimir Rodionov
wrote:
> Hi, all
>
> We have two isolation levels in (used to be in Scan) in Query now. See:
> https://issues.apache.org/jira/browse/HBASE-11936
>
> I moved isolation levels API from Scan upward to Query class. The reason:
> this API was not avai
Andrew Purtell created HBASE-11964:
--
Summary: Improve replication source thread handling
Key: HBASE-11964
URL: https://issues.apache.org/jira/browse/HBASE-11964
Project: HBase
Issue Type: Su
Andrew Purtell created HBASE-11963:
--
Summary: Synchronize peer cluster replication connection attempts
Key: HBASE-11963
URL: https://issues.apache.org/jira/browse/HBASE-11963
Project: HBase
Vlad,
I understand.
However several of the HBase committers aren’t really schooled in RDBMS design.
And again, the older (going back to 0.23 ) use of the term RLL isn’t relational
RLL and when you start to talk about isolation you’re getting in to the RDBMS
RLL
So you really need to define
Ted Yu created HBASE-11962:
--
Summary: Port HBASE-11897 "Add append and remove peer table-cfs
cmds for replication" to 0.98
Key: HBASE-11962
URL: https://issues.apache.org/jira/browse/HBASE-11962
Project: HBa
Michael, this is HBase developers mailing list.
-Vladimir
On Fri, Sep 12, 2014 at 12:08 AM, Michael Segel
wrote:
> Silly question…
>
> HBase uses the term RLL (row level locking) to make the writes to a row
> atomic.
>
> When you start to get in to isolation, RLL takes on a different meaning
Jimmy Xiang created HBASE-11961:
---
Summary: Document region state transitions
Key: HBASE-11961
URL: https://issues.apache.org/jira/browse/HBASE-11961
Project: HBase
Issue Type: Task
Jimmy Xiang created HBASE-11960:
---
Summary: Provide a sample to show how to use Thrift client
authentication
Key: HBASE-11960
URL: https://issues.apache.org/jira/browse/HBASE-11960
Project: HBase
Jimmy Xiang created HBASE-11959:
---
Summary: TestAssignmentManagerOnCluster is falky
Key: HBASE-11959
URL: https://issues.apache.org/jira/browse/HBASE-11959
Project: HBase
Issue Type: Bug
Aff
+1 on inclusion in dev-support.
On Sep 12, 2014, at 6:26 AM, Sean Busbey wrote:
> Yeah +1 for inclusion in dev-support. Be sure to add a ASL header to it
> before pushing.
>
> --
> Sean
> On Sep 12, 2014 12:35 AM, "Misty Stanley-Jones"
> wrote:
>
>> I wrote the script and I think the websit
Yeah +1 for inclusion in dev-support. Be sure to add a ASL header to it
before pushing.
--
Sean
On Sep 12, 2014 12:35 AM, "Misty Stanley-Jones"
wrote:
> I wrote the script and I think the website is all fixed now. You can follow
> my progress and see the script at
> https://issues.apache.org/ji
Liu Shaohui created HBASE-11958:
---
Summary: Add documents about snapshot owner
Key: HBASE-11958
URL: https://issues.apache.org/jira/browse/HBASE-11958
Project: HBase
Issue Type: Sub-task
Liu Shaohui created HBASE-11957:
---
Summary: Backport HBASE-5974 to 0.94
Key: HBASE-11957
URL: https://issues.apache.org/jira/browse/HBASE-11957
Project: HBase
Issue Type: Bug
Reporte
Silly question…
HBase uses the term RLL (row level locking) to make the writes to a row atomic.
When you start to get in to isolation, RLL takes on a different meaning.
So now you have to better define what do you mean by locking. Are you taking
about HBase RLL,
or are you talking about Tra
34 matches
Mail list logo
