Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 27 Mar 2015 13:52:53 +0000 (UTC)
From: "Robert Stupp (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12735584.1408574546000.49928.1427464373545@Atlassian.JIRA>
In-Reply-To: <JIRA.12735584.1408574546000@Atlassian.JIRA>
References: <JIRA.12735584.1408574546000@Atlassian.JIRA>
 <JIRA.12735584.1408574546671@arcas>
Subject: [jira] [Updated] (CASSANDRA-7807) Push notification when tracing
 completes for an operation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-7807?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Stupp updated CASSANDRA-7807:
------------------------------------
    Attachment: 7807-v3.txt

I worked in all of your comments.

{{SimpleClient}}:
Regarding {{TransportException}} - unfortunately it=E2=80=99s an interface =
- not an (unchecked) exception class.

{{Event}}:
I decided to check the version at the top-level methods (so removed the add=
itional, paranoid checks in the individual implementations)

{{TraceState}}:
Added functionality to {{Connection}}/{{ServerConnection}} that checks for =
registration.

{{TraceCompleteTest}}:
removed that unnecessary stuff (so it doesn=E2=80=99t waste time)

{{MessagePayloadTest}}:
Apologies for that.


> Push notification when tracing completes for an operation
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-7807
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7807
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Robert Stupp
>            Priority: Minor
>              Labels: client-impacting, protocolv4
>             Fix For: 3.0
>
>         Attachments: 7807-v2.txt, 7807-v3.txt, 7807.txt
>
>
> Tracing is an asynchronous operation, and drivers currently poll to deter=
mine when the trace is complete (in a loop with sleeps).  Instead, the serv=
er could push a notification to the driver when the trace completes.
> I'm guessing that most of the work for this will be around pushing notifi=
cations to a single connection instead of all connections that have registe=
red listeners for a particular event type.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)