taklwu commented on PR #5469:
URL: https://github.com/apache/hbase/pull/5469#issuecomment-1793159117

   
[`TestClusterScopeQuotaThrottle#testNamespaceClusterScopeQuota`](https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5469/7/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-root.txt)
 timeout in the precommit, but I tried to run it locally, it's not passing for 
some of the assertion count, but it should not be related to this code change.
   
   
   
[TestClusterScopeQuotaThrottle.testUserNamespaceClusterScopeQuota](https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5469/7/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-root.txt)
 is also a cluster timeout issue, I ran it locally but also timeout
   
   ```
   Caused by: org.apache.hadoop.ipc.RemoteException: File 
/user/taklwu/test-data/ea4313cf-0490-4dbb-e5f9-9519c164b89a/WALs/192.168.0.113,51733,1699049073380/192.168.0.113%2C51733%2C1699049073380.1702620709700
 could only be written to 0 of the 1 minReplication nodes. There are 2 
datanode(s) running and 2 node(s) are excluded in this operation.
           at 
org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(BlockManager.java:2276)
           at 
org.apache.hadoop.hdfs.server.namenode.FSDirWriteFileOp.chooseTargetForNewBlock(FSDirWriteFileOp.java:294)
           at 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2820)
           at 
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:910)
   ```
   
   it's existing issue I tried to checkout the branch-3 directly without my 
branch, rebuild and reran unit test still faced the same error
   
   
   @jojochuang  do you have any more comments?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to