beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (BEAM-4049) Improve write throughput of CassandraIO
Date Mon, 16 Apr 2018 13:08:00 GMT

     [ https://issues.apache.org/jira/browse/BEAM-4049?focusedWorklogId=91330&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-91330
]

ASF GitHub Bot logged work on BEAM-4049:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Apr/18 13:07
            Start Date: 16/Apr/18 13:07
    Worklog Time Spent: 10m 
      Work Description: aromanenko-dev commented on issue #5112: [BEAM-4049] Improve CassandraIO
write throughput by performing async queries
URL: https://github.com/apache/beam/pull/5112#issuecomment-381592793
 
 
   @adejanovski Yes, I think it's not related to your changes.

----------------------------------------------------------------
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: 91330)
    Time Spent: 3h 10m  (was: 3h)

> 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: Jean-Baptiste Onofré
>            Priority: Major
>              Labels: performance
>          Time Spent: 3h 10m
>  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)

Mime
View raw message