Connecting to a File Store

This topic provides instructions for connecting to an additional shared file system that Anzo applications can read from and write to during the onboarding processes. At least one file store needs to be shared between Anzo, AnzoGraph, and any Anzo Unstructured, Elasticsearch, or Spark servers. In almost all cases, organizations create an NFS to mount to all of the servers in the Anzo environment. Mounted file systems typically offer the best performance for reading and writing files. For more information, see Deploying the Shared File System.

Anzo supports reading from and writing to local or mounted file systems (such as NFS), Hadoop Distributed File Systems (HDFS), File Transfer Protocol (FTP or FTPS) systems, Google Cloud Platform (GCP) storage, and Amazon Simple Cloud Storage Service (S3).

  1. In the Administration application, expand the Connections menu and click File Store. Anzo displays the File Store screen, which lists existing file store connections. For example:

  2. Click the Add File Connection button and select the type of file connection that you want to create. For the local disk or mounted NFS, choose Local File Connection. Anzo displays the create connection screen for the type of connection you chose.
  3. On the connection screen, provide the file system details. The settings that display depend on the type of file connection that you chose. The list below describes the settings for each file connection type. Click a connection type to view the settings for that type:

    • Name: The name to use to describe this file connection within Anzo.
    • Base Folder: The base or root folder on the file system where you want Anzo to either read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
    • Globally accessible filesystem: Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the AnzoGraph leader server can access this system, leave this option blank.

    • Name: The name to use to describe this file connection within Anzo.
    • Nameservice IP or Name: The IP address or host name for the storage system.
    • Port: The RPC port to access the server on. The default RPC port is 8020.
    • Base Folder: The base or root folder on the file system where you want Anzo to either read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
    • HDFS Configuration Path: Enter the full path to the configuration files.
    • Keytab Path: The full path to the keytab file.
    • Username: The user name for the account used to access the server.
    • Password and Confirm Password: The password for the account used to access the server.
    • Nameservice Rest IP or Name: The HTTP REST IP address or host name. Typically this value is the same as the Nameservice IP or Name.
    • Nameservice Rest Port: The HTTP port. AnzoGraph uses this port to access HDFS and load the FLDS. The default HTTP port for the namenode is 9870.
    • Nameservice Rest Protocol: The protocol to use for requests. Specify one of the following values:
      • hdfs: Specify hdfs for non-secure HTTP protocol.
      • shdfs: Specify shdfs for secure HTTPS protocol.
      • khdfs: Specify khdfs for non-secure HTTP protocol with Kerberos authentication.
      • kshdfs: Specify kshdfs for secure HTTPS protocol with Kerberos authentication.

      If you use Kerberos Authentication with HDFS, you must also configure your AnzoGraph cluster to authenticate with Kerberos. For instructions, see Configuring AnzoGraph for Kerberos Authentication.

    • Globally accessible filesystem: Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the AnzoGraph leader server can access this system, leave this option blank.

    • Name: The name to use to describe this file connection within Anzo.
    • Server IP or Name: The IP address or host name for the storage system.
    • Port: The port to access the server on.
    • Base Folder: The base or root folder on the file system where you want Anzo to either read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
    • Username: The user name for the account used to access the server.
    • Password and Confirm Password: The password for the account used to access the server.
    • Keystore Path: For FTPS connections, the full path to the keystore file.
    • Globally accessible filesystem: Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the AnzoGraph leader server can access this system, leave this option blank.

    • Name: The name to use to describe this file connection within Anzo.
    • Bucket Name: The name of the bucket to store files in.
    • Base Folder: The base or root folder on the file system where you want Anzo to either read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
    • Account Email: The email address for the account used to access the storage.
    • Key File Location: The full path to the keystore password file.
    • Globally accessible filesystem: Select this option if this file store is accessible by all of the servers in an AnzoGraph cluster. If only the AnzoGraph leader server can access this system, leave this option blank.

    When using Amazon S3 for file storage, do not use client-side encryption, where data is encrypted before it is sent to Amazon S3. Anzo cannot read files on S3 if the object store uses client-side encryption.

    • Name: The name to use to describe this file connection within Anzo.
    • Bucket Name: The name of the bucket to store files in.
    • Base Folder: The base or root folder on the file system where you want Anzo to either read or write files. Each time Anzo generates new files it creates a new subdirectory under this base location.
    • Access Key: The Access Key ID to use for accessing the S3 location.
    • Secret Key and Confirm Secret Key: The Secret Key ID for the Access Key.
    • S3 URI Scheme: Specifies whether the URI scheme is S3, S3 Native, or S3A.
    • Globally accessible filesystem: Required. Enable this option for S3 file stores.
  4. Click Save to save the configuration. The file store connection that you specified becomes available as a choice when you create graph data stores or select source files to onboard.

Related Topics