[jira] [Assigned] (IGNITE-13064) Set default transaction timeout to 5 minutes

2020-05-25 Thread Nikita Alemaskin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-13064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikita Alemaskin reassigned IGNITE-13064:
-

Assignee: Nikita Alemaskin

> Set default transaction timeout to 5 minutes
> 
>
> Key: IGNITE-13064
> URL: https://issues.apache.org/jira/browse/IGNITE-13064
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Nikita Alemaskin
>Priority: Major
>  Labels: newbie
>
> 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 will hang for a while) and skip step with googling and 
> debugging.
> 2. Almost every system with transactions has timeout enabled by default.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-11494) Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter

2020-04-10 Thread Nikita Alemaskin (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080286#comment-17080286
 ] 

Nikita Alemaskin commented on IGNITE-11494:
---

Hello, [~amashenkov]! 

Could you, please, take a look at my changes.

> Change message log message in case of too small 
> IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
> -
>
> Key: IGNITE-11494
> URL: https://issues.apache.org/jira/browse/IGNITE-11494
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Nikita Alemaskin
>Priority: Major
>  Labels: newbie, usability
> Attachments: 
> master_ee07f34e52_IGNITE-11494-large_set_logging_improving.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Message "Fetched result set was too large." should be changed to some 
> recommendations regarding IGNITE_SQL_MERGE_TABLE_MAX_SIZE property



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Issue Comment Deleted] (IGNITE-11494) Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter

2020-04-10 Thread Nikita Alemaskin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikita Alemaskin updated IGNITE-11494:
--
Comment: was deleted

(was: Hello, [~jooger]!

Could you, please, take a look at my changes.)

> Change message log message in case of too small 
> IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
> -
>
> Key: IGNITE-11494
> URL: https://issues.apache.org/jira/browse/IGNITE-11494
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Nikita Alemaskin
>Priority: Major
>  Labels: newbie, usability
> Attachments: 
> master_ee07f34e52_IGNITE-11494-large_set_logging_improving.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Message "Fetched result set was too large." should be changed to some 
> recommendations regarding IGNITE_SQL_MERGE_TABLE_MAX_SIZE property



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-11494) Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter

2020-04-08 Thread Nikita Alemaskin (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078686#comment-17078686
 ] 

Nikita Alemaskin commented on IGNITE-11494:
---

Hello, [~jooger]!

Could you, please, take a look at my changes.

> Change message log message in case of too small 
> IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
> -
>
> Key: IGNITE-11494
> URL: https://issues.apache.org/jira/browse/IGNITE-11494
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Nikita Alemaskin
>Priority: Major
>  Labels: newbie, usability
> Attachments: 
> master_ee07f34e52_IGNITE-11494-large_set_logging_improving.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Message "Fetched result set was too large." should be changed to some 
> recommendations regarding IGNITE_SQL_MERGE_TABLE_MAX_SIZE property



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-11494) Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter

2020-04-08 Thread Nikita Alemaskin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikita Alemaskin updated IGNITE-11494:
--
Attachment: master_ee07f34e52_IGNITE-11494-large_set_logging_improving.patch

> Change message log message in case of too small 
> IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
> -
>
> Key: IGNITE-11494
> URL: https://issues.apache.org/jira/browse/IGNITE-11494
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Nikita Alemaskin
>Priority: Major
>  Labels: newbie, usability
> Attachments: 
> master_ee07f34e52_IGNITE-11494-large_set_logging_improving.patch
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Message "Fetched result set was too large." should be changed to some 
> recommendations regarding IGNITE_SQL_MERGE_TABLE_MAX_SIZE property



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (IGNITE-11494) Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter

2020-04-08 Thread Nikita Alemaskin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikita Alemaskin updated IGNITE-11494:
--
Attachment: (was: 
master_ee07f34e52_IGNITE-11494-large_set_logging_improving.patch)

> Change message log message in case of too small 
> IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
> -
>
> Key: IGNITE-11494
> URL: https://issues.apache.org/jira/browse/IGNITE-11494
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Nikita Alemaskin
>Priority: Major
>  Labels: newbie, usability
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Message "Fetched result set was too large." should be changed to some 
> recommendations regarding IGNITE_SQL_MERGE_TABLE_MAX_SIZE property



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (IGNITE-11494) Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter

2020-04-06 Thread Nikita Alemaskin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-11494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikita Alemaskin reassigned IGNITE-11494:
-

Assignee: Nikita Alemaskin

> Change message log message in case of too small 
> IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
> -
>
> Key: IGNITE-11494
> URL: https://issues.apache.org/jira/browse/IGNITE-11494
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.7
>Reporter: Evgenii Zhuravlev
>Assignee: Nikita Alemaskin
>Priority: Major
>  Labels: newbie, usability
>
> Message "Fetched result set was too large." should be changed to some 
> recommendations regarding IGNITE_SQL_MERGE_TABLE_MAX_SIZE property



--
This message was sent by Atlassian Jira
(v8.3.4#803005)