Of course, i just thinking about huge persistent installation and guys who not
carefully reads Release Notes )
In case of long tx timeouts by design, they can easily fix default timeout with
just one jmx call.
>Zhenya,
>
>Can you please elaborate?
>Why we need to change default TX timeout
Zhenya,
Can you please elaborate?
Why we need to change default TX timeout via JMX? It looks feasible and
perhaps may work as a hotfix for live deployments experiencing issues with
long transactions, but it's definitely a separate issue.
On Fri, May 22, 2020 at 6:20 PM Zhenya Stanilovsky
wrote:
Ivan, does global timeout change through jmx in scope of this ticket ? If so,
can you add it ? Opposite we need additional ticket, i hope ? We still have no
somehow store for jmx changed params, every one need to remember that cluster
restart will reset this setting to default, in this case
https://issues.apache.org/jira/browse/IGNITE-13064 is raised with label
"newbie".
On Tue, May 19, 2020 at 4:10 PM Ivan Rakov wrote:
> Support this idea in general but why 5 minutes and not less?
>
> This value looks to me greater than any value that can possibly affect
> existing deployments
>
> Support this idea in general but why 5 minutes and not less?
This value looks to me greater than any value that can possibly affect
existing deployments (existing long transactions may suddenly start to
rollback), but less than reaction time of users that are only starting to
get along with
+1
On Mon, May 18, 2020 at 9:45 PM Sergey Antonov
wrote:
> +1
>
> пн, 18 мая 2020 г. в 21:26, Andrey Mashenkov :
>
> > +1
> >
> > On Mon, May 18, 2020 at 9:19 PM Ivan Rakov
> wrote:
> >
> > > Hi Igniters,
> > >
> > > I have a very simple proposal. Let's set default TX timeout to 5
> minutes
>
+1
пн, 18 мая 2020 г. в 21:26, Andrey Mashenkov :
> +1
>
> On Mon, May 18, 2020 at 9:19 PM Ivan Rakov wrote:
>
> > Hi Igniters,
> >
> > I have a very simple proposal. Let's set default TX timeout to 5 minutes
> > (right now it's 0 = no timeout).
> > Pros:
> > 1. Deadlock detection procedure is
+1
On Mon, May 18, 2020 at 9:19 PM Ivan Rakov wrote:
> Hi Igniters,
>
> I have a very simple proposal. Let's set default TX timeout to 5 minutes
> (right now it's 0 = no timeout).
> Pros:
> 1. Deadlock detection procedure is triggered on timeout. In case user will
> get into key-level deadlock,
+1 here.
Hi Igniters,
I have a very simple proposal. Let's set default TX timeout to 5 minutes
(right now it's 0 = no timeout).
Pros:
1. Deadlock detection procedure is triggered on timeout. In case user
will
get into key-level deadlock, he'll be able to discover root cause from
the
logs
Hi Ivan,
Support this idea in general but why 5 minutes and not less?
-
Denis
On Mon, May 18, 2020 at 11:19 AM Ivan Rakov wrote:
> Hi Igniters,
>
> I have a very simple proposal. Let's set default TX timeout to 5 minutes
> (right now it's 0 = no timeout).
> Pros:
> 1. Deadlock detection
Hi Igniters,
I have a very simple proposal. Let's set default TX timeout to 5 minutes
(right now it's 0 = no timeout).
Pros:
1. Deadlock detection procedure is triggered on timeout. In case user will
get into key-level deadlock, he'll be able to discover root cause from the
logs (even though load
11 matches
Mail list logo
