[jira] [Resolved] (GEODE-5246) QueryService.getIndexes should not return null when there are no indexes
[
https://issues.apache.org/jira/browse/GEODE-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan José Ramos Cassella resolved GEODE-5246.
-
Resolution: Fixed
Fix Version/s: 1.7.0
Changes merged into {{develop}}.
> QueryService.getIndexes should not return null when there are no indexes
>
>
> Key: GEODE-5246
> URL: https://issues.apache.org/jira/browse/GEODE-5246
> Project: Geode
> Issue Type: Improvement
> Components: querying
>Reporter: Jens Deppe
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> I was surprised to discover that {{QueryService.getIndexes(region)}} returned
> null when no indexes were defined. It seems like it would be cleaner (and
> less surprising) to return an empty collection. The doc says nothing about
> returning {{null}}. (Please fix the API and not the doc :) )
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5212) Many distributedTest and integrationTest failures on windows
[ https://issues.apache.org/jira/browse/GEODE-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571941#comment-16571941 ] ASF subversion and git services commented on GEODE-5212: Commit 7b4ca48cf86e37e9453f0566833e92e0662f80bf in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7b4ca48 ] GEODE-5212: Ignore case when comparing paths. (#2268) LocatorLauncher and ServerLauncher should ignore while validating workingDir path. > Many distributedTest and integrationTest failures on windows > > > Key: GEODE-5212 > URL: https://issues.apache.org/jira/browse/GEODE-5212 > Project: Geode > Issue Type: Task > Components: general, gfsh >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available, windows > Time Spent: 3h 20m > Remaining Estimate: 0h > > Windows regressions currently fail spectacularly. The primary culprits > appear to be based around filesystem I/O and passing the current working > directory to members started by our testing framework. > > The scope of this ticket will be defined by "refactors" as children tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5502) Cluster configuration can contain member-specific gateway receiver definitions which cause members to fail to start during rolling
[
https://issues.apache.org/jira/browse/GEODE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barry Oglesby resolved GEODE-5502.
--
Resolution: Fixed
Fix Version/s: 1.7.0
> Cluster configuration can contain member-specific gateway receiver
> definitions which cause members to fail to start during rolling
> --
>
> Key: GEODE-5502
> URL: https://issues.apache.org/jira/browse/GEODE-5502
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available, swat
> Fix For: 1.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In versions before 1.4.0, cluster configuration could contain multiple
> member-specific gateway receiver definitions like:
> {noformat}
>
>
>
>
> {noformat}
> Starting in 1.4.0, multiple receivers are no longer allowed, so a
> configuration like this causes the member to throw an exception and fail to
> start.
> These member-specific receivers should be removed before sending the cluster
> configuration to new members to avoid attempting to create multiple receivers
> in a single member.
> Note: In this case, the member will start with no receivers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5535) Upgrade fast-classpath-scanner to 4.x
Jens Deppe created GEODE-5535: - Summary: Upgrade fast-classpath-scanner to 4.x Key: GEODE-5535 URL: https://issues.apache.org/jira/browse/GEODE-5535 Project: Geode Issue Type: Improvement Components: gfsh Reporter: Jens Deppe The package has been renamed to 'ClassGraph'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5534) With oql indexes and compression enabled, memory usage is greater after compression than before
[
https://issues.apache.org/jira/browse/GEODE-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572021#comment-16572021
]
ASF subversion and git services commented on GEODE-5534:
Commit 9c73847e73e5a0fe007c248c10629c648c70ffa6 in geode's branch
refs/heads/feature/GEODE-5534 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9c73847 ]
GEODE-5534: Forced index key to be a string when a compressed region contains
PDX values
> With oql indexes and compression enabled, memory usage is greater after
> compression than before
> ---
>
> Key: GEODE-5534
> URL: https://issues.apache.org/jira/browse/GEODE-5534
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: swat
>
> A test that shows the behavior is:
> - xml configuration like:
> {noformat}
>
> data-policy="persistent-replicate" disk-store-name="orderDiskStore"
> disk-synchronous="false" cloning-enabled="true">
>
> org.apache.geode.compression.SnappyCompressor
>
>
> expression="index_from.clOrdID" type="range"/>
> expression="index_from.externalOrderID" type="range"/>
> expression="index_from.externalOrderIDSource" type="range"/>
> expression="index_from.orderID" type="range"/>
> expression="index_from.parentOrderID" type="range"/>
>
> {noformat}
> - an Order object defining string fields for clOrdID, externalOrderID,
> orderID and parentOrderID and an enum field for externalOrderIDSource
> Here are some histograms showing the behavior:
> With indexes and no compression:
> {noformat}
> num #instances #bytes class name
> --
> 1: 502136 562132008 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 50 800
> org.apache.geode.internal.cache.PreferBytesCachedDeserializable
> 9: 250680 6016320 java.util.concurrent.ConcurrentSkipListMap$Index
> 10: 80 4196104
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> Total 5474612 739440976
> {noformat}
> With indexes and compression
> {noformat}
> num #instances #bytes class name
> --
> 1: 1003644 643754184 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 250889 6021336 java.util.concurrent.ConcurrentSkipListMap$Index
> 9: 80 4196096
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> 10: 34380 3261936 [C
> Total 5476808 813096488
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5534) With oql indexes and compression enabled, memory usage is greater after compression than before
[
https://issues.apache.org/jira/browse/GEODE-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5534:
--
Labels: pull-request-available swat (was: swat)
> With oql indexes and compression enabled, memory usage is greater after
> compression than before
> ---
>
> Key: GEODE-5534
> URL: https://issues.apache.org/jira/browse/GEODE-5534
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available, swat
>
> A test that shows the behavior is:
> - xml configuration like:
> {noformat}
>
> data-policy="persistent-replicate" disk-store-name="orderDiskStore"
> disk-synchronous="false" cloning-enabled="true">
>
> org.apache.geode.compression.SnappyCompressor
>
>
> expression="index_from.clOrdID" type="range"/>
> expression="index_from.externalOrderID" type="range"/>
> expression="index_from.externalOrderIDSource" type="range"/>
> expression="index_from.orderID" type="range"/>
> expression="index_from.parentOrderID" type="range"/>
>
> {noformat}
> - an Order object defining string fields for clOrdID, externalOrderID,
> orderID and parentOrderID and an enum field for externalOrderIDSource
> Here are some histograms showing the behavior:
> With indexes and no compression:
> {noformat}
> num #instances #bytes class name
> --
> 1: 502136 562132008 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 50 800
> org.apache.geode.internal.cache.PreferBytesCachedDeserializable
> 9: 250680 6016320 java.util.concurrent.ConcurrentSkipListMap$Index
> 10: 80 4196104
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> Total 5474612 739440976
> {noformat}
> With indexes and compression
> {noformat}
> num #instances #bytes class name
> --
> 1: 1003644 643754184 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 250889 6021336 java.util.concurrent.ConcurrentSkipListMap$Index
> 9: 80 4196096
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> 10: 34380 3261936 [C
> Total 5476808 813096488
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5536) Parallelize unit tests
Finn Southerland created GEODE-5536: --- Summary: Parallelize unit tests Key: GEODE-5536 URL: https://issues.apache.org/jira/browse/GEODE-5536 Project: Geode Issue Type: Task Reporter: Finn Southerland Unit tests should run in parallel within subprojects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5536) Parallelize unit tests
[ https://issues.apache.org/jira/browse/GEODE-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572080#comment-16572080 ] ASF subversion and git services commented on GEODE-5536: Commit 31cfb98eb98731c4eedb5d0941a8b080c494ce95 in geode's branch refs/heads/develop from [~fsoutherland] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=31cfb98 ] GEODE-5536 let unit tests fork to run in parallel Signed-off-by: Jacob Barrett > Parallelize unit tests > -- > > Key: GEODE-5536 > URL: https://issues.apache.org/jira/browse/GEODE-5536 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > > Unit tests should run in parallel within subprojects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5463) The generated diskstore restore script is incorrect on Windows
[
https://issues.apache.org/jira/browse/GEODE-5463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572084#comment-16572084
]
ASF subversion and git services commented on GEODE-5463:
Commit 619e3cf126fa04122c5a6741fe89fa03bf2014e8 in geode's branch
refs/heads/develop from Sai Boorlagadda
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=619e3cf ]
GEODE-5463: Generated restore.bat script is incorrect for Windows
ensure that statements creating directories
are not interpreted as oplog files
Signed-off-by: Jens Deppe
> The generated diskstore restore script is incorrect on Windows
> --
>
> Key: GEODE-5463
> URL: https://issues.apache.org/jira/browse/GEODE-5463
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The auto-generated {{restore.bat}} script is incorrect on Windows as there
> are slight differences in the implementations of {{ScriptGenerator}} between
> Windows and Unix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5537) offheap with indexes and pdx can consume too much heap memory
Darrel Schneider created GEODE-5537: --- Summary: offheap with indexes and pdx can consume too much heap memory Key: GEODE-5537 URL: https://issues.apache.org/jira/browse/GEODE-5537 Project: Geode Issue Type: Bug Components: offheap Reporter: Darrel Schneider Much like GEODE-5534, if and off-heap region has an index and the off-heap value is a pdx with a String field, then the String the index references will be a PdxString instance that ends up keeping a byte array in the heap that is the size of the entire off-heap serialized value instead of just the size of the String field. The fix for this should be much like GEODE-5534 but test for the region being offheap instead of having a compressor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5212) Many distributedTest and integrationTest failures on windows
[ https://issues.apache.org/jira/browse/GEODE-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572151#comment-16572151 ] ASF subversion and git services commented on GEODE-5212: Commit db224899ad8b700d93a7274f521970af1da3f051 in geode's branch refs/heads/feature/GEODE-5212-fix-launcher-tests from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=db22489 ] GEODE-5212: Fix launcher test failures Signed-off-by: Sai Boorlagadda > Many distributedTest and integrationTest failures on windows > > > Key: GEODE-5212 > URL: https://issues.apache.org/jira/browse/GEODE-5212 > Project: Geode > Issue Type: Task > Components: general, gfsh >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available, windows > Time Spent: 3h 20m > Remaining Estimate: 0h > > Windows regressions currently fail spectacularly. The primary culprits > appear to be based around filesystem I/O and passing the current working > directory to members started by our testing framework. > > The scope of this ticket will be defined by "refactors" as children tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5522) Upgrade to Gradle 4.9
[ https://issues.apache.org/jira/browse/GEODE-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-5522. Resolution: Fixed Fix Version/s: 1.7.0 > Upgrade to Gradle 4.9 > - > > Key: GEODE-5522 > URL: https://issues.apache.org/jira/browse/GEODE-5522 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5522) Upgrade to Gradle 4.9
[ https://issues.apache.org/jira/browse/GEODE-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun closed GEODE-5522. -- > Upgrade to Gradle 4.9 > - > > Key: GEODE-5522 > URL: https://issues.apache.org/jira/browse/GEODE-5522 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5535) Upgrade fast-classpath-scanner to 4.x
[ https://issues.apache.org/jira/browse/GEODE-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-5535: - Assignee: Jens Deppe > Upgrade fast-classpath-scanner to 4.x > - > > Key: GEODE-5535 > URL: https://issues.apache.org/jira/browse/GEODE-5535 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > > The package has been renamed to 'ClassGraph'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5534) With oql indexes and compression enabled, memory usage is greater after compression than before
[
https://issues.apache.org/jira/browse/GEODE-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572204#comment-16572204
]
ASF subversion and git services commented on GEODE-5534:
Commit 0c4d1822b10fbb3413724733fd35448999efe7d9 in geode's branch
refs/heads/feature/GEODE-5534 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0c4d182 ]
GEODE-5534: Removed InternalRegion cast
> With oql indexes and compression enabled, memory usage is greater after
> compression than before
> ---
>
> Key: GEODE-5534
> URL: https://issues.apache.org/jira/browse/GEODE-5534
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> A test that shows the behavior is:
> - xml configuration like:
> {noformat}
>
> data-policy="persistent-replicate" disk-store-name="orderDiskStore"
> disk-synchronous="false" cloning-enabled="true">
>
> org.apache.geode.compression.SnappyCompressor
>
>
> expression="index_from.clOrdID" type="range"/>
> expression="index_from.externalOrderID" type="range"/>
> expression="index_from.externalOrderIDSource" type="range"/>
> expression="index_from.orderID" type="range"/>
> expression="index_from.parentOrderID" type="range"/>
>
> {noformat}
> - an Order object defining string fields for clOrdID, externalOrderID,
> orderID and parentOrderID and an enum field for externalOrderIDSource
> Here are some histograms showing the behavior:
> With indexes and no compression:
> {noformat}
> num #instances #bytes class name
> --
> 1: 502136 562132008 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 50 800
> org.apache.geode.internal.cache.PreferBytesCachedDeserializable
> 9: 250680 6016320 java.util.concurrent.ConcurrentSkipListMap$Index
> 10: 80 4196104
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> Total 5474612 739440976
> {noformat}
> With indexes and compression
> {noformat}
> num #instances #bytes class name
> --
> 1: 1003644 643754184 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 250889 6021336 java.util.concurrent.ConcurrentSkipListMap$Index
> 9: 80 4196096
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> 10: 34380 3261936 [C
> Total 5476808 813096488
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5521) After an exception is received from a remote server function execution, local threads should not send back result to client later
[
https://issues.apache.org/jira/browse/GEODE-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1657#comment-1657
]
ASF subversion and git services commented on GEODE-5521:
Commit 82ac395f6c88adfc6e2f2c71ef396b154c9e08e6 in geode's branch
refs/heads/develop from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=82ac395 ]
GEODE-5521: lastResultReceived flag set (#2255)
* When an exception is received lastResultReceived flag is set.
* Previously this flag is only set if exception is of type
QueryInvocationTargetException or FunctionInvocationTargetException
* Setting this flag will prevent other threads from sending results to
the client after the exception is sent.
> After an exception is received from a remote server function execution, local
> threads should not send back result to client later
> -
>
> Key: GEODE-5521
> URL: https://issues.apache.org/jira/browse/GEODE-5521
> Project: Geode
> Issue Type: Bug
> Components: functions
>Reporter: nabarun
>Assignee: nabarun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In the method cmdExecute()
> if the local co-ordinator receives an FunctionException of type
> FunctionInvocationTargetException or QueryInvocationTargetException from the
> remote server, setException is called which sets the lastResultReceived flag.
> This flag prevents other results from other threads to be sent to the client,
> as the client may have moved on.
> If there were any other function exception it will just send the exception
> but not set the flag.
> {code:java}
> if (cause instanceof FunctionInvocationTargetException
> || cause instanceof QueryInvocationTargetException) {
> if (cause instanceof InternalFunctionInvocationTargetException) {
> // Fix for #44709: User should not be aware of
> // InternalFunctionInvocationTargetException. No instance of
> // InternalFunctionInvocationTargetException is giving useful
> // information to user to take any corrective action hence logging
> // this at fine level logging
> // 1> When bucket is moved
> // 2> Incase of HA FucntionInvocationTargetException thrown. Since
> // it is HA, fucntion will be reexecuted on right node
> // 3> Multiple target nodes found for single hop operation
> // 4> in case of HA member departed
> if (logger.isDebugEnabled()) {
> logger.debug(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> new Object[] {function}), fe);
> }
> } else if (functionObject.isHA()) {
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function + " :" + message));
> } else {
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function), fe);
> }
> resultSender.setException(fe);
> } else {
> if(!resultSender.isLastResultReceived()){
> resultSender.setLastResultReceived(true);
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function), fe);
> sendException(hasResult, clientMessage, message, serverConnection,
> fe);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5521) After an exception is received from a remote server function execution, local threads should not send back result to client later
[
https://issues.apache.org/jira/browse/GEODE-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun resolved GEODE-5521.
Resolution: Fixed
Fix Version/s: 1.7.0
> After an exception is received from a remote server function execution, local
> threads should not send back result to client later
> -
>
> Key: GEODE-5521
> URL: https://issues.apache.org/jira/browse/GEODE-5521
> Project: Geode
> Issue Type: Bug
> Components: functions
>Reporter: nabarun
>Assignee: nabarun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In the method cmdExecute()
> if the local co-ordinator receives an FunctionException of type
> FunctionInvocationTargetException or QueryInvocationTargetException from the
> remote server, setException is called which sets the lastResultReceived flag.
> This flag prevents other results from other threads to be sent to the client,
> as the client may have moved on.
> If there were any other function exception it will just send the exception
> but not set the flag.
> {code:java}
> if (cause instanceof FunctionInvocationTargetException
> || cause instanceof QueryInvocationTargetException) {
> if (cause instanceof InternalFunctionInvocationTargetException) {
> // Fix for #44709: User should not be aware of
> // InternalFunctionInvocationTargetException. No instance of
> // InternalFunctionInvocationTargetException is giving useful
> // information to user to take any corrective action hence logging
> // this at fine level logging
> // 1> When bucket is moved
> // 2> Incase of HA FucntionInvocationTargetException thrown. Since
> // it is HA, fucntion will be reexecuted on right node
> // 3> Multiple target nodes found for single hop operation
> // 4> in case of HA member departed
> if (logger.isDebugEnabled()) {
> logger.debug(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> new Object[] {function}), fe);
> }
> } else if (functionObject.isHA()) {
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function + " :" + message));
> } else {
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function), fe);
> }
> resultSender.setException(fe);
> } else {
> if(!resultSender.isLastResultReceived()){
> resultSender.setLastResultReceived(true);
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function), fe);
> sendException(hasResult, clientMessage, message, serverConnection,
> fe);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-5521) After an exception is received from a remote server function execution, local threads should not send back result to client later
[
https://issues.apache.org/jira/browse/GEODE-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun closed GEODE-5521.
--
> After an exception is received from a remote server function execution, local
> threads should not send back result to client later
> -
>
> Key: GEODE-5521
> URL: https://issues.apache.org/jira/browse/GEODE-5521
> Project: Geode
> Issue Type: Bug
> Components: functions
>Reporter: nabarun
>Assignee: nabarun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In the method cmdExecute()
> if the local co-ordinator receives an FunctionException of type
> FunctionInvocationTargetException or QueryInvocationTargetException from the
> remote server, setException is called which sets the lastResultReceived flag.
> This flag prevents other results from other threads to be sent to the client,
> as the client may have moved on.
> If there were any other function exception it will just send the exception
> but not set the flag.
> {code:java}
> if (cause instanceof FunctionInvocationTargetException
> || cause instanceof QueryInvocationTargetException) {
> if (cause instanceof InternalFunctionInvocationTargetException) {
> // Fix for #44709: User should not be aware of
> // InternalFunctionInvocationTargetException. No instance of
> // InternalFunctionInvocationTargetException is giving useful
> // information to user to take any corrective action hence logging
> // this at fine level logging
> // 1> When bucket is moved
> // 2> Incase of HA FucntionInvocationTargetException thrown. Since
> // it is HA, fucntion will be reexecuted on right node
> // 3> Multiple target nodes found for single hop operation
> // 4> in case of HA member departed
> if (logger.isDebugEnabled()) {
> logger.debug(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> new Object[] {function}), fe);
> }
> } else if (functionObject.isHA()) {
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function + " :" + message));
> } else {
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function), fe);
> }
> resultSender.setException(fe);
> } else {
> if(!resultSender.isLastResultReceived()){
> resultSender.setLastResultReceived(true);
> logger.warn(LocalizedMessage.create(
>
> LocalizedStrings.ExecuteRegionFunction_EXCEPTION_ON_SERVER_WHILE_EXECUTIONG_FUNCTION_0,
> function), fe);
> sendException(hasResult, clientMessage, message, serverConnection,
> fe);
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-577) SUPERFLAKY: QueryMonitorDUnitTest is flaky and needs to be rewritten (60 failures in 200)
[
https://issues.apache.org/jira/browse/GEODE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572248#comment-16572248
]
ASF subversion and git services commented on GEODE-577:
---
Commit 7c236a70ca5fcea8757412bab2fdd529d3753a0a in geode's branch
refs/heads/develop from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7c236a7 ]
GEODE-577: rewrite QueryMonitorDUnitTest (#2266)
* use rules
* test hook waits till query is cancelled to proceed with the query
* add a junit test
* do not monitor cq query
> SUPERFLAKY: QueryMonitorDUnitTest is flaky and needs to be rewritten (60
> failures in 200)
> -
>
> Key: GEODE-577
> URL: https://issues.apache.org/jira/browse/GEODE-577
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Jinmei Liao
>Priority: Major
> Labels: CI, Flaky, pull-request-available, swat
> Fix For: 1.7.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> GemFire_develop_DistributedTests
> Private Build #38 (Nov 15, 2015 3:12:12 PM)
> Revision: b7f640cf2e41acb40a531cc7abbee932a9ea093c
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> Error Message
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1
> running on Host latvia.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1
> running on Host latvia.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:369)
> at dunit.VM.invoke(VM.java:312)
> at dunit.VM.invoke(VM.java:266)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest.testQueryExecutionLocally(QueryMonitorDUnitTest.java:493)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor123.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordF
[jira] [Commented] (GEODE-5212) Many distributedTest and integrationTest failures on windows
[ https://issues.apache.org/jira/browse/GEODE-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572296#comment-16572296 ] ASF subversion and git services commented on GEODE-5212: Commit d5bdece4afa6849fbd017e282ef01c61ee2ec640 in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d5bdece ] GEODE-5212: Fix launcher test failures (#2273) > Many distributedTest and integrationTest failures on windows > > > Key: GEODE-5212 > URL: https://issues.apache.org/jira/browse/GEODE-5212 > Project: Geode > Issue Type: Task > Components: general, gfsh >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available, windows > Time Spent: 3h 40m > Remaining Estimate: 0h > > Windows regressions currently fail spectacularly. The primary culprits > appear to be based around filesystem I/O and passing the current working > directory to members started by our testing framework. > > The scope of this ticket will be defined by "refactors" as children tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5499) SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror
[
https://issues.apache.org/jira/browse/GEODE-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-5499.
--
Resolution: Fixed
Fix Version/s: 1.8.0
> SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror
> --
>
> Key: GEODE-5499
> URL: https://issues.apache.org/jira/browse/GEODE-5499
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: pull-request-available, swat
> Fix For: 1.8.0
>
> Attachments: Test results - Class
> org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest.html
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This test is failing fairly frequently in CI
> {noformat}
> org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest: 6 failures
> (98.101% success rate)
> | .testTXRmtMirror: 6 failures (98.101% success rate)
> | | Failed build 315 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/315
> | | Failed build 296 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/296
> | | Failed build 233 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/233
> | | Failed build 123 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/123
> | | Failed build 84 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/84
> | | Failed build 51 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/51
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5499) SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror
[
https://issues.apache.org/jira/browse/GEODE-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572311#comment-16572311
]
ASF subversion and git services commented on GEODE-5499:
Commit 946ec0ebf5553a4e5dbf45cbf08c29dbfc1bd68d in geode's branch
refs/heads/develop from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=946ec0e ]
GEODE-5499: Changing testTxRmtMirror to use awaitility, not 200 ms sleep
> SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror
> --
>
> Key: GEODE-5499
> URL: https://issues.apache.org/jira/browse/GEODE-5499
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Dan Smith
>Priority: Major
> Labels: pull-request-available, swat
> Fix For: 1.8.0
>
> Attachments: Test results - Class
> org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest.html
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This test is failing fairly frequently in CI
> {noformat}
> org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest: 6 failures
> (98.101% success rate)
> | .testTXRmtMirror: 6 failures (98.101% success rate)
> | | Failed build 315 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/315
> | | Failed build 296 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/296
> | | Failed build 233 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/233
> | | Failed build 123 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/123
> | | Failed build 84 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/84
> | | Failed build 51 at
> https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/51
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5470) SUPERFLAKY: DlockAndTxlockRegressionTest > testDLockProtectsAgainstTransactionConflict FAILED
[ https://issues.apache.org/jira/browse/GEODE-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572315#comment-16572315 ] ASF subversion and git services commented on GEODE-5470: Commit fcd6940600bc0ad3593a492c9a3a30bef4a9bf76 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fcd6940 ] GEODE-5470: Deleting flaky DlockAndTxLockRegressionTest This test was introduced as part of the fix for GEODE-4928. However, we've determined that GEODE-4928 is not actually fixed, which is why this test is sporadically failing. Since GEODE-4928 actually appears to be trying to introduce new behavior for dlocks that is a rather involved feature to implement. Leaving that feature for another time and deleting this test. > SUPERFLAKY: DlockAndTxlockRegressionTest > > testDLockProtectsAgainstTransactionConflict FAILED > - > > Key: GEODE-5470 > URL: https://issues.apache.org/jira/browse/GEODE-5470 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139 > > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest > > testDLockProtectsAgainstTransactionConflict FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:255] > java.lang.RuntimeException: test failed > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:256] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.testDLockProtectsAgainstTransactionConflict(DlockAndTxlockRegressionTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:257] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:258] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:259] > java.lang.RuntimeException: dlock failed to prevent a transaction conflict > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:260] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.performOps(DlockAndTxlockRegressionTest.java:234) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:261] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.lambda$testDLockProtectsAgainstTransactionConflict$bb17a952$5(DlockAndTxlockRegressionTest.java:123) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:262] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:263] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:264] > org.apache.geode.cache.CommitConflictException: Concurrent transaction > commit detected The key TestKey in region /TestRegion was being modified by > another transaction locally. > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:265] > at > org.apache.geode.internal.cache.locks.TXLockServiceImpl.txLock(TXLockServiceImpl.java:137) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:266] > at > org.apache.geode.internal.cache.TXLockRequest.obtain(TXLockRequest.java:88) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:267] > at org.apache.geode.internal.cache.TXState.reserveAndCheck(TXState.java:340) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:268] > at org.apache.geode.internal.cache.TXState.commit(TXState.java:411) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:269] > at > org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:210) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:270] > at > org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:413) > [
[jira] [Commented] (GEODE-4928) DistributedLockService doesn't work as expected while the dlock grantor is initialized
[ https://issues.apache.org/jira/browse/GEODE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572318#comment-16572318 ] ASF subversion and git services commented on GEODE-4928: Commit fcd6940600bc0ad3593a492c9a3a30bef4a9bf76 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fcd6940 ] GEODE-5470: Deleting flaky DlockAndTxLockRegressionTest This test was introduced as part of the fix for GEODE-4928. However, we've determined that GEODE-4928 is not actually fixed, which is why this test is sporadically failing. Since GEODE-4928 actually appears to be trying to introduce new behavior for dlocks that is a rather involved feature to implement. Leaving that feature for another time and deleting this test. > DistributedLockService doesn't work as expected while the dlock grantor is > initialized > -- > > Key: GEODE-4928 > URL: https://issues.apache.org/jira/browse/GEODE-4928 > Project: Geode > Issue Type: New Feature > Components: distributed lock service >Reporter: Bruce Schuchardt >Priority: Minor > Labels: pull-request-available > Time Spent: 2.5h > Remaining Estimate: 0h > > I wrote a function that obtained a dlock and then performed a transaction. > It always operates on the same dlock key and the same keys in my region. > That protects against getting a commit conflict exception BUT this sometimes > fails if the JVM holding the lock crashes. One of the functions appears to > get the dlock okay but then its transaction fails when it goes to commit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4928) DistributedLockService doesn't work as expected while the dlock grantor is initialized
[ https://issues.apache.org/jira/browse/GEODE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572317#comment-16572317 ] ASF subversion and git services commented on GEODE-4928: Commit fcd6940600bc0ad3593a492c9a3a30bef4a9bf76 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fcd6940 ] GEODE-5470: Deleting flaky DlockAndTxLockRegressionTest This test was introduced as part of the fix for GEODE-4928. However, we've determined that GEODE-4928 is not actually fixed, which is why this test is sporadically failing. Since GEODE-4928 actually appears to be trying to introduce new behavior for dlocks that is a rather involved feature to implement. Leaving that feature for another time and deleting this test. > DistributedLockService doesn't work as expected while the dlock grantor is > initialized > -- > > Key: GEODE-4928 > URL: https://issues.apache.org/jira/browse/GEODE-4928 > Project: Geode > Issue Type: New Feature > Components: distributed lock service >Reporter: Bruce Schuchardt >Priority: Minor > Labels: pull-request-available > Time Spent: 2.5h > Remaining Estimate: 0h > > I wrote a function that obtained a dlock and then performed a transaction. > It always operates on the same dlock key and the same keys in my region. > That protects against getting a commit conflict exception BUT this sometimes > fails if the JVM holding the lock crashes. One of the functions appears to > get the dlock okay but then its transaction fails when it goes to commit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5470) SUPERFLAKY: DlockAndTxlockRegressionTest > testDLockProtectsAgainstTransactionConflict FAILED
[ https://issues.apache.org/jira/browse/GEODE-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5470. -- Resolution: Fixed Fix Version/s: 1.8.0 > SUPERFLAKY: DlockAndTxlockRegressionTest > > testDLockProtectsAgainstTransactionConflict FAILED > - > > Key: GEODE-5470 > URL: https://issues.apache.org/jira/browse/GEODE-5470 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139 > > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest > > testDLockProtectsAgainstTransactionConflict FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:255] > java.lang.RuntimeException: test failed > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:256] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.testDLockProtectsAgainstTransactionConflict(DlockAndTxlockRegressionTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:257] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:258] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:259] > java.lang.RuntimeException: dlock failed to prevent a transaction conflict > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:260] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.performOps(DlockAndTxlockRegressionTest.java:234) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:261] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.lambda$testDLockProtectsAgainstTransactionConflict$bb17a952$5(DlockAndTxlockRegressionTest.java:123) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:262] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:263] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:264] > org.apache.geode.cache.CommitConflictException: Concurrent transaction > commit detected The key TestKey in region /TestRegion was being modified by > another transaction locally. > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:265] > at > org.apache.geode.internal.cache.locks.TXLockServiceImpl.txLock(TXLockServiceImpl.java:137) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:266] > at > org.apache.geode.internal.cache.TXLockRequest.obtain(TXLockRequest.java:88) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:267] > at org.apache.geode.internal.cache.TXState.reserveAndCheck(TXState.java:340) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:268] > at org.apache.geode.internal.cache.TXState.commit(TXState.java:411) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:269] > at > org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:210) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:270] > at > org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:413) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:271] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.performOps(DlockAndTxlockRegressionTest.java:232) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:272] > ... 1 more > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4928) DistributedLockService doesn't work as expected while the dlock grantor is initialized
[ https://issues.apache.org/jira/browse/GEODE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572316#comment-16572316 ] ASF subversion and git services commented on GEODE-4928: Commit fcd6940600bc0ad3593a492c9a3a30bef4a9bf76 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fcd6940 ] GEODE-5470: Deleting flaky DlockAndTxLockRegressionTest This test was introduced as part of the fix for GEODE-4928. However, we've determined that GEODE-4928 is not actually fixed, which is why this test is sporadically failing. Since GEODE-4928 actually appears to be trying to introduce new behavior for dlocks that is a rather involved feature to implement. Leaving that feature for another time and deleting this test. > DistributedLockService doesn't work as expected while the dlock grantor is > initialized > -- > > Key: GEODE-4928 > URL: https://issues.apache.org/jira/browse/GEODE-4928 > Project: Geode > Issue Type: New Feature > Components: distributed lock service >Reporter: Bruce Schuchardt >Priority: Minor > Labels: pull-request-available > Time Spent: 2.5h > Remaining Estimate: 0h > > I wrote a function that obtained a dlock and then performed a transaction. > It always operates on the same dlock key and the same keys in my region. > That protects against getting a commit conflict exception BUT this sometimes > fails if the JVM holding the lock crashes. One of the functions appears to > get the dlock okay but then its transaction fails when it goes to commit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5538) Move examples job to a different pipeline
Finn Southerland created GEODE-5538: --- Summary: Move examples job to a different pipeline Key: GEODE-5538 URL: https://issues.apache.org/jira/browse/GEODE-5538 Project: Geode Issue Type: Task Reporter: Finn Southerland Since it uses different resources and is it's own repository, testing geode-examples should be separate from the develop pipeline. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5539) Remove pr tags from all jobs.
Sean Goller created GEODE-5539: -- Summary: Remove pr tags from all jobs. Key: GEODE-5539 URL: https://issues.apache.org/jira/browse/GEODE-5539 Project: Geode Issue Type: Improvement Components: ci Reporter: Sean Goller Given the workflow change, we no longer need workers tagged with pr. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5539) Remove pr tags from all jobs.
[ https://issues.apache.org/jira/browse/GEODE-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5539: -- Labels: pull-request-available (was: ) > Remove pr tags from all jobs. > - > > Key: GEODE-5539 > URL: https://issues.apache.org/jira/browse/GEODE-5539 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > Given the workflow change, we no longer need workers tagged with pr. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5539) Remove pr tags from all jobs.
[ https://issues.apache.org/jira/browse/GEODE-5539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572435#comment-16572435 ] ASF subversion and git services commented on GEODE-5539: Commit b6f55c7e9cdd45243729d0e02824c39ee7e400e0 in geode's branch refs/heads/develop from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b6f55c7 ] [GEODE-5539] remove pr tags from jobs, provide sane defaults. Signed-off-by: Dick Cavender > Remove pr tags from all jobs. > - > > Key: GEODE-5539 > URL: https://issues.apache.org/jira/browse/GEODE-5539 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Given the workflow change, we no longer need workers tagged with pr. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-838) ClientAuthenticationDUnitTest.testCredentialsForNotifications failed
[
https://issues.apache.org/jira/browse/GEODE-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-838:
-
Labels: CI Flaky pull-request-available swat (was: CI Flaky swat)
> ClientAuthenticationDUnitTest.testCredentialsForNotifications failed
>
>
> Key: GEODE-838
> URL: https://issues.apache.org/jira/browse/GEODE-838
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: xiaojian zhou
>Assignee: Jinmei Liao
>Priority: Major
> Labels: CI, Flaky, pull-request-available, swat
> Fix For: 1.0.0-incubating
>
>
> Revision: 5424312dcb3151ba6ddafca9bf8c4b0fc335f7af
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.createCacheServer
> in VM 1 running on Host zambia.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:173)
> at
> com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.itestCredentialsForNotifications(ClientAuthenticationDUnitTest.java:765)
> at
> com.gemstone.gemfire.security.ClientAuthenticationDUnitTest.testCredentialsForNotifications(ClientAuthenticationDUnitTest.java:701)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: junit.framework.AssertionFailedError: Got unexpected exception
> when starting peer: com.gemstone.gemfire.GemFireIOException: Problem starting
> a locator service
> at
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:772)
> at
> com.gemst
[jira] [Updated] (GEODE-4128) CI failure: org.apache.geode.session.tests.Jetty9Test > newContainersShouldShareDataAccess
[ https://issues.apache.org/jira/browse/GEODE-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helena Bales updated GEODE-4128: Labels: swat (was: ) > CI failure: org.apache.geode.session.tests.Jetty9Test > > newContainersShouldShareDataAccess > -- > > Key: GEODE-4128 > URL: https://issues.apache.org/jira/browse/GEODE-4128 > Project: Geode > Issue Type: Bug > Components: http session >Affects Versions: 1.4.0 >Reporter: Shelley Lynn Hughes-Godfrey >Priority: Major > Labels: swat > > org.apache.geode.session.tests.Jetty9Test > > newContainersShouldShareDataAccess FAILED > org.codehaus.cargo.container.ContainerException: Failed to stop the Jetty > 9.4.5.v20170502 container. Check the > [/tmp/build/ae3c03f4/built-gemfire/test/geode/geode-assembly/build/distributedTest28/cargo_logs/JETTY9_peer-to-peer_newContainersShouldShareDataAccess_1_6875641539702712/container.log] > file containing the container logs for more details. > Caused by: > org.codehaus.cargo.container.ContainerException: Server port 21013 > did not shutdown within the timeout period [12] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5487) Choice of detect read conflict on transaction commit on a per-region basis.
[ https://issues.apache.org/jira/browse/GEODE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-5487: --- Component/s: docs > 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 > Project: Geode > Issue Type: Improvement > Components: docs, transactions >Reporter: Eugene Nedzvetsky >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Geode supports detect read conflict(-Dgemfire.detectReadConflicts=true) on > transaction commit(see > https://geode.apache.org/docs/guide/11/developing/transactions/transaction_semantics.html) > This functionality can be enabled only on application level. It can > dramatically decrease application performance. > I propose to add ability to setup this property per region basis. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5534) With oql indexes and compression enabled, memory usage is greater after compression than before
[
https://issues.apache.org/jira/browse/GEODE-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572484#comment-16572484
]
ASF subversion and git services commented on GEODE-5534:
Commit f4710870495d5a3eb9ba05e7502814e9ef58280f in geode's branch
refs/heads/feature/GEODE-5534 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f471087 ]
GEODE-5534: Added integration test
> With oql indexes and compression enabled, memory usage is greater after
> compression than before
> ---
>
> Key: GEODE-5534
> URL: https://issues.apache.org/jira/browse/GEODE-5534
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 1h
> Remaining Estimate: 0h
>
> A test that shows the behavior is:
> - xml configuration like:
> {noformat}
>
> data-policy="persistent-replicate" disk-store-name="orderDiskStore"
> disk-synchronous="false" cloning-enabled="true">
>
> org.apache.geode.compression.SnappyCompressor
>
>
> expression="index_from.clOrdID" type="range"/>
> expression="index_from.externalOrderID" type="range"/>
> expression="index_from.externalOrderIDSource" type="range"/>
> expression="index_from.orderID" type="range"/>
> expression="index_from.parentOrderID" type="range"/>
>
> {noformat}
> - an Order object defining string fields for clOrdID, externalOrderID,
> orderID and parentOrderID and an enum field for externalOrderIDSource
> Here are some histograms showing the behavior:
> With indexes and no compression:
> {noformat}
> num #instances #bytes class name
> --
> 1: 502136 562132008 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 50 800
> org.apache.geode.internal.cache.PreferBytesCachedDeserializable
> 9: 250680 6016320 java.util.concurrent.ConcurrentSkipListMap$Index
> 10: 80 4196104
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> Total 5474612 739440976
> {noformat}
> With indexes and compression
> {noformat}
> num #instances #bytes class name
> --
> 1: 1003644 643754184 [B
> 2: 200 4800
> org.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node
> 3: 40 35999280
> org.apache.geode.internal.cache.entries.VersionedThinDiskRegionEntryHeapStringKey2
> 4: 54 24000192
> org.apache.geode.internal.cache.DiskId$PersistenceWithIntOffset
> 5: 1503 15457776
> [Lorg.apache.geode.internal.concurrent.CompactConcurrentHashSet2$Node;
> 6: 501508 12036192 java.util.concurrent.ConcurrentSkipListMap$Node
> 7: 501500 12036000 org.apache.geode.pdx.internal.PdxString
> 8: 250889 6021336 java.util.concurrent.ConcurrentSkipListMap$Index
> 9: 80 4196096
> [Lorg.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap$HashEntry;
> 10: 34380 3261936 [C
> Total 5476808 813096488
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5538) Move examples job to a different pipeline
[ https://issues.apache.org/jira/browse/GEODE-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5538: -- Labels: pull-request-available (was: ) > Move examples job to a different pipeline > - > > Key: GEODE-5538 > URL: https://issues.apache.org/jira/browse/GEODE-5538 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > > Since it uses different resources and is it's own repository, testing > geode-examples should be separate from the develop pipeline. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5197) synchronize the adding and removal of cache service profiles while reindexing
[
https://issues.apache.org/jira/browse/GEODE-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun closed GEODE-5197.
--
> synchronize the adding and removal of cache service profiles while reindexing
> -
>
> Key: GEODE-5197
> URL: https://issues.apache.org/jira/browse/GEODE-5197
> Project: Geode
> Issue Type: Sub-task
> Components: lucene
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> As a gemfire developer, while creating a lucene index on the data region the
> addition/verification/[or removal] to the region's cache service profile
> should not be affected by concurrent index creation.
> The below code needs to be synchronized
> {code:java}
> private void createIndexOnExistingRegion(PartitionedRegion region, String
> indexName,
> String regionPath, String[] fields, Analyzer analyzer, Map Analyzer> fieldAnalyzers,
> LuceneSerializer serializer) {
> validateRegionAttributes(region.getAttributes());
> LuceneIndexCreationProfile luceneIndexCreationProfile = new
> LuceneIndexCreationProfile(
> indexName, regionPath, fields, analyzer, fieldAnalyzers, serializer);
> region.addCacheServiceProfile(luceneIndexCreationProfile);
> try {
> validateLuceneIndexProfile(region);
> } catch (Exception e) {
> region.removeCacheServiceProfile(luceneIndexCreationProfile.getId());
> throw new UnsupportedOperationException(
>
> LocalizedStrings.LuceneIndexCreation_INDEX_CANNOT_BE_CREATED_DUE_TO_PROFILE_VIOLATION
> .toString(indexName),
> e);
> }
> String aeqId = LuceneServiceImpl.getUniqueIndexName(indexName,
> regionPath);
> region.updatePRConfigWithNewGatewaySender(aeqId);
> LuceneIndexImpl luceneIndex = beforeDataRegionCreated(indexName,
> regionPath,
> region.getAttributes(), analyzer, fieldAnalyzers, aeqId, serializer,
> fields);
> afterDataRegionCreated(luceneIndex);
> createLuceneIndexOnDataRegion(region, luceneIndex);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5197) synchronize the adding and removal of cache service profiles while reindexing
[
https://issues.apache.org/jira/browse/GEODE-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun resolved GEODE-5197.
Resolution: Fixed
Fix Version/s: 1.7.0
> synchronize the adding and removal of cache service profiles while reindexing
> -
>
> Key: GEODE-5197
> URL: https://issues.apache.org/jira/browse/GEODE-5197
> Project: Geode
> Issue Type: Sub-task
> Components: lucene
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> As a gemfire developer, while creating a lucene index on the data region the
> addition/verification/[or removal] to the region's cache service profile
> should not be affected by concurrent index creation.
> The below code needs to be synchronized
> {code:java}
> private void createIndexOnExistingRegion(PartitionedRegion region, String
> indexName,
> String regionPath, String[] fields, Analyzer analyzer, Map Analyzer> fieldAnalyzers,
> LuceneSerializer serializer) {
> validateRegionAttributes(region.getAttributes());
> LuceneIndexCreationProfile luceneIndexCreationProfile = new
> LuceneIndexCreationProfile(
> indexName, regionPath, fields, analyzer, fieldAnalyzers, serializer);
> region.addCacheServiceProfile(luceneIndexCreationProfile);
> try {
> validateLuceneIndexProfile(region);
> } catch (Exception e) {
> region.removeCacheServiceProfile(luceneIndexCreationProfile.getId());
> throw new UnsupportedOperationException(
>
> LocalizedStrings.LuceneIndexCreation_INDEX_CANNOT_BE_CREATED_DUE_TO_PROFILE_VIOLATION
> .toString(indexName),
> e);
> }
> String aeqId = LuceneServiceImpl.getUniqueIndexName(indexName,
> regionPath);
> region.updatePRConfigWithNewGatewaySender(aeqId);
> LuceneIndexImpl luceneIndex = beforeDataRegionCreated(indexName,
> regionPath,
> region.getAttributes(), analyzer, fieldAnalyzers, aeqId, serializer,
> fields);
> afterDataRegionCreated(luceneIndex);
> createLuceneIndexOnDataRegion(region, luceneIndex);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-1882) Add option to start locator and server in foreground
[
https://issues.apache.org/jira/browse/GEODE-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-1882:
--
Labels: pull-request-available (was: )
> Add option to start locator and server in foreground
>
>
> Key: GEODE-1882
> URL: https://issues.apache.org/jira/browse/GEODE-1882
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Labels: pull-request-available
>
> {{gfsh start server}} and {{gfsh start locator}} commands start the server
> and locator in the background. Since the commands itself returns after
> starting these processes in the background, the container is stopped
> immediately.
> The {{gfsh start server}} and {{gfsh start locator}} need a {{--foreground}}
> option to make sure we get a long running container for geode servers and
> locators.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5535) Upgrade fast-classpath-scanner to 4.x
[ https://issues.apache.org/jira/browse/GEODE-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572557#comment-16572557 ] Jens Deppe commented on GEODE-5535: --- I think version 4.0.4 has a memory leak: https://github.com/classgraph/classgraph/issues/233 > Upgrade fast-classpath-scanner to 4.x > - > > Key: GEODE-5535 > URL: https://issues.apache.org/jira/browse/GEODE-5535 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > > The package has been renamed to 'ClassGraph'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
