AnzoGraph 2.0 Releases

To view the release notes for an AnzoGraph 2.0 version, select the version from the list below. The release notes for each version describe the product changes from the previous version.

If you are upgrading to 2.0.x from a previous release, see AnzoGraph 2.0 Installation and Upgrade Notes for important notes about upgrades.

AnzoGraph Version 2.0.1

This section describes the improvements and issues that were fixed in AnzoGraph Version 2.0.1.

Improved Performance for Elasticsearch Service Calls

Version 2.0.1 includes performance improvements for the execution of the service calls that Elasticsearch makes for unstructured text searches. For more information, see Elasticsearch Performance Improvements.

As part of the performance enhancement, AnzoGraph now communicates with Elasticsearch directly. Previously, Anzo was an intermediary between AnzoGraph and Elasticsearch. After installing AnzoGraph 2.0.1, see Configuring AnzoGraph for Use with Elasticsearch for instructions on setting up AnzoGraph to communicate with Elasticsearch.

Ability to Load Data from Kerberized HDFS Clusters

Version 2.0.1 adds support for reading files directly from HDFS clusters that use the Kerberos authentication protocol. For instructions on configuring AnzoGraph to authenticate with Kerberos, see Configuring AnzoGraph for Kerberos Authentication in the Anzo Deployment and User Guide. Note that AnzoGraph cannot write to HDFS.

More Informative Error Messages on Startup

Version 2.0.1 adds more information to error messages that are received if AnzoGraph fails to start. Previously, users had to view the system management log (azgmgrd.log) to see more detailed messages. The complete message is now displayed on the command line.

Invalid Multi-Byte Character URL Encoding

The URL encoding of multi-byte characters in TOPDOWN SERVICE calls was invalid and prevented users from being able to search for Japanese and Chinese characters in Elasticsearch. Version 2.0.1 corrects the URL encoding for multi-byte characters.

AnzoGraph Version 2.0.0

This section describes the new features and changes to existing components that are introduced in AnzoGraph Version 2.0.0.

AnzoGraph Version Number Changed to 2.0.0

AnzoGraph now aligns with Anzo's semantics for release version numbering. This version numbering scheme change was made to reduce customer confusion for issue reporting and support. It also enables Anzo and AnzoGraph to independently schedule releases that are appropriate for their markets. Future releases of Anzo will specify the versions of AnzoGraph that are certified with that release of Anzo.

Modified AnzoGraph Installer

The installation script for AnzoGraph 2.0.0 has been modified to clarify options, simplify steps, and eliminate the Nginx SSL Authentication Proxy option since it is no longer needed—Anzo connects to AnzoGraph over gRPC and AnzoGraph includes an SSL protocol port that can be enabled if needed. For more information, see Installing AnzoGraph in the Anzo Deployment and User Guide.

AnzoGraph Settings File Lists all Basic and Advanced Settings and Descriptions

In AnzoGraph Version 2.0.0, the settings configuration file, settings.conf, enumerates all of the basic and advanced level AnzoGraph settings so that users can review the file and see the options that are available for configuration.

The following AnzoGraph settings were renamed in settings.conf. However, AnzoGraph continues to support the old names, and the default values were not changed:

Old Name New Name
allow_alternate_vm_config_against_recommendations os_allow_alternate_vm_config
allow_small_map_against_recommendations os_allow_small_mmap
allow_thp_against_recommendations os_allow_thp
sbxmgr_password azgmgrd_password
load_persistance load_persistence

Option to Relocate AnzoGraph Log Files

AnzoGraph Version 2.0.0 enables users to configure an alternate location for AnzoGraph log files. In previous versions, the location of the logs could not be changed. The AnzoGraph database logs (boot.log, compile-errors.log, compile.log debug.log, and warnings.log) were written to the <install_path>/internal/log directory, and the system management logs (azgmgrd.log, azgpidmgr.log, and azgpids.log) were written to the /tmp directory.

Version 2.0.0 introduces the following new settings that control the location of the log files and the size and amount of history to keep in the system manager log (azgmgrd.log):

  • log_directory: This setting specifies the path and directory to write logs to. If you specify a directory that does not exist, AnzoGraph creates it. The setting affects all of the logs described above. Small, user-related logs (such as azgctl-user.log) will continue to be written to the /tmp directory.

    Important: Changing this setting requires restarting the system management daemon, azgmgrd. The azgmgrd.log will not be written to the new location until azgmgrd is restarted.

  • log_size_limit: This setting controls the file size of azgmgrd.log. Once a file grows to the maximum size, AnzoGraph will start writing to a new file.
  • log_rotate_counter: This setting controls the number of azgmgrd.log files to keep. When the limit is reached, AnzoGraph deletes the oldest file before writing a new one.
Related Topics