Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Date: Fri, 26 Feb 2016 13:27:44 -0700 (MST)
From: z11373 <z11373@outlook.com>
To: dev@accumulo.apache.org
Message-ID: <1456518464070-16230.post@n5.nabble.com>
In-Reply-To: <1456516418258-16219.post@n5.nabble.com>
References: <1456502319439-16202.post@n5.nabble.com>
 <56D083A1.3030608@gmail.com>
 <CAGUtCHr8Z3V9kB1gV2zHV8u4nM7R92bqzLRCdqYfdbprAEE_Bw@mail.gmail.com>
 <1456516418258-16219.post@n5.nabble.com>
Subject: Re: cached connector
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I want to add another point from the observation I just did.
The code in my service will cache the connector based on specific id (let
call it firm id in this case), so what I just did was to send another
request with different firm id to that specific service instance. I can see
from my application log, it creates new connector (and then cache it).
Then I keep sending request with that second firm id, and got expected
processing time.
Then I tried sending request with the first firm id (the one which is
already cached and in 'bad' state), and it consistently taking long time and
returns after 8s.

This test result kind of telling me that the connection for that particular
connector is likely already busted (somehow), but it works fine on new
connector.


Thanks,
Z


--
View this message in context: http://apache-accumulo.1065345.n5.nabble.com/cached-connector-tp16202p16230.html
Sent from the Developers mailing list archive at Nabble.com.