Review the list of Oozie issues that are resolved in Cloudera Runtime 7.3.1, its service packs and cumulative hotfixes.
Cloudera Runtime 7.3.1.400 SP2
- CDPD-84224:
test_oracle_import_with_arithmetic_exception fails due to missing error
message in YARN log
- 7.3.1.400
- The Sqoop binary was not correctly updated on
the Oozie sharelib, hence the pre-upgrade version of the Sqoop was used,
which did not contain the necessary log message. After resolving that issue,
the affected executions are now successful.
- CDPD-78506: Fix PATH environment variable creation for
Shell action
- 7.3.1.400
- With this fix, in Oozie's shell actions, the
PATH environment variable is evaluated based on the YARN NodeManager host's
settings. So, the PATH environment variable applies to the Launcher AM
container when executed, rather than being evaluated on the Oozie server's
JVM (the legacy method). You can revert to the legacy behavior by
setting oozie.action.shell.setup-path-in-oozie-server
to true in oozie-site.xml.Also, from now, Oozie also
allows defining action-specific environment variables using
oozie.launcher.<***ACTION_TYPE***>.action.env.<***VARIABLE_NAME***>
allowing you to customize execution environments for each action type in
the Launcher AM.
Cloudera Runtime 7.3.1.300 SP1 CHF 1
There are no fixed issues in this release.
Cloudera Runtime 7.3.1.200 SP1
- CDPD-78069: Oozie action configuration's Java opts are
not applied after CDPD-60551
- 7.3.1.200
-
Added the ability to configure a list of Hadoop properties that can be
passed to the Oozie launcher configuration, if they are not already set
in Oozie through oozie.launcher.<hadoop property
key> or within its workflows.
The default properties in this list are:
yarn.app.mapreduce.am.admin-command-opts and
yarn.app.mapreduce.am.command-opts. These defaults
can be overridden by setting a comma-separated list in the
oozie.service.HadoopAccessorService.global.yarn.java-options-keys
property. The
oozie.LauncherConfigurationInjector.hadoop.search.properties
is now deprecated.
Cloudera Runtime 7.3.1.100 CHF 1
- CDPD-68425: Oozie should validate the backend database
identifiers in a case-insensitive way
- 7.3.1.100
- Resolved an issue where Oozie incorrectly reported
missing tables due to issues with table name casing.
- CDPD-76135: Schema check database connection throws
PSQLException
- 7.3.1.100
- The schema check now completes successfully during
Oozie startup for secure database connections or when custom connection
properties are used, preventing warnings from appearing in the logs.
Cloudera Runtime 7.3.1
- CDPD-70422: Cannot enforce Oozie parameter
oozie.http.hostname
- 7.3.1
- A new property named
oozie.http.bind.hostname is now introduced to specify
the interface that the Oozie Server must be using. This overrides
oozie.http.hostname set by Cloudera Manager for both HTTP and HTTPS.
- CDPD-71117: Oozie server does not pass action start
time to action conf causes a restarting launcher doesn't find child
apps
- 7.3.1
- Whenever Yarn restarted the Oozie Launcher AM,
Oozie could not find the previously started child jobs due to a missing
original start timestamp from the Oozie Server. And the previously started
child Jobs were not terminated when the Launcher AM was restarted. This
issue is now resolved.
- CDPD-48664: Retry mechanism anomaly in Oozie with High
Availability enabled
- 7.3.1
- There was an issue with the retry mechanism in
Oozie when High Availability was enabled. This issue is now resolved.
- CDPD-49745: Expand app_path column in *_JOBS tables to
allow HDFS paths longer than 255 characters
- 7.3.1
- The APP_PATH column now supports storing paths
longer than 255 characters.
