About Domino
Domino Data LabKnowledge BaseData Science BlogTraining

Domino 5.6.0 (May 2023)

See also the fleetcommand-agent Release Notes.

Validated frameworks

The following versions have been validated with Domino 5.6.0. Other versions might be compatible, but are not guaranteed.

New features

Project templates

Project Templates allow you to designate approved Git-based projects in Domino as template projects for everyone in your organization. This reduces the time required to set up new data science work and lets you evangelize best practices and standards in Domino projects. See Project Templates for details.

Multi-storage account support for datasets

Now you can configure additional storage accounts for new datasets and snapshots. Updates to existing datasets and snapshots are made in their original storage location. See Set Up Multiple Storage Accounts.

Experiment management GA

Domino experiment management leverages MLflow Tracking to enable easy logging of experiment parameters, metrics, and artifacts, while providing a Domino-native user experience to help you analyze your results. MLflow runs as a service in your Domino cluster, fully integrated within your workspace and jobs, and honoring role-based access control. Existing MLflow experiments works right out of the box with no code changes required.

In this GA release, we have added a comparison view, the ability to view time-series metrics, and is fully supported in hybrid environments.

See Track and monitor experiments for complete details.

Data source support in Domino Nexus

Data sources are no longer in Preview for Domino Nexus.

Admins now have the ability to create data sources and configure which data planes they are accessible from.

Health checkups and diagnostics

The Fleetcommand CLI is extended to support registering existing Domino instances into Fleetcommand.

In-app feedback channel

Your input helps us prioritize development work that makes a difference to our customers. Now you can send feedback to Domino Data Lab straight from the Domino UI.

You can suggest new features or improvements, tell us about your experience using the product, and include screenshots to illustrate your feedback. Optionally, you can consent to being contacted by Domino for further discussion.

Click Feedback in the side nav to open the feedback window:

Send feedback

Improvements

  • Feature store (public preview)

    Domino’s feature store comes with these improvements in Domino 5.6.0:

    • The search feature in the global registry is improved to help you locate specific features and feature views.

    • The global registry now displays feature metadata so you can identify the features and feature views you need for your project.

    • Admins can now set up the online store in the Domino UI when they enable the feature store.

    • The documentation now includes a Feature Store Quickstart with a simple end-to-end example of how to publish and use a feature.

    The feature store remains a public preview feature in this release.

  • UI improvements

    This release includes a more performant and memory-efficient UI. Additionally, the project menu has a new layout:

    5.5 default project menu5.6 project menu

    5.5 project menu

    5.6 project menu

    In Domino 5.5, the new layout appeared only when the experiment management feature was explicitly enabled. In this release, the new layout always appears.

  • A Terraform module that enables automated provisioning of EKS infrastructure without the use of the AWS CDK. See the provisioning guide.

  • The com.cerebro.domino.workbench.experimentManagement.enabled is deprecated; the experiment management feature is now always enabled.

API changes

  • A new public API endpoint at /api/projects/v1/projects/{project_id}/copy-project copies a Git-based project to use as a template for a new project. See Project Templates for examples. This endpoint is no longer in beta. The path at /api/projects/beta/projects/{project_id}/copy-project is deprecated and will be removed in a future release.

Bug fixes

  • Users can see raw files whose size is ⇐ 5 MB (com.cerebro.domino.frontend.defaultMaxFileSizeToRenderInBytes) when they click on the "View Latest Raw File" button in the code file browser, even if their S3 buckets don’t have CORS enabled.

Known issues

  • S3 buckets must have CORS enabled in order to use "View Latest Raw File" button in the code file browser if the file is > 5 MB (com.cerebro.domino.frontend.defaultMaxFileSizeToRenderInBytes). As a workaround, use the Download button to download larger files and view them on your computer.

  • In Azure Blob Store deployments, projects with many files may fail to sync through the Domino CLI. To work around this issue, do not disable file locking when prompted by Domino.

  • You cannot view the latest raw file. In the navigation pane, go to Files and click a file to view its details. If you click View Latest Raw File, a blank page opens.

  • When uploading a large file to the Azure blob store by syncing a workspace, you may encounter a Java Out of Memory error from Azure if the file/blob already exists. To work around this issue, use the Domino CLI to upload the file to the project.

  • Model Monitoring data sources aren’t validated. If you enter an invalid bucket name and attempt to save, the entry will go through. However, you won’t be able to see metrics for that entry because the name points to an invalid bucket.

  • Domino instances that make use of Azure Blob Storage may experience stalled jobs within projects with many large files.

  • When using Azure Blob Storage for backups, daily backups do not complete successfully and backups are only stored in Azure Files storage.

This issue is resolved in Domino 5.6.1.

  • Upgrading Domino from a version below 5.5.0 to version 5.6.0 on Azure AFS may fail if the Keycloak script providers were previously configured on your instance. Contact Domino Support for help.

This issue is resolved in Domino 5.7.0.

  • If you attach a Git repository to a DFS project that points to a tagged release, the tag won’t be honored when building a model API in that project. The build log will show an error similar to the following, and the model will be built using the default branch of your Git repository instead of the tagged branch:

    Jul 05 2023 14:36:27 -0500 #10 6.481 WARN [d.r.d.GitRepoUpdater] could not parse ref: v1.3.0 checking out default branch correlationId="iA2qWrYSLQ" thread="main"

    To work around this issue, use the branch name when building model APIs instead of the release tag.

  • If the nucleus-dispatcher Kubernetes pod is restarted (during Domino upgrade, after restarting Nucleus services via the admin central configuration page, after the previous pod crashing, or for some other reason), then existing executions (including workspaces and jobs) may fail. This issue is resolved in Domino 5.6.2.

  • The Status, Active Version, and Owner columns do not appear in the Model API list. This issue is fixed in Domino 5.8.0.

  • Deleting all R variables from memory using rm(list = ls(al = TRUE)) also deletes variables that Domino uses for internal processes. To safely delete variables, use rm(list = ls(all = TRUE)[!grepl("^.domino", ls(all = TRUE))]) instead."

  • When restarting a Workspace through the Update Settings modal, External Data Volumes are not mounted in the new Workspace. Follow the steps to mount External Data Volumes. This issue is fixed in Domino 5.9.0.

  • Downloading single files from Datasets will fail if the filename contains special characters, including + and &. As a workaround, remove the mentioned special characters by renaming the file. This issue is fixed in Domino 5.10.0.

  • EDV page may be slow to load when a large number of volumes are registered.

  • Spaces in ADLS filenames are not allowed when getting and putting objects in Azure Data Sources with DominoDataR. As a workaround, upgrade to DominoDataR version 0.2.4. This issue is fixed in Domino 5.10.0.

  • Viewing dataset files in an Azure-based Domino cluster may lock files, preventing them from being deleted or modified. Restarting Nucleus frontend pods will release the lock. This issue is fixed in Domino 5.11.1.

Upgrade notes

Important
 If you are upgrading to this Domino release from a version earlier than Domino 5.3.0, you must put Domino into maintenance mode to avoid losing work. Maintenance mode pauses all apps, model APIs, restartable workspaces, and scheduled jobs. Allow running jobs to complete or stop them manually.