Fwd: Error while running github feature from .asf.yaml in hbase-connectors!
Hi, I merged a commit to hbase-connectors from GitHub and got this automated email from Infra. The .asf.yaml files look identical in hbase [1] and hbase-connectors [2] repositories. Do you have any idea what could be the problem? - Peter [1] https://github.com/apache/hbase/blob/master/.asf.yaml [2] https://github.com/apache-connectors/hbase/blob/master/.asf.yaml -- Forwarded message - From: Apache Infrastructure Date: Tue, Aug 24, 2021 at 11:00 AM Subject: Error while running github feature from .asf.yaml in hbase-connectors! To: , An error occurred while running github feature in .asf.yaml!: dump_all() got an unexpected keyword argument 'sort_keys'
[jira] [Created] (HBASE-26219) Negative time is logged while waiting on regionservers
Peter Somogyi created HBASE-26219:
-
Summary: Negative time is logged while waiting on regionservers
Key: HBASE-26219
URL: https://issues.apache.org/jira/browse/HBASE-26219
Project: HBase
Issue Type: Bug
Reporter: Peter Somogyi
On Master startup when waiting on RegionServers to report in the log message
displays a negative time for the lastChange time.
{noformat}
2021-07-30 06:49:02,882 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=1502ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-1502ms
2021-07-30 06:49:03,693 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:04,384 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=3004ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-3004ms
2021-07-30 06:49:04,694 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:05,694 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:05,886 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=4506ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-4506ms
2021-07-30 06:49:06,695 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:07,389 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=6009ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-6009ms
2021-07-30 06:49:07,695 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:08,700 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:08,891 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=7511ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-7511ms
2021-07-30 06:49:09,701 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:10,393 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=9013ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-9013ms
2021-07-30 06:49:10,701 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:11,702 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:11,896 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=10516ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-10516ms
2021-07-30 06:49:12,702 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:13,398 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=12018ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-12018ms
2021-07-30 06:49:13,703 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:14,703 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:14,900 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=13520ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-13520ms
2021-07-30 06:49:15,704 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:16,402 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=0; waited=15022ms, expecting min=1 server(s),
max=NO_LIMIT server(s), timeout=4500ms, lastChange=-15022ms
2021-07-30 06:49:16,704 WARN
org.apache.hadoop.hbase.master.assignment.AssignmentManager: No servers
available; cannot place 1 unassigned regions.
2021-07-30 06:49:16,778 INFO org.apache.hadoop.hbase.master.ServerManager:
Registering regionserver=example.com,16020,1627627573364
2021-07-30 06:49:16,803 INFO org.apache.hadoop.hbase.master.ServerManager:
Waiting on regionserver count=1; waited=15423ms, expecting min=1 server(s),
max=NO_LIMIT server
[jira] [Created] (HBASE-26220) Use P2P communicate between region servers to sync the list for bootstrap node
Duo Zhang created HBASE-26220: - Summary: Use P2P communicate between region servers to sync the list for bootstrap node Key: HBASE-26220 URL: https://issues.apache.org/jira/browse/HBASE-26220 Project: HBase Issue Type: Sub-task Reporter: Duo Zhang For returning bootstrap nodes to client, we do not need to always track exactly the current live region server. But now, we just set a watcher on zookeeper to watch all the live region servers, on every region server, for large cluster, it will be a big pressure for zookeeper. So here I think, we could let region servers to communicate with each other to sync the available bootstrap node, like a P2P network. Will put a simple design doc soon. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-26173) Return only a sub set of region servers as bootstrap nodes
[ https://issues.apache.org/jira/browse/HBASE-26173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-26173. --- Hadoop Flags: Reviewed Assignee: Duo Zhang Resolution: Fixed Pushed to master and branch-2. Thanks [~bharathv] for reviewing. > Return only a sub set of region servers as bootstrap nodes > -- > > Key: HBASE-26173 > URL: https://issues.apache.org/jira/browse/HBASE-26173 > Project: HBase > Issue Type: Sub-task > Components: Client >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 2.5.0, 3.0.0-alpha-2 > > > For some large clusters we may have thousands of region servers, I do not > think we need to return all the region servers as bootstrap nodes. For me I > think ten servers is enough for a client usually? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-26135) Backport HBASE-25616 "Upgrade opentelemetry to 1.0.0" to branch-2
[
https://issues.apache.org/jira/browse/HBASE-26135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tak-Lon (Stephen) Wu resolved HBASE-26135.
--
Resolution: Fixed
> Backport HBASE-25616 "Upgrade opentelemetry to 1.0.0" to branch-2
> -
>
> Key: HBASE-26135
> URL: https://issues.apache.org/jira/browse/HBASE-26135
> Project: HBase
> Issue Type: Sub-task
> Components: tracing
>Affects Versions: 2.5.0
>Reporter: Tak-Lon (Stephen) Wu
>Assignee: Tak-Lon (Stephen) Wu
>Priority: Major
> Fix For: 2.5.0
>
>
> 12/17 commits of HBASE-22120, original commits
> [{{8399293}}|https://github.com/apache/hbase/commit/8399293e21127df3ffdcb757242e4cb5964c7e99]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-26136) Backport HBASE-25723 "Temporarily remove the trace support for RegionScanner.next" to branch-2
[
https://issues.apache.org/jira/browse/HBASE-26136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tak-Lon (Stephen) Wu resolved HBASE-26136.
--
Resolution: Fixed
commit pushed to
[https://github.com/apache/hbase/commit/817cfe1bf2c23de8cae178e0f96462ab5da33a59]
Thanks [~zhangduo] for reviewing.
> Backport HBASE-25723 "Temporarily remove the trace support for
> RegionScanner.next" to branch-2
> --
>
> Key: HBASE-26136
> URL: https://issues.apache.org/jira/browse/HBASE-26136
> Project: HBase
> Issue Type: Sub-task
> Components: tracing
>Affects Versions: 2.5.0
>Reporter: Tak-Lon (Stephen) Wu
>Assignee: Tak-Lon (Stephen) Wu
>Priority: Major
> Fix For: 2.5.0
>
>
> 13/17 commits of HBASE-22120, original commit
> [{{7f90c22}}|https://github.com/apache/hbase/commit/7f90c2201f6a17d2e2d031505c35ae7c2b1ed7ea]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-26221) Report flaky jenkins job should have the ability to submit flaky tests manually
Duo Zhang created HBASE-26221: - Summary: Report flaky jenkins job should have the ability to submit flaky tests manually Key: HBASE-26221 URL: https://issues.apache.org/jira/browse/HBASE-26221 Project: HBase Issue Type: Improvement Components: jenkins, test Reporter: Duo Zhang Recently our pre commit result is very unstable due to some flaky tests, such as TestReplicationDroppedTable, but it never fails in nightly builds so we never include it in the flaky list. I think our find flaky jenkins job should allow submitting tests manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-26222) Backport HBASE-26204 to branch-2:
Shinya Yoshida created HBASE-26222: -- Summary: Backport HBASE-26204 to branch-2: Key: HBASE-26222 URL: https://issues.apache.org/jira/browse/HBASE-26222 Project: HBase Issue Type: Sub-task Reporter: Shinya Yoshida -- This message was sent by Atlassian Jira (v8.3.4#803005)
