3 Steps to Better Hadoop Management
It makes sense to get excited about the possibilities afforded by Apache™ Hadoop® YARN-based applications such as Spark, Storm, Presto and others to provide substantial business value. However, the actual tasks of managing and maintaining the environment should not get short shrift. Without considering best practices to ensure big data system performance and stability, business users will slowly lose faith and trust in Hadoop as a difference maker for the enterprise.
With a goal of increasing big data application adoption, the Hadoop environment must run optimally to meet end-user expectations. Think Big, a Teradata company, runs Hadoop platforms for numerous global customers and has identified three best practices that can help you improve operations.
- LEVERAGE WORKLOAD MANAGEMENT CAPABILITIES
Workload management is important in a Hadoop environment. Why? Because as your big data systems are more widely used for production, the needs of business teams will invariably drive competition among different components for system resources.
Even though your Hadoop cluster can be deployed with guidelines provided by the distribution provider, it should be configured for your own specific workloads. Administrators can use YARN’s workload management capabilities to decide which users get what systems resources and when to meet service levels.
When workload management settings are properly identified and adjusted, administrators can schedule jobs to gain maximum utilization of cluster resources. This not only keeps the Hadoop cluster’s footprint to an appropriate size, it also increases the adaptability to match resources to changing business requirements.
- STRIVE FOR BUSINESS CONTINUITY
As valuable data is staged and housed in Hadoop, continuous system availability and data protection become more essential. However, Hadoop’s data replication capabilities are not enough to protect vital data sets from disaster. A standard three-way replication is sufficient to protect various data objects from corruption or loss, but it is not an adequate backup and disaster recovery strategy.
Hadoop’s replication is designed to enable better fault tolerance and data locality for processing. But having three copies of the data in the same rack will not protect it from the inevitable problems that will arise. That’s why data must be backed up daily to another data center using an enterprise data archive tool or cloud instance. These efforts help protect the information from a natural disaster, cyberattack or other unforeseen incident.
For business continuity, don’t forget about NameNode backup. The NameNode stores a directory tree of files in the Hadoop Distributed File System (HDFS) and records where data is kept in the cluster. It is a single point of failure, and rebuilding the NameNode from scratch is a time-consuming endeavor fraught with the potential for considerable data loss. That’s why as your production system grows, it’s increasingly important to back up not only business data but also the NameNode.
Critical applications relying on Hadoop resources also require a high-availability strategy. This requires a plan that can be quickly enacted to ensure production workloads aren’t troubled by unanticipated circumstances. Be sure to include a process to reconstruct data sets from raw sources and/or readily restorable offline backups of irreplaceable data sets.
- UTILIZE HADOOP EXPERIENCE
While detailed documentation on Hadoop architecture, daily monitoring tasks and issue resolution are essential, there is no substitute for experience. Even if application support processes are documented, challenges will undoubtedly arise, which is where experience comes into play. A specific skill set is needed to administer and develop on big data open-source platforms, far beyond what a typical DBA is trained to perform.
In addition to Hadoop admin experience, your big data application support teams should have a solid technical background that allows for adapting to non-standard issues. A senior technical person who can help resolve particularly thorny challenges should be part of that team. Ideally, he or she will have a detailed knowledge of custom application development in Hadoop, strong Linux skills and the ability to troubleshoot complex problems. Source