MapR-FS

Setup and Best Practices

Container Location Databases (CLDBs)

When adding a MapR-FS data source, be sure to list each node that runs a CLDB in your cluster. This will allow Dremio to continue to query the source in the event of a CLDB node failure.

Colocation

For all but the most robust network hardware, colocating Dremio nodes with MapR-FS datanodes can lead to noticeably reduced data transfer times and more performant query execution.

Parquet File Performance

When HDFS data is stored in the Parquet file format, then optimal performance is achieved by storing one Parquet row group per file, with a file size less than or equal to the MapR-FS chunk size. Parquet files that overrun the MapR-FS chunk size can negatively impact query times by incurring a considerable amount of filesystem overhead.

NOTE: Ensure that your Dremio cluster has access to the appropriate ports for each node of your MapR-FS source. By default this should be port 7222 for CLDB processes (which should be the one specified when adding the CLDBs of the cluster in the source dialog), as well as ports 5660 and 6660 which are used for internal purposes.

MapR Cluster Names

Dremio does not support MapR cluster names that are non-URI qualified (e.g. containing "_" character). Instead users should use an alias. This alias has to be added to mapr-clusters.conf on all the nodes of the cluster.

Here is a sample entry and command to generate a maprticket for a given alias:

mycluster_test secure=true 123.0.0.1:7222
bestcluster secure=true 123.0.0.2:7222

maprlogin password -cluster bestcluster

Dremio and MapR-FS

Impersonation and Ownership Chaining

You can enable flexible control over file permissions by turning on impersonation in MapR-FS sources (check the 'impersonation' box in the source connection dialog). This means that users who access data stored on this source will have their access mediated by the MapR-FS privileges associated with their Dremio login name, rather than the ones associated with the Dremio daemon.

Enabling impersonation also permits a kind of behavior called 'ownership chaining.' Under ownership chaining, MapR-FS data which is subject to restricted access can be shared with any other Dremio users via the creation of a virtual dataset in a public (non-Home) space.

Dremio Configuration

General

  • Cluster Name -- MapR Cluster name.
  • Enable Impersonation
  • Encrypt Connection -- Specifies whether the cluster is secure or not.

Advanced Options

  • Enable exports into the source (CTAS and DROP).
  • Root Path -- Root path for the source.
  • Connection Properties -- A list of additional connection properties.

    Reflection Refresh

  • Never refresh -- Specifies how often to refresh based on hours, days, weeks, or never.
  • Never expire -- Specifies how often to expire based on hours, days, weeks, or never.

    Metadata

Dataset Handling

  • Remove dataset definitions if underlying data is unavailable (Default).
    If this box is not checked and the underlying files under a folder are removed or the folder/source is not accessible, Dremio does not remove the dataset definitions. This option is useful in cases when files are temporarily deleted and put back in place with new sets of files.
  • Automatically format files into physical datasets when users issue queries. If this box is checked and a query runs against the un-promoted PDS/folder, Dremio automatically promotes using default options. If you have CSV files, especially with non-default options, it might be useful to not check this box.

Metadata Refresh

  • Dataset Details -- The metadata that Dremio needs for query planning such as information needed for fields, types, shards, statistics, and locality.
    • Fetch mode -- Specify either Only Queried Datasets, All Datasets, or As Needed. Default: Only Queried Datasets
      • Only Queried Datasets -- Dremio updates details for previously queried objects in a source.
        This mode increases query performance because less work is needed at query time for these datasets.
      • All Datasets -- Dremio updates details for all datasets in a source. This mode increases query performance because less work is needed at query time.
      • As Needed -- Dremio updates details for a dataset at query time. This mode minimized metadata queries on a source when not used, but might lead to longer planning times.
    • Fetch every -- Specify fetch time based on minutes, hours, days, or weeks. Default: 1 hour
    • Expire after -- Specify expiration time based on minutes, hours, days, or weeks. Default: 3 hours
  • Authorization -- When impersonation is enabled, the maximum amount of time that Dremio will cache authorization information.

    Sharing

You can specify which users can edit. Options include:

  • All users can edit.
  • Specific users can edit.

results matching ""

    No results matching ""