[jira] [Updated] (GEODE-10395) TXLockIdImpl memory leak after CommitConflictException from another node

2022-06-27 Thread Eugene Nedzvetsky (Jira)
Title: Message Title Eugene Nedzvetsky

[jira] [Updated] (GEODE-10395) TXLockIdImpl memory leak after CommitConflictException from another node

2022-06-27 Thread Eugene Nedzvetsky (Jira)
Title: Message Title Eugene Nedzvetsky

[jira] [Created] (GEODE-10395) TXLockIdImpl memory leak after CommitConflictException from another node

2022-06-27 Thread Eugene Nedzvetsky (Jira)
Title: Message Title Eugene Nedzvetsky

[jira] [Comment Edited] (GEODE-6950) Locator can't start if a lot of clients already started

2020-07-13 Thread Eugene Nedzvetsky (Jira)
[ https://issues.apache.org/jira/browse/GEODE-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157007#comment-17157007 ] Eugene Nedzvetsky edited comment on GEODE-6950 at 7/13/20, 10:06 PM: -

[jira] [Commented] (GEODE-6950) Locator can't start if a lot of clients already started

2020-07-13 Thread Eugene Nedzvetsky (Jira)
[ https://issues.apache.org/jira/browse/GEODE-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157007#comment-17157007 ] Eugene Nedzvetsky commented on GEODE-6950: -- Current version: {code:java} @Override public

[jira] [Updated] (GEODE-6950) Locator can't start if a lot of clients already started

2020-07-13 Thread Eugene Nedzvetsky (Jira)
[ https://issues.apache.org/jira/browse/GEODE-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-6950: - Affects Version/s: 1.10.0 1.11.0 1.12.0 >

[jira] [Commented] (GEODE-6950) Locator can't start if a lot of clients already started

2019-11-20 Thread Eugene Nedzvetsky (Jira)
[ https://issues.apache.org/jira/browse/GEODE-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978685#comment-16978685 ] Eugene Nedzvetsky commented on GEODE-6950: -- This issue still exists in the latest develop

[jira] [Updated] (GEODE-6951) Index for region key is extra slow on update

2019-07-09 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-6951: - Description: If index is created for region key CRUD operations are very slow for this

[jira] [Updated] (GEODE-6951) Index for region key is extra slow on update

2019-07-09 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-6951: - Attachment: SlowIndex.zip > Index for region key is extra slow on update >

[jira] [Updated] (GEODE-6951) Index for region key is extra slow on update

2019-07-09 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-6951: - Attachment: (was: SlowIndex.zip) > Index for region key is extra slow on update >

[jira] [Updated] (GEODE-6951) Index for region key is extra slow on update

2019-07-09 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-6951: - Attachment: SlowIndex.zip > Index for region key is extra slow on update >

[jira] [Created] (GEODE-6951) Index for region key is extra slow on update

2019-07-09 Thread Eugene Nedzvetsky (JIRA)
Eugene Nedzvetsky created GEODE-6951: Summary: Index for region key is extra slow on update Key: GEODE-6951 URL: https://issues.apache.org/jira/browse/GEODE-6951 Project: Geode Issue

[jira] [Updated] (GEODE-6950) Locator can't start if a lot of clients already started

2019-07-09 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-6950: - Affects Version/s: 1.7.0 1.8.0 1.9.0

[jira] [Updated] (GEODE-6950) Locator can't start if a lot of clients already started

2019-07-09 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-6950: - Attachment: 1.log > Locator can't start if a lot of clients already started >

[jira] [Created] (GEODE-6950) Locator can't start if a lot of clients already started

2019-07-09 Thread Eugene Nedzvetsky (JIRA)
Eugene Nedzvetsky created GEODE-6950: Summary: Locator can't start if a lot of clients already started Key: GEODE-6950 URL: https://issues.apache.org/jira/browse/GEODE-6950 Project: Geode

[jira] [Commented] (GEODE-5487) Choice of detect read conflict on transaction commit on a per-region basis.

2018-08-10 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576390#comment-16576390 ] Eugene Nedzvetsky commented on GEODE-5487: -- We use most of regions in read-only mode. Typical

[jira] [Created] (GEODE-5487) Choice of detect read conflict on transaction commit on a per-region basis.

2018-07-27 Thread Eugene Nedzvetsky (JIRA)
Eugene Nedzvetsky created GEODE-5487: Summary: Choice of detect read conflict on transaction commit on a per-region basis. Key: GEODE-5487 URL: https://issues.apache.org/jira/browse/GEODE-5487

[jira] [Updated] (GEODE-5486) Two transactions with only read operations produce CommitConflictException if property gemfire.detectReadConflict=true

2018-07-27 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-5486: - Description: Application was started with system property gemfire.detectReadConflict =

[jira] [Updated] (GEODE-5486) Two transactions with only read operations produce CommitConflictException if property gemfire.detectReadConflict=true

2018-07-27 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-5486: - Description: Application was started with system property gemfire.detectReadConflict =

[jira] [Updated] (GEODE-5486) Two transactions with only read operations produce CommitConflictException if property gemfire.detectReadConflict=true

2018-07-27 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-5486: - Attachment: TXJReadConflictTest.java > Two transactions with only read operations

[jira] [Created] (GEODE-5486) Two transactions with only read operations produce CommitConflictException if property gemfire.detectReadConflict=true

2018-07-27 Thread Eugene Nedzvetsky (JIRA)
Eugene Nedzvetsky created GEODE-5486: Summary: Two transactions with only read operations produce CommitConflictException if property gemfire.detectReadConflict=true Key: GEODE-5486 URL:

[jira] [Updated] (GEODE-4802) Geode cluster hung after network problems

2018-03-08 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-4802: - Summary: Geode cluster hung after network problems (was: Geode cluster hanged after

[jira] [Updated] (GEODE-4802) Geode cluster hanged after network problems

2018-03-07 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-4802: - Description: Test preparation: # create file bin/server1/gemfire.properties with

[jira] [Updated] (GEODE-4802) Geode cluster hanged after network problems

2018-03-07 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-4802: - Attachment: threaddump.log > Geode cluster hanged after network problems >

[jira] [Updated] (GEODE-4802) Geode cluster hanged after network problems

2018-03-07 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-4802: - Attachment: clumsy2.jpg > Geode cluster hanged after network problems >

[jira] [Created] (GEODE-4802) Geode cluster hanged after network problems

2018-03-07 Thread Eugene Nedzvetsky (JIRA)
Eugene Nedzvetsky created GEODE-4802: Summary: Geode cluster hanged after network problems Key: GEODE-4802 URL: https://issues.apache.org/jira/browse/GEODE-4802 Project: Geode Issue

[jira] [Commented] (GEODE-4748) Geode put may result in inconsistent cache if network problem occurs or serialization of key or value class fails

2018-03-06 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389202#comment-16389202 ] Eugene Nedzvetsky commented on GEODE-4748: -- Dan Smith. I couldn't reproduce this issue with drop

[jira] [Updated] (GEODE-4748) Geode put may result in inconsistent cache if serialization of key or value class fails

2018-03-02 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-4748: - Attachment: (was: geode-4748.log) > Geode put may result in inconsistent cache if

[jira] [Commented] (GEODE-4748) Geode put may result in inconsistent cache if serialization of key or value class fails

2018-03-02 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383337#comment-16383337 ] Eugene Nedzvetsky commented on GEODE-4748: -- I've simulated network problem with

[jira] [Updated] (GEODE-4748) Geode put may result in inconsistent cache if serialization of key or value class fails

2018-03-02 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-4748: - Attachment: geode-4748.log > Geode put may result in inconsistent cache if serialization

[jira] [Updated] (GEODE-4748) Geode put may result in inconsistent cache if serialization of key or value class fails

2018-03-02 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-4748: - Attachment: geode-4748.log > Geode put may result in inconsistent cache if serialization

[jira] [Updated] (GEODE-4748) Geode put may result in inconsistent cache if serialization of key or value class fails

2018-03-02 Thread Eugene Nedzvetsky (JIRA)
[ https://issues.apache.org/jira/browse/GEODE-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Nedzvetsky updated GEODE-4748: - Attachment: clumsy.jpg > Geode put may result in inconsistent cache if serialization of