Skip to content

Conversation

jerryshao
Copy link
Contributor

Currently streaming block will be replicated when specific storage level is set, since WAL is already fault tolerant, so replication is needless and will hurt the throughput of streaming application.

Hi @tdas , as per discussed about this issue, I fixed with this implementation, I'm not is this the way you want, would you mind taking a look at it? Thanks a lot.

@jerryshao jerryshao changed the title 'Do not replicate streaming block when WAL is enabled [SPARK-4671][Streaming]Do not replicate streaming block when WAL is enabled Dec 1, 2014
@SparkQA
Copy link

SparkQA commented Dec 1, 2014

Test build #23981 has started for PR 3534 at commit 500b456.

  • This patch merges cleanly.

@SparkQA
Copy link

SparkQA commented Dec 1, 2014

Test build #23981 has finished for PR 3534 at commit 500b456.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@AmplabJenkins
Copy link

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/23981/
Test PASSed.

@tdas
Copy link
Contributor

tdas commented Dec 23, 2014

LGTM. Merging this.

@asfgit asfgit closed this in 3f5f4cc Dec 23, 2014
asfgit pushed a commit that referenced this pull request Dec 23, 2014
…nabled

Currently streaming block will be replicated when specific storage level is set, since WAL is already fault tolerant, so replication is needless and will hurt the throughput of streaming application.

Hi tdas , as per discussed about this issue, I fixed with this implementation, I'm not is this the way you want, would you mind taking a look at it? Thanks a lot.

Author: jerryshao <[email protected]>

Closes #3534 from jerryshao/SPARK-4671 and squashes the following commits:

500b456 [jerryshao] Do not replicate streaming block when WAL is enabled

(cherry picked from commit 3f5f4cc)
Signed-off-by: Tathagata Das <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants