# Tez release notes by version


**Topics**
+ [

# Amazon EMR 7.10.0 - Tez release notes
](Tez-release-history-7100.md)
+ [

# Amazon EMR 7.9.0 - Tez release notes
](Tez-release-history-790.md)
+ [

# Amazon EMR 7.8.0 - Tez release notes
](Tez-release-history-780.md)
+ [

# Amazon EMR 7.7.0 - Tez release notes
](Tez-release-history-770.md)
+ [

# Amazon EMR 7.6.0 - Tez release notes
](Tez-release-history-760.md)
+ [

# Amazon EMR 7.5.0 - Tez release notes
](Tez-release-history-750.md)
+ [

# Amazon EMR 7.4.0 - Tez release notes
](Tez-release-history-740.md)
+ [

# Amazon EMR 7.3.0 - Tez release notes
](Tez-release-history-730.md)
+ [

# Amazon EMR 7.2.0 - Tez release notes
](Tez-release-history-720.md)
+ [

# Amazon EMR 7.1.0 - Tez release notes
](Tez-release-history-710.md)
+ [

# Amazon EMR 7.0.0 - Tez release notes
](Tez-release-history-700.md)
+ [

# Amazon EMR 6.15.0 - Tez release notes
](Tez-release-history-6150.md)
+ [

# Amazon EMR 6.14.0 - Tez release notes
](Tez-release-history-6140.md)
+ [

# Amazon EMR 6.13.0 - Tez release notes
](Tez-release-history-6130.md)
+ [

# Amazon EMR 6.12.0 - Tez release notes
](Tez-release-history-6120.md)
+ [

# Amazon EMR 6.11.0 - Tez release notes
](Tez-release-history-6110.md)
+ [

# Amazon EMR 6.10.0 - Tez release notes
](Tez-release-history-6100.md)
+ [

# Amazon EMR 6.9.0 - Tez release notes
](Tez-release-history-690.md)
+ [

# Amazon EMR 6.8.0 - Tez release notes
](Tez-release-history-680.md)
+ [

# Amazon EMR 6.7.0 - Tez release notes
](Tez-release-history-670.md)
+ [

# Amazon EMR 6.6.0 - Tez release notes
](Tez-release-history-660.md)

# Amazon EMR 7.10.0 - Tez release notes
7.10.0 release notes

## Amazon EMR 7.10.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Bug Fix | [TEZ-4595](https://issues.apache.org/jira/browse/TEZ-4595): Fixed a bug where Tez would crash when trying to process a new DAG while it was still recovering from a previous failure, causing both DAGs to interfere with each other and throw an INVALID\$1EVENT exception. | 

**Tez release notes**

Bug fix notes – The issue occurred when recovery files were present and the Application Master transitioned through RECOVERING → IDLE → RUNNING → IDLE states, creating a brief window where Hive could submit new DAGs during the IDLE → RUNNING transition. Modified the state transition logic to skip IDLE state when recovery files are present. The AM now follows RECOVERING → RUNNING → IDLE flow, ensuring new DAG submission only occurs after the recovered DAG is fully cleaned up.

# Amazon EMR 7.9.0 - Tez release notes
7.9.0 release notes

## Amazon EMR 7.9.0 - Tez changes
Tez changes

No changes for the 7.9.0 release.

# Amazon EMR 7.8.0 - Tez release notes
7.8.0 release notes

## Amazon EMR 7.8.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | Upgraded bouncycastle version to 1.78 to match hadoop | 

# Amazon EMR 7.7.0 - Tez release notes
7.7.0 release notes

## Amazon EMR 7.7.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | The tez.task.relaxed.locality property in Apache Tez controls whether task scheduling strictly follows data locality constraints (rack and node locality). When set to true (default in EMR-7.6\$1), Tez does not enforce locality, allowing tasks to be assigned to any available container, which improves resource utilization and reduces wait times in busy clusters. | 

# Amazon EMR 7.6.0 - Tez release notes
7.6.0 release notes

## Amazon EMR 7.6.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | Rack and node locality constraints won't be considered while requesting container for a task by changing default of tez.task.relaxed.locality to false | 
| Improvement | Tune configs to disable delay due to locality and allow non-local fallback | 
| Improvement | [TEZ-4547](https://issues.apache.org/jira/browse/TEZ-4547): Add Tez AM JobID to the JobConf | 

# Amazon EMR 7.5.0 - Tez release notes
7.5.0 release notes

## Amazon EMR 7.5.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | Enabled preemption of task by default | 
| Improvement | Increased number of record readers to asynchronously and proactively init to 10 | 
| Improvement | [TEZ-4580](https://issues.apache.org/jira/browse/TEZ-4580): Slow preemption of new containers when re-use is enabled | 

# Amazon EMR 7.4.0 - Tez release notes
7.4.0 release notes

## Amazon EMR 7.4.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | Remove EventCounter appender from Tez removed in Hadoop 3.4.0 via [HADOOP-17524](https://issues.apache.org/jira/browse/HADOOP-17524) | 
| Upgrade | Upgrade commons-cli to 1.5.0 | 
| Upgrade | Upgrade bouncy-castle version to 1.70.0 | 

# Amazon EMR 7.3.0 - Tez release notes
7.3.0 release notes

## Amazon EMR 7.3.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | Provide option to enable SSL for Tez AM Web UI Service | 
|  |  | 

## Amazon EMR 7.3.0 - New configurations
Amazon EMR 7.3.0 - New configurations


****  

| Classification | Name | Default | Description | 
| --- | --- | --- | --- | 
| tez-site | tez.am.tez-ui.webservice.enable.ssl | false | Allow enabling SSL for for the AM WebUIService | 
| tez-site | tez.am.tez-ui.webservice.enable.client.auth | false | Allow enabling client side authentication for the AM WebUIService | 

**Amazon EMR 7.3.0 - Tez known issues**

**Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

**Fix version:** – EMR 7.3.0

**Workaround** – Add the following SSL configuration to tez-site.xml:

```
<property>
    <name>ssl.client.truststore.location</name>
    <value>{SSL_TRUSTSTORE_LOCATION}</value>
</property>
```

# Amazon EMR 7.2.0 - Tez release notes
7.2.0 release notes

## Amazon EMR 7.2.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | Option provided to disable locality constraints when requesting containers for tasks. | 
| Bug Fix | Make TaskDependencies\$1addTaskDependency thread safe | 
| Upgrade | Upgrade TLS version to 1.3 for Tez. | 

## Amazon EMR 7.2.0 - New configurations
Amazon EMR 7.2.0 - New configurations


****  

| Classification | Name | Default | Description | 
| --- | --- | --- | --- | 
| tez-site | tez.task.relaxed.locality | false | When enabled, rack and node locality constraints are not considered while requesting a container for a task. | 

**Amazon EMR 7.2.0 - Tez known issues**

**Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

**Fix version:** – EMR 7.3.0

**Workaround** – Add the following SSL configuration to tez-site.xml:

```
<property>
    <name>ssl.client.truststore.location</name>
    <value>{SSL_TRUSTSTORE_LOCATION}</value>
</property>
```

# Amazon EMR 7.1.0 - Tez release notes
7.1.0 release notes

## Amazon EMR 7.1.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Bug Fix | [TEZ-4394](https://issues.apache.org/jira/browse/TEZ-4394) – Netty4 ShuffleHandler: should use 1 boss thread (\$1256)  | 
| Upgrade | Upgrades Netty to 4.1.100.Final. | 
| Upgrade | Upgrades Jetty to 9.4.53.v20231009. | 

**Amazon EMR 7.1.0 - Tez known issues**
+ **Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

  **Fix version:** – EMR 7.3.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

# Amazon EMR 7.0.0 - Tez release notes
7.0.0 release notes

Amazon EMR 7.0.0 Tez contains all the changes and updates made up to and including Amazon EMR-6.15.0 Tez.

## Amazon EMR 7.0.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Upgrade | Tez Runtime now uses Java 17 by default. Please refer [EMR 7.0.0 Release Guide](https://docs.amazonaws.cn/emr/latest/ReleaseGuide/emr-700-release.html) for more details. | 

**Amazon EMR 7.0.0 - Tez known issues**
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

  **Fix version:** – EMR 7.3.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

# Amazon EMR 6.15.0 - Tez release notes
6.15.0 release notes

## Amazon EMR 6.15.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Feature | [TEZ-4397](https://issues.apache.org/jira/browse/TEZ-4397): Open Tez Input splits asynchronously | 
| Upgrade | [TEZ-4493](https://issues.apache.org/jira/browse/TEZ-4493): Upgrade Apache Hadoop to 3.3.6 | 

**Amazon EMR 6.15.0 - Tez known issues**
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

  **Fix version:** – EMR 7.3.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

## Amazon EMR 6.15.0 - Tez features
Tez features
+ **[Tez asynchronous split opening](tez-configure.md#tez-configure-async)** – Amazon EMR 6.15.0 introduces configurations that you can specify to asynchronously open the input splits in a Tez *grouped split*. The feature was initiated by [TEZ-4397](https://issues.apache.org/jira/browse/TEZ-4397), but had regressions in OSS Hive. Amazon EMR Hive fixed the regressions and additional bugs in Hive ACID table. This improvement results in faster performance of read queries when there are a large number of input splits in a single Tez grouped split. For more information, see [Tez asynchronous split opening](tez-configure.md#tez-configure-async).

# Amazon EMR 6.14.0 - Tez release notes
6.14.0 release notes

## Amazon EMR 6.14.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | Upgrade TLS version in Tez to 1.2 | 

**Amazon EMR 6.14.0 - Tez known issues**
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

  **Fix version:** – EMR 7.3.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

# Amazon EMR 6.13.0 - Tez release notes
6.13.0 release notes

## Amazon EMR 6.13.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Bug Fix | REVERT [TEZ-4295](https://issues.apache.org/jira/browse/TEZ-4295): Could not decompress data. Buffer length is too small. | 
| Bug Fix | REVERT [TEZ-4302](https://issues.apache.org/jira/browse/TEZ-4302): NullPointerException in CodecUtils with GzipCodec. | 
| Bug Fix | REVERT [TEZ-4234](https://issues.apache.org/jira/browse/TEZ-4234): Compressor can cause IllegalArgumentException in Buffer.limit where limit exceeds capacity. | 
| Bug Fix | REVERT [TEZ-4135](https://issues.apache.org/jira/browse/TEZ-4135): Improve memory allocation when executing in-memory reads. | 

**Amazon EMR 6.13.0 - Tez known issues**
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

  **Fix version:** – EMR 7.3.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

# Amazon EMR 6.12.0 - Tez release notes
6.12.0 release notes

## Amazon EMR 6.12.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Improvement | Added Support For JDK 11 and JDK 17 Runtime | 
| Bug Fix | [TEZ-4492](https://issues.apache.org/jira/browse/TEZ-4492): Update Bowerrc to use bower.herokuapp mirror to avoid Bower Registry CERT\$1EXPIRE issue (BOWER-2608) | 
| Upgrade | Upgraded Surefire to 3.0.0-M7  | 

**Amazon EMR 6.12.0 - Tez known issues**
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

  **Fix version:** – EMR 7.3.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

# Amazon EMR 6.11.0 - Tez release notes
6.11.0 release notes

## Amazon EMR 6.11.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Bug | Fixed invalid vertex state transition during vertex level cleanup of shuffle data | 
| Bug | Fixed DAG or vertex level cleanup of shuffle data not working | 
| Improvement | Enable tez.am.dag.cleanup.on.completion by default for clearing shuffle data of completed DAGs | 

**Amazon EMR 6.11.0 - Tez known issues**
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Tez DAG cleanup issue (EMR 6.11.0 - EMR 7.2.0)** – In clusters with SSL enabled running EMR versions 6.11.0 to 7.2.0, there is a known issue where *SSLHandshakeException* occurs in TEZ Application Master (AM) during the DAG cleanup phase. This happens when attempting to delete intermediate shuffle data from remote nodes over HTTPS after query completion, not during the query execution. The issue occurs because Tez AM cannot read the relevant **trustStore** configuration when calling the shuffle handler service endpoint. However this affects only the cleaning up of shuffle data during DAG cleanup, the application(AM) level cleanup happens anyways and cleans up any lingering shuffle data. So this doesn’t lead to shuffle data accumulation. 

  **Fix version:** – EMR 7.3.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

# Amazon EMR 6.10.0 - Tez release notes
6.10.0 release notes

## Amazon EMR 6.10.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Feature | Enable tez.runtime.transfer.data-via-events.enabled by default | 
| Backport | [TEZ-4450](https://issues.apache.org/jira/browse/TEZ-4450): Fix shuffle data fetch failure when shuffle data is transferred via data movement events | 
| Backport | [TEZ-4460](https://issues.apache.org/jira/browse/TEZ-4460): Fix read timeout error in fetching shuffle data from Tez Shuffle Handler | 
| Backport | [TEZ-4455](https://issues.apache.org/jira/browse/TEZ-4455): Add LoggingHandler in ShuffleHandler pipeline for better debuggability | 
| Bug | Fix Tez task getting stuck intermittently when preemption of task is enabled | 

**Amazon EMR 6.10.0 - Tez known issues**
+ **Hive jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0, there is a known issue where Hive jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Hive).

  **Fix version:** – EMR 6.10.0

  **Workaround for version 6.9** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

# Amazon EMR 6.9.0 - Tez release notes
6.9.0 release notes

## Amazon EMR 6.9.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Upgrade | Tez is upgraded to 0.10.2. For more information, see the [change log for Apache Tez 0.10.2](https://github.com/apache/tez/blob/rel/release-0.10.2/CHANGES.txt). | 
| Upgrade | Upgrade Hadoop to 3.3.3. | 
| Bug | Disable tez.runtime.transfer.data-via-events.enabled by default due to [TEZ-4450](https://issues.apache.org/jira/browse/TEZ-4450). | 

**Amazon EMR 6.9.0 - Tez known issues**
+ **Hive jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0, there is a known issue where Hive jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Hive).

  **Fix version:** – EMR 6.10.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```
+ **Pig jobs running on Tez** – In clusters with SSL enabled running EMR version 6.9.0 to 7.0.0, there is a known issue where Pig jobs running on Tez fail with *SSLHandshakeException*. This is related to the open-source issue [TEZ-4096](https://issues.apache.org/jira/browse/TEZ-4096), which was introduced with the Tez upgrade to version 0.10.2 in EMR 6.9.0. The issue requires SSL-related configurations to be passed from the client side (Pig).

  **Fix version:** – EMR 7.1.0

  **Workaround** – Add the following SSL configuration to tez-site.xml:

  ```
  <property>
      <name>ssl.client.truststore.location</name>
      <value>{SSL_TRUSTSTORE_LOCATION}</value>
  </property>
  ```

# Amazon EMR 6.8.0 - Tez release notes
6.8.0 release notes

## Amazon EMR 6.8.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Backport | [TEZ-3363](https://issues.apache.org/jira/browse/TEZ-3363): Delete intermediate data at the vertex level for Shuffle Handler | 
| Backport | [TEZ-4129](https://issues.apache.org/jira/browse/TEZ-4129): Delete intermediate attempt data for failed attempts for Shuffle Handler | 
| Backport | [TEZ-4430](https://issues.apache.org/jira/browse/TEZ-4430): Fixed tez.task.launch.cmd-opts property not working | 

# Amazon EMR 6.7.0 - Tez release notes
6.7.0 release notes

## Amazon EMR 6.7.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Backport | [TEZ-4403](https://issues.apache.org/jira/browse/TEZ-4403): Upgrade SLF4J version to 1.7.36 | 
| Backport | [TEZ-4405](https://issues.apache.org/jira/browse/TEZ-4405): Replace log4j 1.x with reload4j | 
| Backport | [TEZ-4411](https://issues.apache.org/jira/browse/TEZ-4411): Tez Build Failure: FileSaver.js not found | 

# Amazon EMR 6.6.0 - Tez release notes
6.6.0 release notes

## Amazon EMR 6.6.0 - Tez changes
Tez changes


| Type | Description | 
| --- | --- | 
| Backport | [TEZ-3918](https://issues.apache.org/jira/browse/TEZ-3918): Fixed tez.task.log.level property not working. | 
| Backport | [TEZ-4353](https://issues.apache.org/jira/browse/TEZ-4353): Update commons-io to 2.8.0. | 
| Backport | [TEZ-4114](https://issues.apache.org/jira/browse/TEZ-4114): Remove direct jetty dependency from tez. | 
| Backport | [TEZ-4323](https://issues.apache.org/jira/browse/TEZ-4323): Jetty jars were removed from dist package with TEZ-4114. |