Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Branch 0.6 #19935

Closed
wants to merge 97 commits into from
Closed

Branch 0.6 #19935

wants to merge 97 commits into from

Conversation

crazed7
Copy link

@crazed7 crazed7 commented Dec 9, 2017

What changes were proposed in this pull request?

(Please fill in changes proposed in this fix)

How was this patch tested?

(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Please review http://spark.apache.org/contributing.html before opening a pull request.

mateiz and others added 30 commits October 24, 2012 21:52
…he master due to

a locally computed operation
- Don't report a job as finishing multiple times
- Don't show state of workers as LOADING when they're running
- Show start and finish times in web UI
- Sort web UI tables by ID and time by default
fix bug in getting slave id out of mesos
1. Changed the lock structure of BlockManager by replacing the 337 coarse-grained locks to use BlockInfo objects as per-block fine-grained locks.
2. Changed the MemoryStore lock structure by making the block putting threads lock on a different object (not the memory store) thus making sure putting threads minimally blocks to the getting treads.
3. Added spark.storage.ThreadingTest to stress test the BlockManager using 5 block producer and 5 block consumer threads.
…reads each doing 50k puts (gets), took 15 minutes to run, no errors or deadlocks.
matching with data locality hints from storage systems.
charlesreiss and others added 27 commits February 4, 2013 12:07
Conflicts:
	core/src/main/scala/spark/scheduler/DAGScheduler.scala
This prevents ConnectionManager from getting confused if a machine
has multiple host names and the one getHostName() finds happens
not to be the one that was passed from, e.g., the BlockManagerMaster.
Also fixes some issues in the rest of the code with detecting workers this way.
Fixes link to issue tracker in documentation page "Contributing to Spark"
@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Dec 9, 2017

@khanm002 close this

@crazed7 crazed7 closed this Dec 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet