1. Configuration
7/6/2012
© 2012 MapR Technologies Configuration 1

2. Configuration
Agenda
• Setting up the Node Topology
• Setting up Volumes
• Central Configuration
• Setting up Multiple NICs
• Setting up VIPs for NFS
• Managing Users
• LAB: Configuration
© 2012 MapR Technologies Configuration 2

3. Configuration
Objectives
At the end of this module you will be able to:
• Configure node and volume topology
• Explain how Central Configuration manages the centralized repository of
MapR configuration files
• Set up or restrict NICs for use with MapR
• Configure VIPs for NFS HA
• Manage permissions for users and groups on the cluster as well as on
volumes and the MapR-FS
• Set quotas for volumes, users, and groups
© 2012 MapR Technologies Configuration 3

4. Setting up the Node
Topology
© 2012 MapR Technologies Configuration 4

5. Node Topology
 Topology indicates locations of nodes and racks
– Determines where MapR places replicated data
– Replication scattered across racks
• Data still available if a rack fails
Offline Active
– Specify a topology for each node row22
• Group nodes by rack/switch depending on
– How physical cluster is arranged
– How you want to place replicated data
Rack5 Rack 6
© 2012 MapR Technologies Configuration 5

6. Node Topology
© 2012 MapR Technologies Configuration 6

7. Setting up Volumes
© 2012 MapR Technologies Configuration 7

8. Setting up Volumes
 Volume:
– A logical unit of storage that allows you to apply policies to
• Files
• Directories
• Sub-volumes
 Use volumes to
/ /projects /users
– Enforce disk usage limits
– Set replication levels
– Establish ownership and accountability
– Measure costs
 Create a separate volume for each user/department/project
 Mount volumes under other volumes as needed
© 2012 MapR Technologies Configuration 8

9. Typical Volume Layout
/
/binaries /hbase /projects /users /var/mapr
/build /test /mjones /jsmith local...
Recommendation: set up a volume per user
© 2012 MapR Technologies Configuration 9

10. Volume Topology
 Place a volume on specific racks or node(s)
– Set volume topology to node/nodes/rack
 Note:
– By default, new volumes are created with a topology of /
– Change the default topology, with the config save command
• Set the cldb.default.volume.topology parameter
• For example:
maprcli config save -values
"{"cldb.default.volume.topology":"/default-rack"}”
• After running the above command, new volumes have the default topology is
/default-rack
© 2012 MapR Technologies Configuration 10

11. Volume Topology
© 2012 MapR Technologies Configuration 11

12. Central Configuration
© 2012 MapR Technologies Configuration 12

13. Central Configuration
 Central location for all MapR config files
– No need to SSH to individual nodes
• Uses MapR-FS
– Built-in replication
– Use snapshots for versioning
– Details
• maprfs:///var/mapr/configuration
• Config options in warden.conf
– centralconfig.enabled=true
– pollcentralconfig.interval.seconds=300
© 2012 MapR Technologies Configuration 13

14. Central Configuration
 How does it work?
– Warden copies files from
maprfs:///var/mapr/configuration
to local node /opt/mapr/…
 Examples
From: maprfs:///var/mapr/configuration/default/hadoop/hadoop-0.20.2/conf
To: /opt/mapr/hadoop/hadoop-0.20.2/conf
From: maprfs:///var/mapr/configuration/nodes/hostname/hadoop/hadoop-0.20.2/conf
To: /opt/mapr/hadoop/hadoop-0.20.2/conf
© 2012 MapR Technologies Configuration 14

15. Setting up Multiple NICs
© 2012 MapR Technologies Configuration 15

16. Configuring NICs with MapR
 Configure which NICs are used for MapR traffic
– Faster NICs for high-bandwidth data transfer
– Slower NIC for ssh, etc.
 Set MAPR_SUBNETS
– Comma-separated list of up to four subnets
– CIDR notation with no spaces
– For example
export MAPR_SUBNETS=1.2.3.4/12,1.2.5.6/24
– If MAPR_SUBNETS is not set, MapR uses all NICs present on the node
© 2012 MapR Technologies Configuration 16

17. Setting up VIPs for NFS
© 2012 MapR Technologies Configuration 17

18. VIPs for NFS HA
 Use Virtual IP addresses (VIPs) to achieve HA with NFS
– If one node fails VIP moves to next node in pool
– Recommendation: NFS nodes >= 3
– First set up one or more VIP(s)
• Node are added to the pool by starting NFS service
– If all NICs are on the same subnet
• Manually add IP/MAC to pool
– Use maprcli virtualip add or MCS
– If not all NICs on NFS nodes in same subnet
– OR if you wish to restrict VIPs assignments to specific NICs or MAC addresses
© 2012 MapR Technologies Configuration 18

19. VIPs for NFS HA
© 2012 MapR Technologies Configuration 19

20. Managing Users
© 2012 MapR Technologies Configuration 20

21. Managing Users
 MapR uses OS/PAM to authenticate users
– Assign a specific user (e.g. “mapr”) to administer the cluster
– UIDs and GIDs should match on all nodes
– Assign permissions to users/groups via MCS or use acl edit or acl
set
• Cluster (ACL)
• Volume (ACL)
• MapR-FS (POSIX-like)
– Assign quotas on volumes
• Limit space used by a volume
• limit space used on all volumes by a user/group
© 2012 MapR Technologies Configuration 21

22. Cluster Permissions
Code Allowed Action Includes
login Log in to the MapR Control cv
System, use the API and
command-line interface,
read access on cluster and
volumes
ss Start/stop services
cv Create volumes
a Admin access All permissions except fc
fc Full control (administrative a
access and permission to
change the cluster ACL)
© 2012 MapR Technologies Configuration 22

23. Volume Permissions
Code Allowed Action
dump Dump the volume
restore Mirror or restore the volume
m Modify volume properties, create and
delete snapshots
d Delete a volume
fc Full control (admin access and
permission to change volume ACL)
© 2012 MapR Technologies Configuration 23

24. LAB:
Configuration
© 2012 MapR Technologies Configuration 24

25. Questions
© 2012 MapR Technologies Configuration 25