Abstract
MapReduce is a popular big data processing tool, but there exists a main node failure problem. In order to make the restarted JobTracker recover jobs site quickly, there are mainly two recovery mechanisms: synchronization mechanism and backup mechanism. In synchronization mechanism, TaskTracker sends synchronous message to JobTracker within required time in order to recover jobs without considering dependency between Map and Reduce tasks, which leads to congestion. Using backup mechanism, JobTracker recovers jobs based on backup records ignoring assigned tasks between backup intervals (which is called zombie tasks). That will result in repeated task assignment. We come up with a new backup mechanism based on transferring dependency, with the addition of dependency list mechanism and zombie task recovery mechanism. The new mechanism effectively solves problems of congestion and duplicated distribution of zombie tasks, making the jobs continue running from the breakpoint.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
