diff options
| author | Davies Liu <davies@databricks.com> | 2016-05-19 11:47:17 -0700 |
|---|---|---|
| committer | Andrew Or <andrew@databricks.com> | 2016-05-19 11:47:17 -0700 |
| commit | ad182086cc3bd7951aaf82693d9bcb56815b43e4 (patch) | |
| tree | 14e801ca91c5b50ee1a36136dfe66c2d87a7d55c /python | |
| parent | ef7a5e0bcaee45b907a10b73f11c838ef6e23614 (diff) | |
| download | spark-ad182086cc3bd7951aaf82693d9bcb56815b43e4.tar.gz spark-ad182086cc3bd7951aaf82693d9bcb56815b43e4.tar.bz2 spark-ad182086cc3bd7951aaf82693d9bcb56815b43e4.zip | |
[SPARK-15300] Fix writer lock conflict when remove a block
## What changes were proposed in this pull request?
A writer lock could be acquired when 1) create a new block 2) remove a block 3) evict a block to disk. 1) and 3) could happen in the same time within the same task, all of them could happen in the same time outside a task. It's OK that when someone try to grab the write block for a block, but the block is acquired by another one that has the same task attempt id.
This PR remove the check.
## How was this patch tested?
Updated existing tests.
Author: Davies Liu <davies@databricks.com>
Closes #13082 from davies/write_lock_conflict.
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions