HDFS-17065. Fix typos in hadoop-hdfs-project (#5796)

This commit is contained in:
Zhaohui Wang 2023-07-03 23:41:37 +08:00 committed by GitHub
parent 5a35fb5a72
commit 9659d0720d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 5 additions and 5 deletions

View File

@ -874,7 +874,7 @@ private BigInteger getNameserviceAggregatedBigInt(
/** /**
* Fetches the most active namenode memberships for all known nameservices. * Fetches the most active namenode memberships for all known nameservices.
* The fetched membership may not or may not be active. Excludes expired * The fetched membership may or may not be active. Excludes expired
* memberships. * memberships.
* @throws IOException if the query could not be performed. * @throws IOException if the query could not be performed.
* @return List of the most active NNs from each known nameservice. * @return List of the most active NNs from each known nameservice.

View File

@ -186,8 +186,8 @@ public void sendOOB() throws IOException, InterruptedException {
if (br == null) { if (br == null) {
return; return;
} }
// This doesn't need to be in a critical section. Althogh the client // This doesn't need to be in a critical section. Although the client
// can resue the connection to issue a different request, trying sending // can reuse the connection to issue a different request, trying sending
// an OOB through the recently closed block receiver is harmless. // an OOB through the recently closed block receiver is harmless.
LOG.info("Sending OOB to peer: {}", peer); LOG.info("Sending OOB to peer: {}", peer);
br.sendOOB(); br.sendOOB();

View File

@ -624,7 +624,7 @@ private static FileState analyzeFileState(
// timeout, or because of an HA failover. In that case, we know // timeout, or because of an HA failover. In that case, we know
// by the fact that the client is re-issuing the RPC that it // by the fact that the client is re-issuing the RPC that it
// never began to write to the old block. Hence it is safe to // never began to write to the old block. Hence it is safe to
// to return the existing block. // return the existing block.
// 3) This is an entirely bogus request/bug -- we should error out // 3) This is an entirely bogus request/bug -- we should error out
// rather than potentially appending a new block with an empty // rather than potentially appending a new block with an empty
// one in the middle, etc // one in the middle, etc

View File

@ -327,7 +327,7 @@ public void testPipelineRecoveryOnOOB() throws Exception {
// Wait long enough to receive an OOB ack before closing the file. // Wait long enough to receive an OOB ack before closing the file.
GenericTestUtils.waitForThreadTermination( GenericTestUtils.waitForThreadTermination(
"Async datanode shutdown thread", 100, 10000); "Async datanode shutdown thread", 100, 10000);
// Retart the datanode // Restart the datanode
cluster.restartDataNode(0, true); cluster.restartDataNode(0, true);
// The following forces a data packet and end of block packets to be sent. // The following forces a data packet and end of block packets to be sent.
out.close(); out.close();