Thanks Dima! That definitely would be handy.
-Mikhail
On Mon, Apr 3, 2017 at 10:55 PM, Dima Spivak wrote:
> I can help with running the API compatibility tooling. It's the least I can
> do since I no longer have access to the computing resources I used to rely
> upon for testing releases. Just
I can help with running the API compatibility tooling. It's the least I can
do since I no longer have access to the computing resources I used to rely
upon for testing releases. Just ping me when you need a hand, Mikhail.
On Mon, Apr 3, 2017 at 10:35 PM Mikhail Antonov
wrote:
> Hi,
>
> I've been
[
https://issues.apache.org/jira/browse/HBASE-17868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan resolved HBASE-17868.
Resolution: Duplicate
Dup of HBASE-HBASE-15691.
> Backport HBASE-10205 to
Hi,
I've been planning to cut an RC for 1.3.1 for some time, apologize for the
delay here. I'm going to go over outstanding jiras tomorrow,
I think there are still few issues waiting for backports.
Andrew - appreciate your offer! I have started preparations for 1.3.1
release, but any help with tr
I'd be happy to RM 1.3.1 unless someone already has it waiting in the wings.
> On Apr 3, 2017, at 5:43 PM, James Taylor wrote:
>
> Hello,
> We'd like to start supporting releases of Phoenix that work with the HBase
> 1.3 branch, but there's a committed fix on which we rely (HBASE-17587) for
>
Tomu Tsuruhara created HBASE-17871:
--
Summary: scan#setBatch(int) call leads wrong result of
VerifyReplication
Key: HBASE-17871
URL: https://issues.apache.org/jira/browse/HBASE-17871
Project: HBase
+1
I meant to send this a while ago.
On 4/3/17, 5:43 PM, "James Taylor" wrote:
Hello,
We'd like to start supporting releases of Phoenix that work with the HBase
1.3 branch, but there's a committed fix on which we rely (HBASE-17587) for
Phoenix to function correctly. Is there a t
Hello,
We'd like to start supporting releases of Phoenix that work with the HBase
1.3 branch, but there's a committed fix on which we rely (HBASE-17587) for
Phoenix to function correctly. Is there a time frame for an HBase 1.3.1
release?
Thanks,
James
Ashu Pachauri created HBASE-17870:
-
Summary: Backport HBASE-12770 to branch-1.3
Key: HBASE-17870
URL: https://issues.apache.org/jira/browse/HBASE-17870
Project: HBase
Issue Type: Improvement
Hi HBase Developers,
The previous email I sent seem to spur more conversion on the durability of
HBase rather than its overall architecture; so I think i would send another
email to plead comments on our architectural document (
http://pages.cs.wisc.edu/~suli/hbase.pdf) .
We are doing some researc
On Fri, Mar 31, 2017 at 7:29 PM, 杨苏立 Yang Su Li wrote:
> Hi,
>
> We found that when there is a mix of CPU-intensive and I/O intensive
> workload, HBase seems to slow everything down to the disk throughput level.
>
> This is shown in the performance graph at
> http://pages.cs.wisc.edu/~suli/blocki
Jerry He created HBASE-17869:
Summary: UnsafeAvailChecker wrongly returns false on ppc
Key: HBASE-17869
URL: https://issues.apache.org/jira/browse/HBASE-17869
Project: HBase
Issue Type: Bug
A
Yes, you are correct that there is an edge condition here when there is
abrupt power-failure to a node. HDFS guards against most of this as
there are multiple copies of your data spread across racks. However, if
you have abrupt power failure across multiple racks (or your entire
hardware), yes,
ramkrishna.s.vasudevan created HBASE-17868:
--
Summary: Backport HBASE-10205 to branch-1.3
Key: HBASE-17868
URL: https://issues.apache.org/jira/browse/HBASE-17868
Project: HBase
Issue
14 matches
Mail list logo