[jira] [Created] (IGNITE-9768) Network partition leads to failures in Ignite's atomic data types.

2018-10-02 Thread Mo (JIRA)
Mo created IGNITE-9768: -- Summary: Network partition leads to failures in Ignite's atomic data types. Key: IGNITE-9768 URL: https://issues.apache.org/jira/browse/IGNITE-9768 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-9767) Network partition leads to failures in Ignite's semaphore

2018-10-02 Thread Mo (JIRA)
Mo created IGNITE-9767: -- Summary: Network partition leads to failures in Ignite's semaphore Key: IGNITE-9767 URL: https://issues.apache.org/jira/browse/IGNITE-9767 Project: Ignite Issue Type: Bug Af

[jira] [Created] (IGNITE-9766) Network partition leads to failures in Ignite's set

2018-10-02 Thread Mo (JIRA)
Mo created IGNITE-9766: -- Summary: Network partition leads to failures in Ignite's set Key: IGNITE-9766 URL: https://issues.apache.org/jira/browse/IGNITE-9766 Project: Ignite Issue Type: Bug Affects

[jira] [Updated] (IGNITE-9765) Network partition leads to failures in Ignite's queue

2018-10-02 Thread Mo (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mo updated IGNITE-9765: --- Description: Creating a network partition in a replicated Ignite cluster leads to creating two independent clusters

[jira] [Created] (IGNITE-9765) Network partition leads to failures in Ignite's queue

2018-10-02 Thread Mo (JIRA)
Mo created IGNITE-9765: -- Summary: Network partition leads to failures in Ignite's queue Key: IGNITE-9765 URL: https://issues.apache.org/jira/browse/IGNITE-9765 Project: Ignite Issue Type: Bug Affect

[jira] [Created] (IGNITE-9762) Network partition leads to failures in Ignite's cache

2018-10-02 Thread Mo (JIRA)
Mo created IGNITE-9762: -- Summary: Network partition leads to failures in Ignite's cache Key: IGNITE-9762 URL: https://issues.apache.org/jira/browse/IGNITE-9762 Project: Ignite Issue Type: Bug

[jira] [Updated] (IGNITE-8883) Semaphore fails on network partitioning 2

2018-10-02 Thread Mo (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-8883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mo updated IGNITE-8883: --- Affects Version/s: 2.4 > Semaphore fails on network partitioning 2 > - > >

[jira] [Updated] (IGNITE-8882) Semaphore fails on network partitioning 1

2018-10-02 Thread Mo (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-8882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mo updated IGNITE-8882: --- Affects Version/s: 2.4 > Semaphore fails on network partitioning 1 > - > >

[jira] [Created] (IGNITE-8883) Semaphore fails on network partitioning 2

2018-06-26 Thread Mo (JIRA)
Mo created IGNITE-8883: -- Summary: Semaphore fails on network partitioning 2 Key: IGNITE-8883 URL: https://issues.apache.org/jira/browse/IGNITE-8883 Project: Ignite Issue Type: Bug Components:

[jira] [Created] (IGNITE-8882) Semaphore fails on network partitioning 1

2018-06-26 Thread Mo (JIRA)
Mo created IGNITE-8882: -- Summary: Semaphore fails on network partitioning 1 Key: IGNITE-8882 URL: https://issues.apache.org/jira/browse/IGNITE-8882 Project: Ignite Issue Type: Bug Components:

[jira] [Updated] (IGNITE-8881) Semaphore hangs on network partitioning

2018-06-26 Thread Mo (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-8881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mo updated IGNITE-8881: --- Description: Scenario: Three servers (s1,s2,s3) two clients (c1,c2). A semaphore with one permit is created.  Conf

[jira] [Created] (IGNITE-8881) Semaphore hangs on network partitioning

2018-06-26 Thread Mo (JIRA)
Mo created IGNITE-8881: -- Summary: Semaphore hangs on network partitioning Key: IGNITE-8881 URL: https://issues.apache.org/jira/browse/IGNITE-8881 Project: Ignite Issue Type: Bug Components: da

[jira] [Updated] (IGNITE-8593) The semaphore's isBroken function doesn't work properly.

2018-06-26 Thread Mo (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mo updated IGNITE-8593: --- Description: Scenario: Three servers (s1,s2,s3) two clients (c1,c2). A semaphore with one permit is created.  Conf

[jira] [Updated] (IGNITE-8593) The semaphore's isBroken function doesn't work properly.

2018-06-26 Thread Mo (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mo updated IGNITE-8593: --- Description: Scenario: Three servers (s1,s2,s3) two clients (c1,c2). A semaphore with one permit is created.  Conf

[jira] [Created] (IGNITE-8593) The semaphore's isBroken function doesn't work properly.

2018-05-24 Thread Mo (JIRA)
Mo created IGNITE-8593: -- Summary: The semaphore's isBroken function doesn't work properly. Key: IGNITE-8593 URL: https://issues.apache.org/jira/browse/IGNITE-8593 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-8592) Network partitions lead to two independent clusters

2018-05-24 Thread Mo (JIRA)
Mo created IGNITE-8592: -- Summary: Network partitions lead to two independent clusters Key: IGNITE-8592 URL: https://issues.apache.org/jira/browse/IGNITE-8592 Project: Ignite Issue Type: Bug Affects