[Fix](InternalSchema) Compute nodes should not be used for Internal schema three replica #36130
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
cambyzju
reviewed
Jun 11, 2024
fe/fe-core/src/main/java/org/apache/doris/system/SystemInfoService.java
Outdated
Show resolved
Hide resolved
Contributor
|
run buildall |
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
Contributor
|
please replace screenshot with text |
TPC-H: Total hot run time: 40050 ms |
TPC-DS: Total hot run time: 172180 ms |
ClickBench: Total hot run time: 30.34 s |
…chema three replica
…vice.java Co-authored-by: camby <104178625@qq.com>
Contributor
|
run buildall |
TPC-H: Total hot run time: 40188 ms |
TPC-DS: Total hot run time: 173627 ms |
ClickBench: Total hot run time: 30.68 s |
yiguolei
approved these changes
Jul 15, 2024
morningman
pushed a commit
to morningman/doris
that referenced
this pull request
Jul 17, 2024
…chema three replica (apache#36130) ## Proposed changes Issue Number: close #xxx When I add computing nodes to the cluster, a large number of warning logs will appear in the FE log, as shown below: ``` 2024-06-11 17:50:04,360 WARN (InternalSchemaInitializer|137) [InternalSchemaInitializer.modifyTblReplicaCount():146] Failed to scale replica of stats tbl:column_statistics to 3 org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = errCode = 2, detailMessage = Failed to find enough backend, please check the replication num,replication tag and storage medium and avail capacity of backends. Create failed replications: replication tag: {"location" : "default"}, replication num: 3, storage medium: null at org.apache.doris.common.util.PropertyAnalyzer.analyzeReplicaAllocationImpl(PropertyAnalyzer.java:1217) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.common.util.PropertyAnalyzer.analyzeReplicaAllocation(PropertyAnalyzer.java:1136) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.Env.modifyTableReplicaAllocation(Env.java:4868) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.InternalSchemaInitializer.modifyTblReplicaCount(InternalSchemaInitializer.java:123) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.InternalSchemaInitializer.run(InternalSchemaInitializer.java:93) ~[doris-fe.jar:1.2-SNAPSHOT] ```  This is because the computing node is also considered a replica in the code, and the computing node does not have storage resources, resulting in an error message. --------- Co-authored-by: camby <104178625@qq.com>
seawinde
pushed a commit
to seawinde/doris
that referenced
this pull request
Jul 17, 2024
…chema three replica (apache#36130) ## Proposed changes Issue Number: close #xxx When I add computing nodes to the cluster, a large number of warning logs will appear in the FE log, as shown below: ``` 2024-06-11 17:50:04,360 WARN (InternalSchemaInitializer|137) [InternalSchemaInitializer.modifyTblReplicaCount():146] Failed to scale replica of stats tbl:column_statistics to 3 org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = errCode = 2, detailMessage = Failed to find enough backend, please check the replication num,replication tag and storage medium and avail capacity of backends. Create failed replications: replication tag: {"location" : "default"}, replication num: 3, storage medium: null at org.apache.doris.common.util.PropertyAnalyzer.analyzeReplicaAllocationImpl(PropertyAnalyzer.java:1217) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.common.util.PropertyAnalyzer.analyzeReplicaAllocation(PropertyAnalyzer.java:1136) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.Env.modifyTableReplicaAllocation(Env.java:4868) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.InternalSchemaInitializer.modifyTblReplicaCount(InternalSchemaInitializer.java:123) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.InternalSchemaInitializer.run(InternalSchemaInitializer.java:93) ~[doris-fe.jar:1.2-SNAPSHOT] ```  This is because the computing node is also considered a replica in the code, and the computing node does not have storage resources, resulting in an error message. --------- Co-authored-by: camby <104178625@qq.com>
dataroaring
pushed a commit
that referenced
this pull request
Jul 17, 2024
…chema three replica (#36130) ## Proposed changes Issue Number: close #xxx When I add computing nodes to the cluster, a large number of warning logs will appear in the FE log, as shown below: ``` 2024-06-11 17:50:04,360 WARN (InternalSchemaInitializer|137) [InternalSchemaInitializer.modifyTblReplicaCount():146] Failed to scale replica of stats tbl:column_statistics to 3 org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = errCode = 2, detailMessage = Failed to find enough backend, please check the replication num,replication tag and storage medium and avail capacity of backends. Create failed replications: replication tag: {"location" : "default"}, replication num: 3, storage medium: null at org.apache.doris.common.util.PropertyAnalyzer.analyzeReplicaAllocationImpl(PropertyAnalyzer.java:1217) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.common.util.PropertyAnalyzer.analyzeReplicaAllocation(PropertyAnalyzer.java:1136) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.Env.modifyTableReplicaAllocation(Env.java:4868) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.InternalSchemaInitializer.modifyTblReplicaCount(InternalSchemaInitializer.java:123) ~[doris-fe.jar:1.2-SNAPSHOT] at org.apache.doris.catalog.InternalSchemaInitializer.run(InternalSchemaInitializer.java:93) ~[doris-fe.jar:1.2-SNAPSHOT] ```  This is because the computing node is also considered a replica in the code, and the computing node does not have storage resources, resulting in an error message. --------- Co-authored-by: camby <104178625@qq.com>
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Issue Number: close #xxx
When I add computing nodes to the cluster, a large number of warning logs will appear in the FE log, as shown below:
This is because the computing node is also considered a replica in the code, and the computing node does not have storage resources, resulting in an error message.