You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bahir.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/04 17:32:00 UTC
[jira] [Commented] (BAHIR-180) kudu connector improve real-time
data performance
[ https://issues.apache.org/jira/browse/BAHIR-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783584#comment-16783584 ]
ASF GitHub Bot commented on BAHIR-180:
--------------------------------------
eskabetxe commented on issue #40: [BAHIR-180] changes to improve eventual consistence
URL: https://github.com/apache/bahir-flink/pull/40#issuecomment-469342224
@lresende could you check this
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> kudu connector improve real-time data performance
> -------------------------------------------------
>
> Key: BAHIR-180
> URL: https://issues.apache.org/jira/browse/BAHIR-180
> Project: Bahir
> Issue Type: Improvement
> Components: Flink Streaming Connectors
> Affects Versions: Flink-Next
> Reporter: mei jie
> Assignee: Joao Boto
> Priority: Major
> Fix For: Flink-Next
>
>
> kudu connector has poof performance to write real-time data with either strong consistency or eventual consistency. at my environment(3server with 250G memory, 5 disk, and the parallelism of flink is 60), the speed is about 20,000/s.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)