Administration of the MapR-DB is done primarily via the command line (maprcli) or with the MapR Control System (MCS). Regardless of whether the MapR-DB table is used for binary files or JSON documents, the same types of commands are used with slightly different parameter options. MapR-DB administration is associated with tables, columns and column families, and table regions.

The MapR Data Access Gateway is a service that acts as a proxy and gateway for translating requests between lightweight client applications and the MapR cluster. This section describes considerations when upgrading the service, how to modify configuration settings, and how to administer and manage the service.

Cluster Maintenance Schedule

A maintenance schedule shows which tasks a cluster administrator
should perform daily, weekly, monthly, and quarterly, as well as
initial setup tasks. This sample schedule is offered as a template
that you can customize to suit your needs.

Initial Setup

Daily

Weekly

Monthly

Quarterly

Perform hardware checks

Check alarms

Check logs
(cluster and job logs)

Clean up logs

Audit storage use

Check Prerequisites

Onboard new users

Check for zombie jobs

Reevaluate node and
volume topology

Perform security audit

Verify Installation

Offboard users

Perform simple performance test

Check performance
(jobs, I/O)

Upgrade MapR core, Hive, HCatalog

High Availability planning

Check cluster health

Verify snapshots

Verify mirrors

Set up VIPs for NFS

Perform hardware maintenance
(disks)

Remove old snapshots

Clean up data

Benchmark and tuning

Failbacks to restore service layout

MapR-FS balancing

Set up node and volume topologies

Capacity planning

Upgrade ecosystem components (other than Hive and HCatalog, which are done
quarterly)

Set up user permissions
(ACLs, directory permissions, users, home
directories)