cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1489) Expose progress made on PendingStreams through JMX
Date Fri, 10 Sep 2010 21:56:33 GMT


Nick Bailey commented on CASSANDRA-1489:

The current patch doesn't break up the sending and receiving any so the progress will jump
randomly.  We could set a limit on the number of bytes we try to read or write at a time but
I'm not sure if there is much overhead with each call.

> Expose progress made on PendingStreams through JMX
> --------------------------------------------------
>                 Key: CASSANDRA-1489
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>    Affects Versions: 0.7.0
>            Reporter: paul cannon
>            Priority: Minor
>             Fix For: 0.7.0
>         Attachments: 0001-Progress-added-to-incoming-streams.patch, 0002-Progess-added-to-outgoing-streams.patch,
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> So I thought originally that the pairs of numbers shown after filenames returned from
org.apache.cassandra.service:type=StreamingService's getOutgoingFiles/getIncomingFiles calls
were (octetsSent, totalSizeInOctets).  Now I know that they are ranges, and that there can
be several of them with one file, and that makes sense, but there doesn't seem to be any way
to query the progress made on a PendingFile stream.
> We would very much like to be able to inspect that from the outside, in whatever way
makes sense.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message