Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CABuYRcrCQxDuSwJ1EGh7KSy66V+njoR2Zm4zN_Lm4fjU3s8j8g@mail.gmail.com>
References: <CABuYRcrCQxDuSwJ1EGh7KSy66V+njoR2Zm4zN_Lm4fjU3s8j8g@mail.gmail.com>
From: Igor Rudyak <irudyak@gmail.com>
Date: Wed, 12 Apr 2017 08:47:45 -0700
Message-ID: <CAMpMOYFTsT+RbVmmrZ__AWicoYijb-KzkXhY-w-0u-p94TsJvw@mail.gmail.com>
Subject: Re: Session expiration in Cassandra store
To: Valentin Kulichenko <valentin.kulichenko@gmail.com>
Cc: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=f403045da082373d92054cfa21df
archived-at: Wed, 12 Apr 2017 15:48:04 -0000

--f403045da082373d92054cfa21df
Content-Type: text/plain; charset=UTF-8

Hi Val,

1) The genral idea is to have a session pool, cause closing and reopening
Cassandra session each time is rather expensive operation.

2) I can easily add session expiration timeout as a parameter for Cassandra
store. Will create a ticket for this.

3) It could be easily implemented ether, by closing and reopening session
every time or just keeping opened sessions forever, but both approaches are
bad. It's better to have a session pool and specify rather long session
expiration timeout.

Igor


On Apr 12, 2017 2:48 AM, "Valentin Kulichenko" <
valentin.kulichenko@gmail.com> wrote:

Hi Igor,

I recently faced an issue with Cassandra store closing idle connections
after some time. While investigating I found that this is caused by
SessionPool and its SessionMonitor thread which closes sessions that were
not acquired from the pool within 5 minutes.

I have several questions regarding this:

   - What is the general idea behind this?
   - Why the timeout is not configurable?
   - Is it possible to add an option to disable this thread completely?
   Will this have any drawbacks?

-Val

--f403045da082373d92054cfa21df--