W0710 23:30:54.833759 12361 checks.go:835] detected that the sandbox image "registry.k8s.io/pause:3.6" of the container runtime is inconsistent with that used by kubeadm. It is recommended that using "registry.aliyuncs.com/google_containers/pause:3.9" as the CRI sandbox image.

您好！对于您的问题，建议您使用"registry.aliyuncs.com/google_containers/pause:3.9"作为CRI容器运行时的沙箱镜像。这是因为检测到您当前使用的沙箱镜像"registry.k8s.io/pause:3.6"与kubeadm使用的镜像不一致。更换为匹配的镜像可以确保系统的一致性和稳定性。

相关问题

E: The repository 'http://pkg.jenkins.io/debian-stable binary/ Release' is not signed.

This error message indicates that the repository for Jenkins, located at http://pkg.jenkins.io/debian-stable binary/, does not have a valid GPG signature. This means that the package manager on your system cannot verify the authenticity of the packages being downloaded from this repository.

To solve this issue, you can try the following steps:

1. Check if the repository is still active and accessible. Sometimes, repositories may go offline or become inaccessible due to various reasons.

2. Verify that you have added the correct repository URL to your package manager's sources.list file.

3. Update your GPG keyring by running the following command in a terminal:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys KEY-ID

Replace KEY-ID with the GPG key ID of the repository. You can find the key ID on the Jenkins website.

4. Alternatively, you can also try disabling the GPG signature check for this repository. However, this is not recommended as it can compromise the security of your system.

To disable signature checks, add the following line to your package manager's configuration file:

Acquire::AllowInsecureRepositories "true";

Again, this is not recommended and should only be used as a last resort.

org.apache.hadoop.hbase.DoNotRetryIOException: Unable to load configured region split policy 'org.apache.phoenix.schema.MetaDataSplitPolicy' for table 'SYSTEM.CATALOG' Set hbase.table.sanity.checks to false at conf or table descriptor if you want to bypass sanity checks at org.apache.hadoop.hbase.util.TableDescriptorChecker.warnOrThrowExceptionForFailure(TableDescriptorChecker.java:296) at org.apache.hadoop.hbase.util.TableDescriptorChecker.sanityCheck(TableDescriptorChecker.java:109) at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:2025) at org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:657) at org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java) at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:133) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318) org.apache.hadoop.hbase.DoNotRetryIOException: Unable to load configured region split policy 'org.apache.phoenix.schema.MetaDataSplitPolicy' for table 'SYSTEM.CATALOG' Set hbase.table.sanity.checks to false at conf or table descriptor if you want to bypass sanity checks at org.apache.hadoop.hbase.util.TableDescriptorChecker.warnOrThrowExceptionForFailure(TableDescriptorChecker.java:296) at org.apache.hadoop.hbase.util.TableDescriptorChecker.sanityCheck(TableDescriptorChecker.java:109) at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:2025) at org.apache.hadoop.hbase.master.MasterRpcServices.createTable(MasterRpcServices.java:657) at org.apache.hadoop.hbase.shaded.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java) at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:413) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:133) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338) at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318)

这个错误日志表明在创建名为 'SYSTEM.CATALOG' 的表时，HBase无法加载配置的区域拆分策略 'org.apache.phoenix.schema.MetaDataSplitPolicy'，并建议将 'hbase.table.sanity.checks' 设置为false来绕过健康检查。

这个错误通常发生在使用Apache Phoenix来创建HBase表时，因为Phoenix需要特定的配置和设置来正确地运行。在这种情况下，你可以尝试以下解决方法：

1. 检查配置：确保HBase和Phoenix的相关配置正确设置。特别是，确保'HBase-site.xml'和'Phoenix-core.jar'文件在HBase的类路径下。

2. 检查Phoenix版本：确保使用的Phoenix版本与HBase版本兼容。不同版本之间可能存在不兼容性，导致无法正确加载区域拆分策略。

3. 禁用健康检查：按照错误提示的建议，在HBase的配置文件中将 'hbase.table.sanity.checks' 设置为false。这将绕过表描述符的健康检查，但需要谨慎使用。

4. 更新Phoenix配置：如果你使用的是较新的Phoenix版本，可能需要更新配置以适应最新的HBase版本。查阅Phoenix和HBase的官方文档，了解他们之间的兼容性和配置要求。

如果问题仍然存在，我建议你查看更详细的错误日志以了解更多上下文信息，并在HBase和Phoenix的社区或论坛中咨询其他开发者，以获取更专业的帮助和支持。