Mate Szalay-Beko created HBASE-25297:
Summary: regenerate a missing table descriptors by hbck2
Key: HBASE-25297
URL: https://issues.apache.org/jira/browse/HBASE-25297
Project: HBase
Oh, this is my fault. I mean the old behavior IS to go to primary replica
first, which is what we want to change here.
And what I commented on jira, is to say that we do not need to get a
performance improvement before merging, it is not the goal of this issue.
And I suggested that if we want to
tianhang tang created HBASE-25296:
-
Summary: [Documentation]fix duplicate conf entry
Key: HBASE-25296
URL: https://issues.apache.org/jira/browse/HBASE-25296
Project: HBase
Issue Type: Bug
Guanghao Zhang created HBASE-25295:
--
Summary: Refactor the locate WAL logic in ReplicationSource
Key: HBASE-25295
URL: https://issues.apache.org/jira/browse/HBASE-25295
Project: HBase
Issue
Michael Stack created HBASE-25294:
-
Summary: Follow-on: defend against read replicas being enabled for
server-side clients
Key: HBASE-25294
URL: https://issues.apache.org/jira/browse/HBASE-25294
On Sun, Nov 15, 2020 at 11:20 PM 张铎(Duo Zhang)
wrote:
> So what is your purpose of distributing the request of region location
> lookup? It is just because you want to 'distribute the request of region
> location lookup'?
>
> Then I'm -1 on merging. We should reach an agreement on what we want
Huaxiang Sun created HBASE-25293:
Summary: Followup jira to address the client handling issue when
chaning from meta replica to non-meta-replica at the server side.
Key: HBASE-25293
URL:
Andrew Kyle Purtell created HBASE-25292:
---
Summary: Update InetSocketAddress usage discipline
Key: HBASE-25292
URL: https://issues.apache.org/jira/browse/HBASE-25292
Project: HBase
Huaxiang Sun created HBASE-25291:
Summary: Document how to enable the meta replica load balance mode
for the client
Key: HBASE-25291
URL: https://issues.apache.org/jira/browse/HBASE-25291
Project:
[
https://issues.apache.org/jira/browse/HBASE-25280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-25280.
---
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to feature branches, HBASE-18070 and
Folks,
As I explained in the jira, before our load hits the region server's
limit, the throughput is going to be similar for primary-only and meta
replica Load Balance mode. We are examining our test today, trying to push
up the load and
will come back.
Best Regards,
Huaxiang Sun
Update.
On the thread "HEAD-UP: Merging HBASE-18070 "Enable memstore replication
for meta replica" to master and then back to branch-2" I was asked to wait
so the participants in that discussion can resolve a misunderstanding.
I hope and encourage a timely resolution to the conflict so we can
I see, sure we can try to resolve it.
We had two full weeks, from now until the end of the month, for the RC, to
get it out before end of month. Further delay lessens that time frame but I
admit it is an arbitrary target and that shouldn't be the top most concern
given the interest of the
On Mon, Nov 16, 2020 at 7:44 AM Andrew Purtell wrote:
> My apologies, Stack, it's time to move on for 2.4. We can revisit this for
> 2.5.
>
>
One more day to allow Duo reconsider (my fault for not making this a VOTE
thread)?
The work here is mostly that of others. It would be a shame it didn't
Spinning the bits today. Pre-flight checks will take about 24 hours. Any
last minute work has that much time to make the train.
--
Best regards,
Andrew
Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
- A23, Crosstalk
My apologies, Stack, it's time to move on for 2.4. We can revisit this for
2.5.
On Mon, Nov 16, 2020 at 7:41 AM Stack wrote:
> On Sun, Nov 15, 2020 at 11:20 PM 张铎(Duo Zhang)
> wrote:
>
> > So what is your purpose of distributing the request of region location
> > lookup? It is just because you
On Sun, Nov 15, 2020 at 11:20 PM 张铎(Duo Zhang)
wrote:
> So what is your purpose of distributing the request of region location
> lookup? It is just because you want to 'distribute the request of region
> location lookup'?
>
> Then I'm -1 on merging. We should reach an agreement on what we want
Anyway I don’t wish to discuss this veto at length. What’s done is done. The
merge is off for the 2.4 RC. It will proceed without this feature.
> On Nov 16, 2020, at 7:33 AM, Andrew Purtell wrote:
>
> Your -1 throws a wrench into an agreement we had to merge this for 2.4. The
> 2.4 RC has
Your -1 throws a wrench into an agreement we had to merge this for 2.4. The 2.4
RC has been waiting for two weeks for this reason. It is a rather unfriendly
act and frustrating to me as 2.4 RC. I feel this needs to be said. Despite what
you claim the reason for hedged reads has been explained
[
https://issues.apache.org/jira/browse/HBASE-23224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lixiaobao resolved HBASE-23224.
---
Resolution: Fixed
> Delete the TODO ("get rid of allocations") tag in the WALProcedureStore class
Duo Zhang created HBASE-25290:
-
Summary: Remove table on master related code
Key: HBASE-25290
URL: https://issues.apache.org/jira/browse/HBASE-25290
Project: HBase
Issue Type: Sub-task
Sun Xin created HBASE-25289:
---
Summary: [testing] Clean up resources after tests in
rsgroup_shell_test.rb
Key: HBASE-25289
URL: https://issues.apache.org/jira/browse/HBASE-25289
Project: HBase
22 matches
Mail list logo
