[jira] [Updated] (IGNITE-14167) Concurrency issues in reconnect. Invalid update strategy of partition update.
[ https://issues.apache.org/jira/browse/IGNITE-14167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-14167: - Fix Version/s: python-0.4.0 > Concurrency issues in reconnect. Invalid update strategy of partition update. > - > > Key: IGNITE-14167 > URL: https://issues.apache.org/jira/browse/IGNITE-14167 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: python-0.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently the code in Connection class is not properly synchronized and > socket can be set to None while reconnecting and sending requests > simultaneously. > Also, reconnections attempt are to short (8 fibonacci sequence items) and > total only 33 > sec. > These issues lead to flaky tests for affinity suite. > *APPEND* Also, there is invalid update of affinity version (stale version > could be written) This lead to invalid partition update. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14167) Concurrency issues in reconnect. Invalid update strategy of partition update.
[ https://issues.apache.org/jira/browse/IGNITE-14167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy updated IGNITE-14167: -- Description: Currently the code in Connection class is not properly synchronized and socket can be set to None while reconnecting and sending requests simultaneously. Also, reconnections attempt are to short (8 fibonacci sequence items) and total only 33 sec. These issues lead to flaky tests for affinity suite. *APPEND* Also, there is invalid update of affinity version (stale version could be written) This lead to invalid partition update. was: Currently the code in Connection class is not properly synchronized and socket can be set to None while reconnecting and sending requests simultaneously. Also, reconnections attempt are to short (8 fibonacci sequence items) and total only 33 sec. These issues lead to flaky tests for affinity suite. > Concurrency issues in reconnect. Invalid update strategy of partition update. > - > > Key: IGNITE-14167 > URL: https://issues.apache.org/jira/browse/IGNITE-14167 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > > Currently the code in Connection class is not properly synchronized and > socket can be set to None while reconnecting and sending requests > simultaneously. > Also, reconnections attempt are to short (8 fibonacci sequence items) and > total only 33 > sec. > These issues lead to flaky tests for affinity suite. > *APPEND* Also, there is invalid update of affinity version (stale version > could be written) This lead to invalid partition update. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14167) Concurrency issues in reconnect. Invalid update strategy of partition update.
[ https://issues.apache.org/jira/browse/IGNITE-14167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy updated IGNITE-14167: -- Summary: Concurrency issues in reconnect. Invalid update strategy of partition update. (was: Concurrency issues in reconnect and too short backoff strategy for reconnect timeout.) > Concurrency issues in reconnect. Invalid update strategy of partition update. > - > > Key: IGNITE-14167 > URL: https://issues.apache.org/jira/browse/IGNITE-14167 > Project: Ignite > Issue Type: Bug > Components: python, thin client >Reporter: Ivan Daschinskiy >Assignee: Ivan Daschinskiy >Priority: Major > > Currently the code in Connection class is not properly synchronized and > socket can be set to None while reconnecting and sending requests > simultaneously. > Also, reconnections attempt are to short (8 fibonacci sequence items) and > total only 33 > sec. > These issues lead to flaky tests for affinity suite. -- This message was sent by Atlassian Jira (v8.3.4#803005)
