[ 
https://issues.apache.org/jira/browse/HDDS-17606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Elavarasan Kathirvel updated HDDS-17606:
----------------------------------------
    Description: 
Short-circuit read is enabled on the cluster. An EC key is written and then 
read from a client running on the same host as a datanode.

An EC key must use the normal read path via gRPC. Short-circuit is for Ratis 
keys.

*Steps to Reproduce:*
 * Enable Short-Circuit Read (SCR) on the client and all DataNodes.
 ** Run {{ozone debug checknative}} and verify that {{hadoop: true}} is 
displayed on the client and DataNodes.

 * Create an EC bucket, for example, {{{}RS-3-2{}}}.

 * Create a 200 MB key and identify the replica host.

 * Read the key from the replica host. and check the {{localBytesGetBlock}} 
metric increases.

 

Expected: 
 * The read succeeds and the data matches.
 * The client uses the normal read path via gRPC.
 * {{numLocalGetBlock}} and {{localBytesGetBlock}} stays 0 on every datanode, 
including the co-located one.

Actual: 
 * The read succeeds and the data matches.
 * {{numLocalGetBlock}} and {{localBytesGetBlock}} increases on the co-located 
datanode.

  was:
Short-circuit read is enabled on the cluster. An EC key is written and then 
read from a client running on the same host as a datanode.

An EC key must use the normal read path via gRPC. Short-circuit is for Ratis 
keys.

*Steps to Reproduce:*
 * Enable Short-Circuit Read (SCR) on the client and all DataNodes.

 ** Run {{ozone debug checknative}} and verify that {{hadoop: true}} is 
displayed on the client and DataNodes.

 * Create an EC bucket, for example, {{{}RS-3-2{}}}.

 * Create a 200 MB key and identify the replica host.

 * Read the key from the replica host. and check the {{localBytesGetBlock}} 
metric increases.

 

Expected: 
 * The read succeeds and the data matches.
 * The client uses the normal read path via gRPC.
 * {{numLocalGetBlock}} and {{localBytesGetBlock}} stays 0 on every datanode, 
including the co-located one.

Actual: 
 * The read succeeds and the data matches.
 * {{numLocalGetBlock}} and {{localBytesGetBlock}} increases on the co-located 
datanode.


> EC key is read by short-circuit on a co-located client
> ------------------------------------------------------
>
>                 Key: HDDS-17606
>                 URL: https://issues.apache.org/jira/browse/HDDS-17606
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Elavarasan Kathirvel
>            Priority: Major
>              Labels: short-circuit-read
>
> Short-circuit read is enabled on the cluster. An EC key is written and then 
> read from a client running on the same host as a datanode.
> An EC key must use the normal read path via gRPC. Short-circuit is for Ratis 
> keys.
> *Steps to Reproduce:*
>  * Enable Short-Circuit Read (SCR) on the client and all DataNodes.
>  ** Run {{ozone debug checknative}} and verify that {{hadoop: true}} is 
> displayed on the client and DataNodes.
>  * Create an EC bucket, for example, {{{}RS-3-2{}}}.
>  * Create a 200 MB key and identify the replica host.
>  * Read the key from the replica host. and check the {{localBytesGetBlock}} 
> metric increases.
>  
> Expected: 
>  * The read succeeds and the data matches.
>  * The client uses the normal read path via gRPC.
>  * {{numLocalGetBlock}} and {{localBytesGetBlock}} stays 0 on every datanode, 
> including the co-located one.
> Actual: 
>  * The read succeeds and the data matches.
>  * {{numLocalGetBlock}} and {{localBytesGetBlock}} increases on the 
> co-located datanode.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to