[jira] [Updated] (IGNITE-11029) Public API for edge-chasing deadlock detection configuration
[ https://issues.apache.org/jira/browse/IGNITE-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-11029: - Ignite Flags: Docs Required,Release Notes Required (was: Docs Required) > Public API for edge-chasing deadlock detection configuration > > > Key: IGNITE-11029 > URL: https://issues.apache.org/jira/browse/IGNITE-11029 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > As deadlock detection introduce overhead during transaction processing some > configuration means should be introduced. Following aspects should be > addressed: > 1. Turning detection on/off. > 2. Adjusting a timeout before starting actual detection. > It is proposed to introduce single property in {{TransactionConfiguration}} > to address both concerns. > Also it is desired that configuration is consistent across all cluster nodes > (detection turned off on even one node can lead to undetected deadlocks). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11029) Public API for edge-chasing deadlock detection configuration
[ https://issues.apache.org/jira/browse/IGNITE-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin updated IGNITE-11029: Description: As deadlock detection introduce overhead during transaction processing some configuration means should be introduced. Following aspects should be addressed: 1. Turning detection on/off. 2. Adjusting a timeout before starting actual detection. It is proposed to introduce single property in {{TransactionConfiguration}} to address both concerns. Also it is desired that configuration is consistent across all cluster nodes (detection turned off on even one node can lead to undetected deadlocks). was: As deadlock detection introduce overhead during transaction processing some configuration means should be introduced. Following aspects should be addressed: 1. Turning detection on/off. 2. Adjusting a timeout before starting actual detection. It is proposed to introduce single property in {{TransactionConfiguration}} to address both concerns. Also configuration should achieve following goals: 1. Be the same for every node in cluster. 2. Be configurable in run time. > Public API for edge-chasing deadlock detection configuration > > > Key: IGNITE-11029 > URL: https://issues.apache.org/jira/browse/IGNITE-11029 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.8 > > > As deadlock detection introduce overhead during transaction processing some > configuration means should be introduced. Following aspects should be > addressed: > 1. Turning detection on/off. > 2. Adjusting a timeout before starting actual detection. > It is proposed to introduce single property in {{TransactionConfiguration}} > to address both concerns. > Also it is desired that configuration is consistent across all cluster nodes > (detection turned off on even one node can lead to undetected deadlocks). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11029) Public API for edge-chasing deadlock detection configuration
[ https://issues.apache.org/jira/browse/IGNITE-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin updated IGNITE-11029: Description: As deadlock detection introduce overhead during transaction processing some configuration means should be introduced. Following aspects should be addressed: 1. Turning detection on/off. 2. Adjusting a timeout before starting actual detection. It is proposed to introduce single property in {{TransactionConfiguration}} to address both concerns. Also configuration should achieve following goals: 1. Be the same for every node in cluster. 2. Be configurable in run time. was: As deadlock detection introduce overhead during transaction processing some configuration means should be introduced. Following aspects should be addressed: 1. Turning detection on/off. 2. Adjusting a timeout before starting actual detection. It is proposed to introduce single property in {{TransactionConfiguration}} to address both items. > Public API for edge-chasing deadlock detection configuration > > > Key: IGNITE-11029 > URL: https://issues.apache.org/jira/browse/IGNITE-11029 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Major > Fix For: 2.8 > > > As deadlock detection introduce overhead during transaction processing some > configuration means should be introduced. Following aspects should be > addressed: > 1. Turning detection on/off. > 2. Adjusting a timeout before starting actual detection. > It is proposed to introduce single property in {{TransactionConfiguration}} > to address both concerns. > Also configuration should achieve following goals: > 1. Be the same for every node in cluster. > 2. Be configurable in run time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)