Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0A682191B8 for ; Wed, 23 Mar 2016 15:19:02 +0000 (UTC) Received: (qmail 93558 invoked by uid 500); 23 Mar 2016 15:19:00 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 93513 invoked by uid 500); 23 Mar 2016 15:18:59 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 93503 invoked by uid 99); 23 Mar 2016 15:18:59 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Mar 2016 15:18:59 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7B92A180218 for ; Wed, 23 Mar 2016 15:18:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id UhHvA7AUygTI for ; Wed, 23 Mar 2016 15:18:57 +0000 (UTC) Received: from mail-vk0-f54.google.com (mail-vk0-f54.google.com [209.85.213.54]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 71FB45F33E for ; Wed, 23 Mar 2016 15:18:57 +0000 (UTC) Received: by mail-vk0-f54.google.com with SMTP id e185so23518746vkb.1 for ; Wed, 23 Mar 2016 08:18:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=B2b3VwYxPTQNUaob+A+GGbfIp/mVQ+qaTnnR31q5zIg=; b=MnHYSyhK8dc2reAsXukVXFxQcVKr116sJyyoYyQxvFnLWHxwNg/fI2bf0ZW5/GYfAe AWbk3mwB5OxGF9ktrgbWH52ihMRHPwvz/pMobAEB4oYwsEd+XPrLxID57gLjIKeye7G8 06YeBQUxmDkT2/02pjIrsJke4Sl3BUI+VSSvVw4bXFqBTrmAqO4UfkFozcTFwklP41a0 cB+w+2Rl+DSVdz6uKa8JEsWxUk16K0hEjmKXz1rLT+dfkGA+NBj15O5hGV0hooO0s3D0 qgFcNbR74+cEW7k1NYoUQLZu++VdsogoS4fPFOUXB676hQiNM843cVWqWE/A++/UJROY zB+w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=B2b3VwYxPTQNUaob+A+GGbfIp/mVQ+qaTnnR31q5zIg=; b=ll82uY7G7MXX8BA1uJw2SqcqfTy2XF7l9ChZHa5xc8rSvw2eAx0K9n0Swfg4+9vSG2 xpmFjxccvMAlhjWYXm+alycVwsaoJnaHHebKsY+U1zgPgpxYd01zQ5+ifoxpCRfLyaKh k0c7HyQdRN5GNhx32IgAaYwFOX6VFO5oFu6ghowhjPNfmHFP0BOTiW789RP5qiITtRXA VEQG/MH7dNuv/H2VaR3cmT1B/kckERfIv2s6yg+Gf8RltaQNKc68EBKoE7ZvBf1mEM98 WUECstQg3TA3ndn9Kpz6csr5wcqsOYfRgFAEF/jWN4anTC1PaSgvSkjEhoT+2i9PP3Qg tpfw== X-Gm-Message-State: AD7BkJJXt5uWV6kJmIhPSL5zX0h/AdXGNLwVzAp0Wfv476Bum7wo0nSslhENDoMThw+C3AZthVW6+z+Sc7mfRQ== MIME-Version: 1.0 X-Received: by 10.31.140.130 with SMTP id o124mr1853810vkd.145.1458746331545; Wed, 23 Mar 2016 08:18:51 -0700 (PDT) Received: by 10.31.54.13 with HTTP; Wed, 23 Mar 2016 08:18:51 -0700 (PDT) In-Reply-To: References: Date: Wed, 23 Mar 2016 11:18:51 -0400 Message-ID: Subject: Re: com.datastax.driver.core.Connection "This should not happen and is likely a bug, please report." From: Jack Krupansky To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11425f30e8c616052eb8d84e --001a11425f30e8c616052eb8d84e Content-Type: text/plain; charset=UTF-8 It would be nice for that message (and there is one more like it in the driver) to say something more specific about how/where exactly to "report" the situation. I mean, should users file Jira tickets for those two scenarios or simply email to the Java (or other driver) email lists? The message should be specific as to desired process for filing a bug. For example, the Python driver CONTRIBUTING.rst recommends filing a JIRA ticket, but generally on this list and most projects people are encouraged to open a discussion on the user list before concluding than an apparent issue is actually a real issue necessitating a ticket. But in the case of these two explicit cases where the driver itself is directing the user to report, it becomes unclear whether a simple inquiry/report on the driver mailing list is sufficient or whether a full Jira is warranted. Granted, starting on the mailing list is always a good idea, but as we continually see, people have difficulty even discerning the distinction between the Cassandra user list and the driver user lists. In truth, to some (a lot) of us, this distinction between "user" and "driver" is quite baffling. Sorry for the mini-rant! -- Jack Krupansky On Wed, Mar 23, 2016 at 9:57 AM, Thunder Stumpges < thunder.stumpges@gmail.com> wrote: > OK. Thanks. > On Tue, Mar 22, 2016 at 12:56 PM Alex Popescu wrote: > >> Hi Thunder, >> >> This would be better sent to the Java mailing list >> https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user. >> A quick search revealed >> https://datastax-oss.atlassian.net/browse/JAVA-603 which seem to match >> the Cassandra/DataStax community version but not the driver version. >> >> On Mon, Mar 21, 2016 at 9:33 PM, Thunder Stumpges < >> thunder.stumpges@gmail.com> wrote: >> >>> Hi guys, >>> >>> So, quick background, we are using Outworkers (previously WebSudos) >>> Phantom v 1.22.0 Which appears to be using DataStax driver 3.0.0. We are >>> running scala 2.10 inside Samza on Yarn (CDH 5.4.4) with Oracle JDK 8. >>> >>> This is all pointing at a 3 node dev cluster of DataStax Community v >>> 2.1.13 >>> >>> After running for a short time, the following error is thrown by the >>> Datastax driver in the Samza container: >>> >>> Logger: com.datastax.driver.core.Connection >>> Message: >>> "Forcing termination of Connection[/:9042-3, >>> inFlight=0, closed=true]. This should not happen and is likely a bug, >>> please report." >>> >>> There aren't really any other logs around this time, so not sure what >>> else I can provide. It said to "please report" so I guess I am. If what I >>> have provided is enough information to actually file a bug report, please >>> let me know and I will. Otherwise, what additional information can I >>> collect for this? >>> >>> Thanks, >>> Thunder >>> >>> >> >> >> -- >> Bests, >> >> Alex Popescu | @al3xandru >> Sen. Product Manager @ DataStax >> >> --001a11425f30e8c616052eb8d84e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It would be nice for that message (and there is one more l= ike it in the driver) to say something more specific about how/where exactl= y to "report" the situation. I mean, should users file Jira ticke= ts for those two scenarios or simply email to the Java (or other driver) em= ail lists? The message should be specific as to desired process for filing = a bug. For example, the Python driver CONTRIBUTING.rst recommends filing a = JIRA ticket, but generally on this list and most projects people are encour= aged to open a discussion on the user list before concluding than an appare= nt issue is actually a real issue necessitating a ticket. But in the case o= f these two explicit cases where the driver itself is directing the user to= report, it becomes unclear whether a simple inquiry/report on the driver m= ailing list is sufficient or whether a full Jira is warranted. Granted, sta= rting on the mailing list is always a good idea, but as we continually see,= people have difficulty even discerning the distinction between the Cassand= ra user list and the driver user lists. In truth, to some (a lot) of us, th= is distinction between "user" and "driver" is quite baf= fling. Sorry for the mini-rant!

-- Jack Krupa= nsky

On Wed, Mar 23, 2016 at 9:57 AM, Thunder Stu= mpges <thunder.stumpges@gmail.com> wrote:
OK. Thanks.
On Tue, Mar 22, 2016 at= 12:56 PM Alex Popescu <alexp@datastax.com> wrote:
Hi Thunder,

This would be better= sent to the Java mailing list=C2=A0https:= //groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user= . A quick search revealed=C2=A0https://datastax-oss.atlassian.net/bro= wse/JAVA-603 which seem to match the Cassandra/DataStax community versi= on but not the driver version.
=

On Mon, Mar 21, 2= 016 at 9:33 PM, Thunder Stumpges <thunder.stumpges@gmail.com&= gt; wrote:
Hi guy= s,

So, quick background, we are using Outworkers (previo= usly WebSudos) Phantom v 1.22.0 Which appears to be using DataStax driver 3= .0.0. We are running scala 2.10 inside Samza on Yarn (CDH 5.4.4) with Oracl= e JDK 8.=C2=A0

This is all pointing at a 3 node de= v cluster of DataStax Community v 2.1.13

After run= ning for a short time, the following error is thrown by the Datastax driver= in the Samza container:

Logger:=C2=A0com.datastax.driver.c= ore.Connection
Message:
"Forcing termi= nation of Connection[<cass-host>/<ip.add.re.ss>:9042-3, inFligh= t=3D0, closed=3Dtrue]. This should not happen and is likely a bug, please r= eport."

There aren't really any= other logs around this time, so not sure what else I can provide. It said = to "please report" so I guess I am. If what I have provided is en= ough information to actually file a bug report, please let me know and I wi= ll. Otherwise, what additional information can I collect for this?

Thanks,
Thunder
=



--
Bests,

Alex Popescu |=C2=A0@al3xandr= u
Sen. Product Manager @ DataStax


--001a11425f30e8c616052eb8d84e--