• Share
  • Email
  • Embed
  • Like
  • Private Content
Cisco Hadoop Summit 2013
 

Cisco Hadoop Summit 2013

on

  • 6,702 views

Cisco's presentations at Hadoop Summit 2013.

Cisco's presentations at Hadoop Summit 2013.

Statistics

Views

Total Views
6,702
Views on SlideShare
1,154
Embed Views
5,548

Actions

Likes
0
Downloads
40
Comments
0

5 Embeds 5,548

http://blogs.cisco.com 3642
http://gblogs.cisco.com 1900
http://translate.googleusercontent.com 3
http://webcache.googleusercontent.com 2
https://www.google.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Generally 1G is being used largely due to the cost/performance trade-offs. Though 10GE can provide benefits depending on workloadReduced spike with 10G and smoother job completion timeMultiple 1G or 10G links can be bonded together to not only increase bandwidth, but increase resiliency.
  • Talk about intensity of failure with smaller job vs bigger jobThe MAP job are executed parallel so unit time for each MAP tasks/node remains same and more less completes the job roughly at the same time. However during the failure, set of MAP task remains pending (since other nodes in the cluster are still completing their task) till ALL the node finishes the assigned tasks.Once all the node finishes their MAP task, the left over MAP task being reassigned by name node, the unit time it take to finish those sets of MAP task remain the same(linear) as the time it took to finish the other MAPs – its just happened to be NOT done in parallel thus it could double job completion time. This is the worst case scenario with Terasort, other workload may have variable completion time.