You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/04 14:49:00 UTC
[jira] [Work logged] (BEAM-4049) Improve write throughput of
CassandraIO
[ https://issues.apache.org/jira/browse/BEAM-4049?focusedWorklogId=151204&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-151204 ]
ASF GitHub Bot logged work on BEAM-4049:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Oct/18 14:48
Start Date: 04/Oct/18 14:48
Worklog Time Spent: 10m
Work Description: echauchot commented on issue #5112: [BEAM-4049] Improve CassandraIO write throughput by performing async queries
URL: https://github.com/apache/beam/pull/5112#issuecomment-427047728
@script3r version mismatch in the cassandra client library (version in classpath is not the same as the one defined in Beam cassandra IO) ? Maybe you provided the library inside your app jar.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
Issue Time Tracking
-------------------
Worklog Id: (was: 151204)
Time Spent: 6h 50m (was: 6h 40m)
> Improve write throughput of CassandraIO
> ---------------------------------------
>
> Key: BEAM-4049
> URL: https://issues.apache.org/jira/browse/BEAM-4049
> Project: Beam
> Issue Type: Improvement
> Components: io-java-cassandra
> Affects Versions: 2.4.0
> Reporter: Alexander Dejanovski
> Assignee: Alexander Dejanovski
> Priority: Major
> Labels: performance
> Fix For: 2.5.0
>
> Time Spent: 6h 50m
> Remaining Estimate: 0h
>
> The CassandraIO currently uses the mapper to perform writes in a synchronous fashion.
> This implies that writes are serialized and is a very suboptimal way of writing to Cassandra.
> The IO should use the saveAsync() method instead of save() and should wait for completion each time 100 queries are in flight, in order to avoid overwhelming clusters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)