[
https://issues.apache.org/jira/browse/HBASE-17843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved HBASE-17843.
Resolution: Not A Problem
> JUnit test timed out in TestRegionReplicaFailover.java
> --
[
https://issues.apache.org/jira/browse/HBASE-17726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar resolved HBASE-17726.
---
Resolution: Fixed
Assignee: Enis Soztutar (was: Xiaobing Zhou)
Fix Version/s:
Raman Ch created HBASE-17901:
Summary: HBase region server stops because of a failure during
memstore flush
Key: HBASE-17901
URL: https://issues.apache.org/jira/browse/HBASE-17901
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved HBASE-7292.
---
Resolution: Won't Fix
HTablePool had been removed in 0.98.1, so this jira should be closed.
>
[
https://issues.apache.org/jira/browse/HBASE-17173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-17173.
-
Resolution: Duplicate
> update ref guide links for discussions to use lists.apache.org
>
[
https://issues.apache.org/jira/browse/HBASE-16380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-16380.
-
Resolution: Duplicate
Assignee: (was: Sean Busbey)
rolling this into a generalized "cle
Ted Yu created HBASE-17902:
--
Summary: Backport HBASE-16367 "Race between master and region
server initialization may lead to premature server abort" to 1.3
Key: HBASE-17902
URL: https://issues.apache.org/jira/browse/HBAS
Build status: Failure
The HBase website has not been updated to incorporate HBase commit
${HBASE_GIT_SHA}.
See https://builds.apache.org/job/hbase_generate_website/955/console
Let me revive this thread.
Recall, we are stuck on old or particular versions of critical libs. We are
unable to update because our versions will clash w/ versions from
upstreamer hadoop2.7/2.8/3.0/spark, etc. We have a shaded client. We need
to message downstreamers that they should use it going
Build status: Still Failing
The HBase website has not been updated to incorporate HBase commit
${HBASE_GIT_SHA}.
See https://builds.apache.org/job/hbase_generate_website/956/console
[
https://issues.apache.org/jira/browse/HBASE-7456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-7456.
--
Resolution: Won't Fix
HTP has been removed. 0.94 is EOL.
> Stargate's HTablePool maxSize is hard-coded at 10, t
+1 (non-binding)
This sounds like a good idea to me!
Zach
On 4/11/17, 9:48 AM, "saint@gmail.com on behalf of Stack"
wrote:
Let me revive this thread.
Recall, we are stuck on old or particular versions of critical libs. We are
unable to update because our versions will cla
Should we allow dependent projects (such as Phoenix) to weigh in on this issue
since they are likely going to be the ones that benefit/are effected?
On 4/11/17, 10:17 AM, "York, Zach" wrote:
+1 (non-binding)
This sounds like a good idea to me!
Zach
On 4/11/17, 9:4
Chia-Ping Tsai created HBASE-17903:
--
Summary: The alias for the link of HBASE-6580 is incorrect
Key: HBASE-17903
URL: https://issues.apache.org/jira/browse/HBASE-17903
Project: HBase
Issue T
huaxiang sun created HBASE-17904:
Summary: Get runs into NoSuchElementException when using Read
Replica, with hbase. ipc.client.specificThreadForWriting to be true and
hbase.rpc.client.impl to be org.apache.hadoop.hbase.ipc.RpcClientImpl
> would ask for a new repo [1]. In here we'd create a new mvn project.
Why get a new repo? A different (new) HBase mvn module that is depended
upon via other modules should cover it, IIRC. That module can handle all
the shading and not include transitive dependencies. Then in "downstream
modules"
[
https://issues.apache.org/jira/browse/HBASE-17438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janos Gub resolved HBASE-17438.
---
Resolution: Duplicate
> Server side change to accommodate limit by number of mutations
>
[
https://issues.apache.org/jira/browse/HBASE-17838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janos Gub resolved HBASE-17838.
---
Resolution: Won't Fix
> Replace fixed Executor Threads with dynamic thread pool
> --
A new module probably won't work due to the fact that we need to reference
the relocated classes in source code and maven won't do that until the
"package" phase.
IDEs in particular will barf all over the place.
On Tue, Apr 11, 2017 at 1:04 PM Jesse Yates wrote:
> > would ask for a new repo [1]
Right, hence the install/package phase (probably with -DskipTests) first.
Probably only have to do this occasionally, as dependencies change.
Agree the IDEs are really unhappy with this though.
Seems like more headache to create another repo, but I'm not too tied
either way. Just asking. Thanks S
On Tue, Apr 11, 2017 at 10:23 AM, York, Zach wrote:
> Should we allow dependent projects (such as Phoenix) to weigh in on this
> issue since they are likely going to be the ones that benefit/are effected?
>
> I dumped a pointer to here into dev@phoenix.
St.Ack
> On 4/11/17, 10:17 AM, "York, Za
Yi Liang created HBASE-17905:
Summary: [hbase-spark] bulkload does not work when table not exist
Key: HBASE-17905
URL: https://issues.apache.org/jira/browse/HBASE-17905
Project: HBase
Issue Type
Build status: Failure
The HBase website has not been updated to incorporate HBase commit
${HBASE_GIT_SHA}.
See https://builds.apache.org/job/hbase_generate_website/964/console
[
https://issues.apache.org/jira/browse/HBASE-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved HBASE-8220.
---
Resolution: Won't Fix
> can we record the count opened HTable for HTablePool
> ---
[
https://issues.apache.org/jira/browse/HBASE-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved HBASE-10396.
Resolution: Won't Fix
0.94 is EOL. Reopen it if objection on mailing list.
> The construct
> This effort is about our internals. We have a mess of other components all
> up inside us such as HDFS, etc., each with their own sets of dependencies
> many of which we have in common. This project t is about making it so we
> can upgrade at a rate independent of when our upstreamers choose to
c
26 matches
Mail list logo