[jira] [Resolved] (GEODE-8643) ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep value
[
https://issues.apache.org/jira/browse/GEODE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Gomez resolved GEODE-8643.
--
Fix Version/s: 1.14.0
Resolution: Fixed
> ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep
> value
> ---
>
> Key: GEODE-8643
> URL: https://issues.apache.org/jira/browse/GEODE-8643
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> While investigating GEODE-8642, I noticed this error in the logs:
> {noformat}
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_100> tid=0x8e] Initialization of region
> _B__index#__aRegion.files_100 completed
> [vm0] [info 2020/10/22 03:02:32.271 GMT _B__aRegion_9> tid=0x70] Initialization of region
> _B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_9
> completed
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_58> tid=0x80] Initialization of region
> _B__index#__aRegion.files_58 completed
> [vm0] [info 2020/10/22 03:02:32.280 GMT _B__aRegion_77> tid=0x86] Region
> /__PR/_B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_77
> recovered from the local disk. Old persistent ID:
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335705530 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null, new persistent ID
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335751289 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null
> [vm0] [warn 2020/10/22 03:02:32.277 GMT GatewaySender_AsyncEventQueue_index#_aRegion_7> tid=0x62] An Exception
> occurred. The dispatcher will continue.
> [vm0] java.lang.IllegalArgumentException: timeout value is negative
> [vm0] at java.lang.Thread.sleep(Native Method)
> [vm0] at
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.peek(ParallelGatewaySenderQueue.java:1310)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:499)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1121)
> {noformat}
> I believe it may be related to this change:
> e4328553fb5783e8310833df42e1f17e48dc2ac4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8643) ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep value
[
https://issues.apache.org/jira/browse/GEODE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235241#comment-17235241
]
ASF subversion and git services commented on GEODE-8643:
Commit 475dce8424b4523a814968a2e8c96f1b6c9000b3 in geode's branch
refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=475dce8 ]
GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueu… (#5653)
* GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueue for
negative sleep value
* GEODE-8643: Small corrections after review
> ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep
> value
> ---
>
> Key: GEODE-8643
> URL: https://issues.apache.org/jira/browse/GEODE-8643
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
>
> While investigating GEODE-8642, I noticed this error in the logs:
> {noformat}
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_100> tid=0x8e] Initialization of region
> _B__index#__aRegion.files_100 completed
> [vm0] [info 2020/10/22 03:02:32.271 GMT _B__aRegion_9> tid=0x70] Initialization of region
> _B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_9
> completed
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_58> tid=0x80] Initialization of region
> _B__index#__aRegion.files_58 completed
> [vm0] [info 2020/10/22 03:02:32.280 GMT _B__aRegion_77> tid=0x86] Region
> /__PR/_B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_77
> recovered from the local disk. Old persistent ID:
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335705530 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null, new persistent ID
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335751289 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null
> [vm0] [warn 2020/10/22 03:02:32.277 GMT GatewaySender_AsyncEventQueue_index#_aRegion_7> tid=0x62] An Exception
> occurred. The dispatcher will continue.
> [vm0] java.lang.IllegalArgumentException: timeout value is negative
> [vm0] at java.lang.Thread.sleep(Native Method)
> [vm0] at
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.peek(ParallelGatewaySenderQueue.java:1310)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:499)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1121)
> {noformat}
> I believe it may be related to this change:
> e4328553fb5783e8310833df42e1f17e48dc2ac4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8643) ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep value
[
https://issues.apache.org/jira/browse/GEODE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235242#comment-17235242
]
ASF subversion and git services commented on GEODE-8643:
Commit 475dce8424b4523a814968a2e8c96f1b6c9000b3 in geode's branch
refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=475dce8 ]
GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueu… (#5653)
* GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueue for
negative sleep value
* GEODE-8643: Small corrections after review
> ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep
> value
> ---
>
> Key: GEODE-8643
> URL: https://issues.apache.org/jira/browse/GEODE-8643
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
>
> While investigating GEODE-8642, I noticed this error in the logs:
> {noformat}
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_100> tid=0x8e] Initialization of region
> _B__index#__aRegion.files_100 completed
> [vm0] [info 2020/10/22 03:02:32.271 GMT _B__aRegion_9> tid=0x70] Initialization of region
> _B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_9
> completed
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_58> tid=0x80] Initialization of region
> _B__index#__aRegion.files_58 completed
> [vm0] [info 2020/10/22 03:02:32.280 GMT _B__aRegion_77> tid=0x86] Region
> /__PR/_B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_77
> recovered from the local disk. Old persistent ID:
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335705530 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null, new persistent ID
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335751289 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null
> [vm0] [warn 2020/10/22 03:02:32.277 GMT GatewaySender_AsyncEventQueue_index#_aRegion_7> tid=0x62] An Exception
> occurred. The dispatcher will continue.
> [vm0] java.lang.IllegalArgumentException: timeout value is negative
> [vm0] at java.lang.Thread.sleep(Native Method)
> [vm0] at
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.peek(ParallelGatewaySenderQueue.java:1310)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:499)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1121)
> {noformat}
> I believe it may be related to this change:
> e4328553fb5783e8310833df42e1f17e48dc2ac4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8643) ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep value
[
https://issues.apache.org/jira/browse/GEODE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235243#comment-17235243
]
ASF subversion and git services commented on GEODE-8643:
Commit 475dce8424b4523a814968a2e8c96f1b6c9000b3 in geode's branch
refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=475dce8 ]
GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueu… (#5653)
* GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueue for
negative sleep value
* GEODE-8643: Small corrections after review
> ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep
> value
> ---
>
> Key: GEODE-8643
> URL: https://issues.apache.org/jira/browse/GEODE-8643
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
>
> While investigating GEODE-8642, I noticed this error in the logs:
> {noformat}
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_100> tid=0x8e] Initialization of region
> _B__index#__aRegion.files_100 completed
> [vm0] [info 2020/10/22 03:02:32.271 GMT _B__aRegion_9> tid=0x70] Initialization of region
> _B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_9
> completed
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_58> tid=0x80] Initialization of region
> _B__index#__aRegion.files_58 completed
> [vm0] [info 2020/10/22 03:02:32.280 GMT _B__aRegion_77> tid=0x86] Region
> /__PR/_B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_77
> recovered from the local disk. Old persistent ID:
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335705530 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null, new persistent ID
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335751289 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null
> [vm0] [warn 2020/10/22 03:02:32.277 GMT GatewaySender_AsyncEventQueue_index#_aRegion_7> tid=0x62] An Exception
> occurred. The dispatcher will continue.
> [vm0] java.lang.IllegalArgumentException: timeout value is negative
> [vm0] at java.lang.Thread.sleep(Native Method)
> [vm0] at
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.peek(ParallelGatewaySenderQueue.java:1310)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:499)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1121)
> {noformat}
> I believe it may be related to this change:
> e4328553fb5783e8310833df42e1f17e48dc2ac4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8643) ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep value
[
https://issues.apache.org/jira/browse/GEODE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235238#comment-17235238
]
ASF subversion and git services commented on GEODE-8643:
Commit 475dce8424b4523a814968a2e8c96f1b6c9000b3 in geode's branch
refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=475dce8 ]
GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueu… (#5653)
* GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueue for
negative sleep value
* GEODE-8643: Small corrections after review
> ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep
> value
> ---
>
> Key: GEODE-8643
> URL: https://issues.apache.org/jira/browse/GEODE-8643
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
>
> While investigating GEODE-8642, I noticed this error in the logs:
> {noformat}
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_100> tid=0x8e] Initialization of region
> _B__index#__aRegion.files_100 completed
> [vm0] [info 2020/10/22 03:02:32.271 GMT _B__aRegion_9> tid=0x70] Initialization of region
> _B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_9
> completed
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_58> tid=0x80] Initialization of region
> _B__index#__aRegion.files_58 completed
> [vm0] [info 2020/10/22 03:02:32.280 GMT _B__aRegion_77> tid=0x86] Region
> /__PR/_B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_77
> recovered from the local disk. Old persistent ID:
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335705530 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null, new persistent ID
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335751289 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null
> [vm0] [warn 2020/10/22 03:02:32.277 GMT GatewaySender_AsyncEventQueue_index#_aRegion_7> tid=0x62] An Exception
> occurred. The dispatcher will continue.
> [vm0] java.lang.IllegalArgumentException: timeout value is negative
> [vm0] at java.lang.Thread.sleep(Native Method)
> [vm0] at
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.peek(ParallelGatewaySenderQueue.java:1310)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:499)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1121)
> {noformat}
> I believe it may be related to this change:
> e4328553fb5783e8310833df42e1f17e48dc2ac4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8643) ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep value
[
https://issues.apache.org/jira/browse/GEODE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235240#comment-17235240
]
ASF subversion and git services commented on GEODE-8643:
Commit 475dce8424b4523a814968a2e8c96f1b6c9000b3 in geode's branch
refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=475dce8 ]
GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueu… (#5653)
* GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueue for
negative sleep value
* GEODE-8643: Small corrections after review
> ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep
> value
> ---
>
> Key: GEODE-8643
> URL: https://issues.apache.org/jira/browse/GEODE-8643
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
>
> While investigating GEODE-8642, I noticed this error in the logs:
> {noformat}
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_100> tid=0x8e] Initialization of region
> _B__index#__aRegion.files_100 completed
> [vm0] [info 2020/10/22 03:02:32.271 GMT _B__aRegion_9> tid=0x70] Initialization of region
> _B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_9
> completed
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_58> tid=0x80] Initialization of region
> _B__index#__aRegion.files_58 completed
> [vm0] [info 2020/10/22 03:02:32.280 GMT _B__aRegion_77> tid=0x86] Region
> /__PR/_B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_77
> recovered from the local disk. Old persistent ID:
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335705530 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null, new persistent ID
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335751289 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null
> [vm0] [warn 2020/10/22 03:02:32.277 GMT GatewaySender_AsyncEventQueue_index#_aRegion_7> tid=0x62] An Exception
> occurred. The dispatcher will continue.
> [vm0] java.lang.IllegalArgumentException: timeout value is negative
> [vm0] at java.lang.Thread.sleep(Native Method)
> [vm0] at
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.peek(ParallelGatewaySenderQueue.java:1310)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:499)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1121)
> {noformat}
> I believe it may be related to this change:
> e4328553fb5783e8310833df42e1f17e48dc2ac4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8643) ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep value
[
https://issues.apache.org/jira/browse/GEODE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235239#comment-17235239
]
ASF subversion and git services commented on GEODE-8643:
Commit 475dce8424b4523a814968a2e8c96f1b6c9000b3 in geode's branch
refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=475dce8 ]
GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueu… (#5653)
* GEODE-8643: Fix IllegalArgumentException in ParallelGatewaySenderQueue for
negative sleep value
* GEODE-8643: Small corrections after review
> ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep
> value
> ---
>
> Key: GEODE-8643
> URL: https://issues.apache.org/jira/browse/GEODE-8643
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
>
> While investigating GEODE-8642, I noticed this error in the logs:
> {noformat}
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_100> tid=0x8e] Initialization of region
> _B__index#__aRegion.files_100 completed
> [vm0] [info 2020/10/22 03:02:32.271 GMT _B__aRegion_9> tid=0x70] Initialization of region
> _B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_9
> completed
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_58> tid=0x80] Initialization of region
> _B__index#__aRegion.files_58 completed
> [vm0] [info 2020/10/22 03:02:32.280 GMT _B__aRegion_77> tid=0x86] Region
> /__PR/_B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_77
> recovered from the local disk. Old persistent ID:
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335705530 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null, new persistent ID
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335751289 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null
> [vm0] [warn 2020/10/22 03:02:32.277 GMT GatewaySender_AsyncEventQueue_index#_aRegion_7> tid=0x62] An Exception
> occurred. The dispatcher will continue.
> [vm0] java.lang.IllegalArgumentException: timeout value is negative
> [vm0] at java.lang.Thread.sleep(Native Method)
> [vm0] at
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.peek(ParallelGatewaySenderQueue.java:1310)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:499)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1121)
> {noformat}
> I believe it may be related to this change:
> e4328553fb5783e8310833df42e1f17e48dc2ac4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8643) ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep value
[
https://issues.apache.org/jira/browse/GEODE-8643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235237#comment-17235237
]
ASF GitHub Bot commented on GEODE-8643:
---
mkevo merged pull request #5653:
URL: https://github.com/apache/geode/pull/5653
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> ParallelGatewaySenderQueue throws IllegalArgumentException for negative sleep
> value
> ---
>
> Key: GEODE-8643
> URL: https://issues.apache.org/jira/browse/GEODE-8643
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Jens Deppe
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
>
> While investigating GEODE-8642, I noticed this error in the logs:
> {noformat}
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_100> tid=0x8e] Initialization of region
> _B__index#__aRegion.files_100 completed
> [vm0] [info 2020/10/22 03:02:32.271 GMT _B__aRegion_9> tid=0x70] Initialization of region
> _B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_9
> completed
> [vm0] [info 2020/10/22 03:02:32.278 GMT _B__aRegion_58> tid=0x80] Initialization of region
> _B__index#__aRegion.files_58 completed
> [vm0] [info 2020/10/22 03:02:32.280 GMT _B__aRegion_77> tid=0x86] Region
> /__PR/_B__AsyncEventQueue__index#__aRegion__PARALLEL__GATEWAY__SENDER__QUEUE_77
> recovered from the local disk. Old persistent ID:
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335705530 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null, new persistent ID
> /172.17.0.10:/home/geode/geode/geode-lucene/build/upgradeTest5/LuceneSearchWithRollingUpgradeTestBase/diskStoreVM_0
> created at timestamp 1603335751289 version 0 diskStoreId
> 658975c5f23b479f-af5311e17567ca78 name null
> [vm0] [warn 2020/10/22 03:02:32.277 GMT GatewaySender_AsyncEventQueue_index#_aRegion_7> tid=0x62] An Exception
> occurred. The dispatcher will continue.
> [vm0] java.lang.IllegalArgumentException: timeout value is negative
> [vm0] at java.lang.Thread.sleep(Native Method)
> [vm0] at
> org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.peek(ParallelGatewaySenderQueue.java:1310)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:499)
> [vm0] at
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1121)
> {noformat}
> I believe it may be related to this change:
> e4328553fb5783e8310833df42e1f17e48dc2ac4
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8656) Ping not sent to the right gateway receiver endpoint when several receivers have the same hostname-for-senders value
[
https://issues.apache.org/jira/browse/GEODE-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235215#comment-17235215
]
ASF GitHub Bot commented on GEODE-8656:
---
albertogpz commented on a change in pull request #5670:
URL: https://github.com/apache/geode/pull/5670#discussion_r526639463
##
File path:
geode-assembly/src/acceptanceTest/java/org/apache/geode/cache/wan/SeveralGatewayReceiversWithSamePortAndHostnameForSenders.java
##
@@ -0,0 +1,260 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+package org.apache.geode.cache.wan;
+
+import static
com.palantir.docker.compose.execution.DockerComposeExecArgument.arguments;
+import static
com.palantir.docker.compose.execution.DockerComposeExecOption.options;
+import static org.apache.geode.cache.Region.SEPARATOR;
+import static
org.apache.geode.distributed.ConfigurationProperties.DISTRIBUTED_SYSTEM_ID;
+import static org.apache.geode.distributed.ConfigurationProperties.LOCATORS;
+import static
org.apache.geode.distributed.ConfigurationProperties.REMOTE_LOCATORS;
+import static org.junit.Assert.assertEquals;
+import static org.junit.Assert.assertNotNull;
+
+import java.io.File;
+import java.net.URL;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.Properties;
+import java.util.StringTokenizer;
+
+import com.palantir.docker.compose.DockerComposeRule;
+import org.junit.BeforeClass;
+import org.junit.ClassRule;
+import org.junit.Rule;
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.Cache;
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.cache.PartitionAttributesFactory;
+import org.apache.geode.cache.Region;
+import org.apache.geode.cache.RegionFactory;
+import org.apache.geode.cache.RegionShortcut;
+import org.apache.geode.cache.persistence.PartitionOfflineException;
+import org.apache.geode.client.sni.NotOnWindowsDockerRule;
+import org.apache.geode.distributed.Locator;
+import org.apache.geode.internal.cache.ForceReattemptException;
+import org.apache.geode.internal.cache.PoolStats;
+import org.apache.geode.internal.cache.wan.AbstractGatewaySender;
+import org.apache.geode.internal.cache.wan.InternalGatewaySenderFactory;
+import org.apache.geode.test.dunit.IgnoredException;
+import org.apache.geode.test.dunit.VM;
+import org.apache.geode.test.dunit.rules.DistributedRule;
+import org.apache.geode.test.junit.categories.WanTest;
+
+
+/**
+ * These tests use two Geode sites:
+ *
+ * - One site (the remote one) consisting of a 2-server, 1-locator Geode
cluster.
+ * The servers host a partition region (region-wan) and have gateway senders
to receive events
+ * from the other site with the same value for hostname-for-senders and
listening on the
+ * same port (2324).
+ * The servers and locator run each inside a Docker container and are not
route-able
+ * from the host (where this JUnit test is running).
+ * Another Docker container is running the HAProxy image and it's set up as a
TCP load balancer.
+ * The other site connects to the locator and to the gateway receivers via the
+ * TCP load balancer that forwards traffic directed to the 20334 port to the
locator and
+ * traffic directed to the 2324 port to the receivers in a round robin fashion.
+ *
+ * - Another site consisting of a 1-server, 1-locator Geode cluster.
+ * The server hosts a partition region (region-wan) and has a parallel gateway
receiver
+ * to send events to the remote site.
+ *
+ * The aim of the tests is verify that when several gateway receivers in a
remote site
+ * share the same port and hostname-for-senders, the pings sent from the
gateway senders
+ * reach the right gateway receiver and not just any of the receivers. Failure
to do this
+ * may result in the closing of connections by a gateway receiver for not
having
+ * received the ping in time.
+ */
+@Category({WanTest.class})
+public class SeveralGatewayReceiversWithSamePortAndHostnameForSenders {
+
+ private static final int NUM_SERVERS = 2;
+
+ private static Cache cache;
+
+ private static final URL DOCKER_COMPOSE_PATH =
+
[jira] [Updated] (GEODE-8683) maximum-time-between-pings parameter in GatewayReceiver creation does not have any effect
[ https://issues.apache.org/jira/browse/GEODE-8683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Gomez updated GEODE-8683: - Description: The maximum-time-between-pings parameter than can be set at gateway receiver creation has no effect, i.e. the value used as maximum time between pings for gateway sender connections to the gateway receiver is either the default value (6) or the one set on the server where the receiver is running. The reason is that the ClientHealthMonitor is a server-side singleton that monitors the health of all clients. The value set for this parameter in the ClientHealthMonitor is first set when the server is started and the first Acceptor is created. was: The maximum-time-between-pings parameter than can be set at gateway sender creation has no effect, i.e. the value used as maximum time between pings for gateway sender connections to the gateway receiver is either the default value (6) or the one set on the server where the receiver is running. The reason is that the ClientHealthMonitor is a server-side singleton that monitors the health of all clients. The value set for this parameter in the ClientHealthMonitor is first set when the server is started and the first Acceptor is created. > maximum-time-between-pings parameter in GatewayReceiver creation does not > have any effect > - > > Key: GEODE-8683 > URL: https://issues.apache.org/jira/browse/GEODE-8683 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > The maximum-time-between-pings parameter than can be set at gateway receiver > creation has no effect, i.e. the value used as maximum time between pings for > gateway sender connections to the gateway receiver is either the default > value (6) or the one set on the server where the receiver is running. > The reason is that the ClientHealthMonitor is a server-side singleton that > monitors the health of all clients. The value set for this parameter in the > ClientHealthMonitor is first set when the server is started and the first > Acceptor is created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-2896) CI Failure: ClassCastException in GMSMembershipManagerJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235189#comment-17235189
]
Geode Integration commented on GEODE-2896:
--
Seen on support/1.13 in [UnitTestOpenJDK8
#39|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/UnitTestOpenJDK8/builds/39]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.1-build.0403/test-results/test/1605747073/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.1-build.0403/test-artifacts/1605747073/unittestfiles-OpenJDK8-1.13.1-build.0403.tgz].
> CI Failure: ClassCastException in GMSMembershipManagerJUnitTest
>
>
> Key: GEODE-2896
> URL: https://issues.apache.org/jira/browse/GEODE-2896
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Nabarun Nag
>Priority: Major
> Labels: ci
>
> {noformat}
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureDueToForcedDisconnect FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureDueToForcedDisconnect(GMSMembershipManagerJUnitTest.java:343)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testStartupEvents FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testStartupEvents(GMSMembershipManagerJUnitTest.java:219)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testSendToEmptyListIsRejected FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testSendToEmptyListIsRejected(GMSMembershipManagerJUnitTest.java:177)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendAllRecipients FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendAllRecipients(GMSMembershipManagerJUnitTest.java:331)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSend FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSend(GMSMembershipManagerJUnitTest.java:281)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureToOneRecipient FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureToOneRecipient(GMSMembershipManagerJUnitTest.java:294)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureToAll FAILED
> java.lang.ClassCastException:
>
[jira] [Reopened] (GEODE-2896) CI Failure: ClassCastException in GMSMembershipManagerJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols reopened GEODE-2896:
-
This is occurring again on support/1.13 since the image used to run the tests
changed from
[ubuntu-minimal-1804-bionic-v20201014|https://www.googleapis.com/compute/v1/projects/ubuntu-os-cloud/global/images/ubuntu-minimal-1804-bionic-v20201014]
to
[ubuntu-minimal-1804-bionic-v20201116|https://www.googleapis.com/compute/v1/projects/ubuntu-os-cloud/global/images/ubuntu-minimal-1804-bionic-v20201116]
> CI Failure: ClassCastException in GMSMembershipManagerJUnitTest
>
>
> Key: GEODE-2896
> URL: https://issues.apache.org/jira/browse/GEODE-2896
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Nabarun Nag
>Priority: Major
> Labels: ci
>
> {noformat}
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureDueToForcedDisconnect FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureDueToForcedDisconnect(GMSMembershipManagerJUnitTest.java:343)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testStartupEvents FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testStartupEvents(GMSMembershipManagerJUnitTest.java:219)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testSendToEmptyListIsRejected FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testSendToEmptyListIsRejected(GMSMembershipManagerJUnitTest.java:177)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendAllRecipients FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendAllRecipients(GMSMembershipManagerJUnitTest.java:331)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSend FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSend(GMSMembershipManagerJUnitTest.java:281)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureToOneRecipient FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureToOneRecipient(GMSMembershipManagerJUnitTest.java:294)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureToAll FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
>
[jira] [Commented] (GEODE-2896) CI Failure: ClassCastException in GMSMembershipManagerJUnitTest
[
https://issues.apache.org/jira/browse/GEODE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235183#comment-17235183
]
Geode Integration commented on GEODE-2896:
--
Seen on support/1.13 in [UnitTestOpenJDK8
#36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/UnitTestOpenJDK8/builds/36]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.2-build.0406/test-results/test/1605722821/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.2-build.0406/test-artifacts/1605722821/unittestfiles-OpenJDK8-1.13.2-build.0406.tgz].
> CI Failure: ClassCastException in GMSMembershipManagerJUnitTest
>
>
> Key: GEODE-2896
> URL: https://issues.apache.org/jira/browse/GEODE-2896
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Nabarun Nag
>Priority: Major
> Labels: ci
>
> {noformat}
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureDueToForcedDisconnect FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureDueToForcedDisconnect(GMSMembershipManagerJUnitTest.java:343)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testStartupEvents FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testStartupEvents(GMSMembershipManagerJUnitTest.java:219)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testSendToEmptyListIsRejected FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testSendToEmptyListIsRejected(GMSMembershipManagerJUnitTest.java:177)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendAllRecipients FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendAllRecipients(GMSMembershipManagerJUnitTest.java:331)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSend FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSend(GMSMembershipManagerJUnitTest.java:281)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureToOneRecipient FAILED
> java.lang.ClassCastException:
> org.apache.geode.distributed.internal.LonerDistributionManager cannot be cast
> to org.apache.geode.distributed.internal.DistributionManager
> at
> org.apache.geode.distributed.internal.HighPriorityAckedMessage.(HighPriorityAckedMessage.java:68)
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest.testDirectChannelSendFailureToOneRecipient(GMSMembershipManagerJUnitTest.java:294)
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManagerJUnitTest
> > testDirectChannelSendFailureToAll FAILED
> java.lang.ClassCastException:
>
[jira] [Commented] (GEODE-8664) JGroups exception is not propagated
[
https://issues.apache.org/jira/browse/GEODE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235121#comment-17235121
]
ASF GitHub Bot commented on GEODE-8664:
---
kohlmu-pivotal edited a comment on pull request #5751:
URL: https://github.com/apache/geode/pull/5751#issuecomment-730081544
> I think this violates the intent that `membership` exceptions should not
escape the module
@echobravopapa I love the idea that modules/components don't leak anything
outside of itself. But if looking at the `DistribtionImpl` the exceptions that
you don't want to leak "out", have already leaked into geode-core. So, not sure
how we are trying to stop the leaking.
It is not like there is even a violation of public -> internal package
namespaces. The usage are in 2 internal packages.
If the intent that exceptions do not escape the module, then the current
implementation needs to be addressed. As the current implementation is a sieve.
The exceptions have already leaked out!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> JGroups exception is not propagated
> ---
>
> Key: GEODE-8664
> URL: https://issues.apache.org/jira/browse/GEODE-8664
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Affects Versions: 1.12.0, 1.13.0
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Minor
> Labels: pull-request-available
> Attachments: GEODE-8664.patch
>
>
> *AS A* geode contributor
> *I WANT* exceptions thrown in DistributionImpl.start to be propagated
> *SO THAT* more information is provided while tackling issues.
>
>
> *Additional information:*
> After looking at an issue while starting a locator having to do with
> JGroupMessenger I noticed that exceptions from Membership.start are not
> correctly propagated in DistributionImpl.start method.
> To ilustrate the problem I attach below the reported exception while starting
> the locator:
>
> {noformat}
> locator is exiting due to an exception
> org.apache.geode.GemFireConfigException: unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:184)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:779)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3033)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:743)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:388)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:716)
> at org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:623)
> at
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:217){noformat}
>
> Thing is with that kind of information there's no way to know why the problem
> is happening, so the idea would be to propagate the exceptions, so it looks
> more like this:
> {noformat}
> locator is exiting due to an exception
> org.apache.geode.SystemConnectException: unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:186)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
> at
>
[jira] [Commented] (GEODE-8664) JGroups exception is not propagated
[
https://issues.apache.org/jira/browse/GEODE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235119#comment-17235119
]
ASF GitHub Bot commented on GEODE-8664:
---
kohlmu-pivotal commented on pull request #5751:
URL: https://github.com/apache/geode/pull/5751#issuecomment-730082165
> I think this violates the intent that `membership` exceptions should not
escape the module
@echobravopapa if the intent is not for the exceptions leaking out, could
you possibly suggest an alternate implementations on how to resolve the issue
that @gaussianrecurrence has raised?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> JGroups exception is not propagated
> ---
>
> Key: GEODE-8664
> URL: https://issues.apache.org/jira/browse/GEODE-8664
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Affects Versions: 1.12.0, 1.13.0
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Minor
> Labels: pull-request-available
> Attachments: GEODE-8664.patch
>
>
> *AS A* geode contributor
> *I WANT* exceptions thrown in DistributionImpl.start to be propagated
> *SO THAT* more information is provided while tackling issues.
>
>
> *Additional information:*
> After looking at an issue while starting a locator having to do with
> JGroupMessenger I noticed that exceptions from Membership.start are not
> correctly propagated in DistributionImpl.start method.
> To ilustrate the problem I attach below the reported exception while starting
> the locator:
>
> {noformat}
> locator is exiting due to an exception
> org.apache.geode.GemFireConfigException: unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:184)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:779)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3033)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:743)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:388)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:716)
> at org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:623)
> at
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:217){noformat}
>
> Thing is with that kind of information there's no way to know why the problem
> is happening, so the idea would be to propagate the exceptions, so it looks
> more like this:
> {noformat}
> locator is exiting due to an exception
> org.apache.geode.SystemConnectException: unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:186)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:779)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290)
> at
>
[jira] [Commented] (GEODE-8664) JGroups exception is not propagated
[
https://issues.apache.org/jira/browse/GEODE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235120#comment-17235120
]
ASF GitHub Bot commented on GEODE-8664:
---
kohlmu-pivotal edited a comment on pull request #5751:
URL: https://github.com/apache/geode/pull/5751#issuecomment-730082165
> I think this violates the intent that `membership` exceptions should not
escape the module
@echobravopapa if the intent is not for the exceptions leaking out, could
you possibly suggest alternate implementations on how to resolve the issue that
@gaussianrecurrence has raised?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> JGroups exception is not propagated
> ---
>
> Key: GEODE-8664
> URL: https://issues.apache.org/jira/browse/GEODE-8664
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Affects Versions: 1.12.0, 1.13.0
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Minor
> Labels: pull-request-available
> Attachments: GEODE-8664.patch
>
>
> *AS A* geode contributor
> *I WANT* exceptions thrown in DistributionImpl.start to be propagated
> *SO THAT* more information is provided while tackling issues.
>
>
> *Additional information:*
> After looking at an issue while starting a locator having to do with
> JGroupMessenger I noticed that exceptions from Membership.start are not
> correctly propagated in DistributionImpl.start method.
> To ilustrate the problem I attach below the reported exception while starting
> the locator:
>
> {noformat}
> locator is exiting due to an exception
> org.apache.geode.GemFireConfigException: unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:184)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:779)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3033)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:743)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:388)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:716)
> at org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:623)
> at
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:217){noformat}
>
> Thing is with that kind of information there's no way to know why the problem
> is happening, so the idea would be to propagate the exceptions, so it looks
> more like this:
> {noformat}
> locator is exiting due to an exception
> org.apache.geode.SystemConnectException: unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:186)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:779)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290)
> at
[jira] [Commented] (GEODE-8664) JGroups exception is not propagated
[
https://issues.apache.org/jira/browse/GEODE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235117#comment-17235117
]
ASF GitHub Bot commented on GEODE-8664:
---
kohlmu-pivotal commented on pull request #5751:
URL: https://github.com/apache/geode/pull/5751#issuecomment-730081544
> I think this violates the intent that `membership` exceptions should not
escape the module
@echobravopapa I love the idea that modules/components don't leak anything
outside of itself. But if looking at the `DistribtionImpl` the exceptions that
you don't want to leak "out", have already leaked into geode-core. So, not sure
how we are trying to stop the leaking.
It is not like there is even a violation of public -> internal package. The
usage are in 2 internal classes.
If the intent that exceptions do not escape the module, then the current
implementation needs to be addressed. As the current implementation is a sieve.
The exceptions have already leaked out!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> JGroups exception is not propagated
> ---
>
> Key: GEODE-8664
> URL: https://issues.apache.org/jira/browse/GEODE-8664
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
>Affects Versions: 1.12.0, 1.13.0
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Minor
> Labels: pull-request-available
> Attachments: GEODE-8664.patch
>
>
> *AS A* geode contributor
> *I WANT* exceptions thrown in DistributionImpl.start to be propagated
> *SO THAT* more information is provided while tackling issues.
>
>
> *Additional information:*
> After looking at an issue while starting a locator having to do with
> JGroupMessenger I noticed that exceptions from Membership.start are not
> correctly propagated in DistributionImpl.start method.
> To ilustrate the problem I attach below the reported exception while starting
> the locator:
>
> {noformat}
> locator is exiting due to an exception
> org.apache.geode.GemFireConfigException: unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:184)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:779)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3033)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:743)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:388)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:716)
> at org.apache.geode.distributed.LocatorLauncher.run(LocatorLauncher.java:623)
> at
> org.apache.geode.distributed.LocatorLauncher.main(LocatorLauncher.java:217){noformat}
>
> Thing is with that kind of information there's no way to know why the problem
> is happening, so the idea would be to propagate the exceptions, so it looks
> more like this:
> {noformat}
> locator is exiting due to an exception
> org.apache.geode.SystemConnectException: unable to create jgroups channel
> at
> org.apache.geode.distributed.internal.DistributionImpl.start(DistributionImpl.java:186)
> at
> org.apache.geode.distributed.internal.DistributionImpl.createDistribution(DistributionImpl.java:222)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:464)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:497)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:326)
> at
>
[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies
[ https://issues.apache.org/jira/browse/GEODE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235097#comment-17235097 ] ASF subversion and git services commented on GEODE-2484: Commit 9fdb183e146b0e0ecf5beed5aef87f7673f459fd in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=9fdb183 ] GEODE-2484: Removes ACE_DLL (#591) Replaces with boost::dll. > Remove ACE from native client dependencies > -- > > Key: GEODE-2484 > URL: https://issues.apache.org/jira/browse/GEODE-2484 > Project: Geode > Issue Type: Task > Components: native client >Reporter: David Kimura >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 11h 20m > Remaining Estimate: 0h > > Remove ACE from native client dependencies. > Replace ACE usage with C++11 and/or Boost 1.63+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-2484) Remove ACE from native client dependencies
[ https://issues.apache.org/jira/browse/GEODE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235096#comment-17235096 ] ASF GitHub Bot commented on GEODE-2484: --- pivotal-jbarrett merged pull request #591: URL: https://github.com/apache/geode-native/pull/591 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove ACE from native client dependencies > -- > > Key: GEODE-2484 > URL: https://issues.apache.org/jira/browse/GEODE-2484 > Project: Geode > Issue Type: Task > Components: native client >Reporter: David Kimura >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 11h 20m > Remaining Estimate: 0h > > Remove ACE from native client dependencies. > Replace ACE usage with C++11 and/or Boost 1.63+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235063#comment-17235063 ] ASF subversion and git services commented on GEODE-8724: Commit ba85630388e51a7ae7a73529dafa10172ca9d85a in geode-native's branch refs/heads/support/1.13 from Mario Salazar de Torres [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=ba85630 ] GEODE-8724: Fix compilation using docker image (#696) - As latest tag for ubuntu base image was recently change from 18.04 to 20.04 it seems that some libraries version changed, like for example libc++. - As it seems with this new version libc++ headers are either not anymore located within /usr/include/c++/v1 or the symlink is missing. - So in order to solve that a symlink is manually created to ensure clang is able to find libc++ headers. (cherry picked from commit 4e241ffe6f6bda0254f97cdfe18929ce81d04ace) > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235062#comment-17235062 ] ASF subversion and git services commented on GEODE-8724: Commit ba85630388e51a7ae7a73529dafa10172ca9d85a in geode-native's branch refs/heads/support/1.13 from Mario Salazar de Torres [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=ba85630 ] GEODE-8724: Fix compilation using docker image (#696) - As latest tag for ubuntu base image was recently change from 18.04 to 20.04 it seems that some libraries version changed, like for example libc++. - As it seems with this new version libc++ headers are either not anymore located within /usr/include/c++/v1 or the symlink is missing. - So in order to solve that a symlink is manually created to ensure clang is able to find libc++ headers. (cherry picked from commit 4e241ffe6f6bda0254f97cdfe18929ce81d04ace) > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235045#comment-17235045 ] ASF subversion and git services commented on GEODE-8724: Commit c26387e564412e259d154606caf84551a59c361f in geode-native's branch refs/heads/support/1.12 from Mario Salazar de Torres [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=c26387e ] GEODE-8724: Fix compilation using docker image (#696) - As latest tag for ubuntu base image was recently change from 18.04 to 20.04 it seems that some libraries version changed, like for example libc++. - As it seems with this new version libc++ headers are either not anymore located within /usr/include/c++/v1 or the symlink is missing. - So in order to solve that a symlink is manually created to ensure clang is able to find libc++ headers. (cherry picked from commit 4e241ffe6f6bda0254f97cdfe18929ce81d04ace) > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8728) Configure Gradle to run parallel tests in isolation without Docker
[ https://issues.apache.org/jira/browse/GEODE-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Emery updated GEODE-8728: -- Labels: GeodeOperationAPI (was: ) > Configure Gradle to run parallel tests in isolation without Docker > -- > > Key: GEODE-8728 > URL: https://issues.apache.org/jira/browse/GEODE-8728 > Project: Geode > Issue Type: Test > Components: tests >Affects Versions: 1.14.0 >Reporter: Dale Emery >Priority: Major > Labels: GeodeOperationAPI > > For tests to behave well when run in parallel, each must refrain from using > ports and test files that are in use by other tests. > Geode's Gradle build isolates concurrently executing tests by running each > test class in a Docker container. To do this, the build applies an open > source "Gradle Dockerized Test" plugin that is obsolete and appears to be > unmaintained. > This ticket removes the obsolete plugin and replaces it with a small amount > of custom Gradle code and a few minor changes to Geode: > - Configure Gradle to assign each concurrently executing test JVM a unique > working directory and a distinct range of ports. > - Change Geode's "available port" feature to allocate ports only from the > ranges assigned by Gradle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8728) Configure Gradle to run parallel tests in isolation without Docker
[ https://issues.apache.org/jira/browse/GEODE-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Emery reassigned GEODE-8728: - Assignee: Dale Emery > Configure Gradle to run parallel tests in isolation without Docker > -- > > Key: GEODE-8728 > URL: https://issues.apache.org/jira/browse/GEODE-8728 > Project: Geode > Issue Type: Test > Components: tests >Affects Versions: 1.14.0 >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Major > Labels: GeodeOperationAPI > > For tests to behave well when run in parallel, each must refrain from using > ports and test files that are in use by other tests. > Geode's Gradle build isolates concurrently executing tests by running each > test class in a Docker container. To do this, the build applies an open > source "Gradle Dockerized Test" plugin that is obsolete and appears to be > unmaintained. > This ticket removes the obsolete plugin and replaces it with a small amount > of custom Gradle code and a few minor changes to Geode: > - Configure Gradle to assign each concurrently executing test JVM a unique > working directory and a distinct range of ports. > - Change Geode's "available port" feature to allocate ports only from the > ranges assigned by Gradle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8728) Configure Gradle to run parallel tests in isolation without Docker
Dale Emery created GEODE-8728: - Summary: Configure Gradle to run parallel tests in isolation without Docker Key: GEODE-8728 URL: https://issues.apache.org/jira/browse/GEODE-8728 Project: Geode Issue Type: Test Components: tests Affects Versions: 1.14.0 Reporter: Dale Emery For tests to behave well when run in parallel, each must refrain from using ports and test files that are in use by other tests. Geode's Gradle build isolates concurrently executing tests by running each test class in a Docker container. To do this, the build applies an open source "Gradle Dockerized Test" plugin that is obsolete and appears to be unmaintained. This ticket removes the obsolete plugin and replaces it with a small amount of custom Gradle code and a few minor changes to Geode: - Configure Gradle to assign each concurrently executing test JVM a unique working directory and a distinct range of ports. - Change Geode's "available port" feature to allocate ports only from the ranges assigned by Gradle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8727) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated test[from_v1.2.0
[
https://issues.apache.org/jira/browse/GEODE-8727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Ingles updated GEODE-8727:
--
Description:
This test hung in an upgradeTest run. Stack traces show it interacting with a
Locator and making progress over the 15 seconds between traces.
CI webpage:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/589
Artifacts are here:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-artifacts/1605733271/upgradetestfiles-OpenJDK11-1.14.0-build.0500.tgz
Here is the main test thread:
{code:java}
"Test worker" #27 prio=5 os_prio=0 cpu=4900.15ms elapsed=2902.12s
tid=0x7fe70cbd4800 nid=0x1b runnable [0x7fe6d8894000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(java.base@11.0.9.1/Native
Method)
at
java.net.SocketInputStream.socketRead(java.base@11.0.9.1/SocketInputStream.java:115)
at
java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:168)
at
java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:140)
at
java.io.BufferedInputStream.fill(java.base@11.0.9.1/BufferedInputStream.java:252)
at
java.io.BufferedInputStream.read(java.base@11.0.9.1/BufferedInputStream.java:271)
- locked <0xf6487988> (a java.io.BufferedInputStream)
at
java.io.DataInputStream.readByte(java.base@11.0.9.1/DataInputStream.java:270)
at
sun.rmi.transport.StreamRemoteCall.executeCall(java.rmi@11.0.9.1/StreamRemoteCall.java:240)
at
sun.rmi.server.UnicastRef.invoke(java.rmi@11.0.9.1/UnicastRef.java:164)
at
java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:217)
at
java.rmi.server.RemoteObjectInvocationHandler.invoke(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:162)
at com.sun.proxy.$Proxy53.executeMethodOnObject(Unknown Source)
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
at
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrent(LuceneSearchWithRollingUpgradeTestBase.java:347)
at
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrentCreateLuceneIndexAndCreateRegion(LuceneSearchWithRollingUpgradeTestBase.java:359)
at
org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:108)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.9.1/Native
Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.9.1/NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.9.1/DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(java.base@11.0.9.1/Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
{code}
was:
This test hung in an upgradeTest run. Stack traces show it interacting with a
Locator and making progress over the 15 seconds between traces.
Artifacts are here:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-artifacts/1605733271/upgradetestfiles-OpenJDK11-1.14.0-build.0500.tgz
Here is the main test thread:
{code:java}
"Test worker" #27 prio=5 os_prio=0 cpu=4900.15ms elapsed=2902.12s
tid=0x7fe70cbd4800 nid=0x1b runnable [0x7fe6d8894000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(java.base@11.0.9.1/Native
Method)
at
java.net.SocketInputStream.socketRead(java.base@11.0.9.1/SocketInputStream.java:115)
at
java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:168)
at
java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:140)
at
java.io.BufferedInputStream.fill(java.base@11.0.9.1/BufferedInputStream.java:252)
at
java.io.BufferedInputStream.read(java.base@11.0.9.1/BufferedInputStream.java:271)
- locked <0xf6487988> (a java.io.BufferedInputStream)
at
[jira] [Updated] (GEODE-8727) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated test[from_v1.2.0
[
https://issues.apache.org/jira/browse/GEODE-8727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Ingles updated GEODE-8727:
--
Affects Version/s: 1.14.0
> CI Failure:
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> test[from_v1.2.0
>
>
> Key: GEODE-8727
> URL: https://issues.apache.org/jira/browse/GEODE-8727
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.14.0
>Reporter: Raymond Ingles
>Priority: Major
>
> This test hung in an upgradeTest run. Stack traces show it interacting with
> a Locator and making progress over the 15 seconds between traces.
> Artifacts are here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-artifacts/1605733271/upgradetestfiles-OpenJDK11-1.14.0-build.0500.tgz
> Here is the main test thread:
> {code:java}
> "Test worker" #27 prio=5 os_prio=0 cpu=4900.15ms elapsed=2902.12s
> tid=0x7fe70cbd4800 nid=0x1b runnable [0x7fe6d8894000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(java.base@11.0.9.1/Native
> Method)
> at
> java.net.SocketInputStream.socketRead(java.base@11.0.9.1/SocketInputStream.java:115)
> at
> java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:168)
> at
> java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:140)
> at
> java.io.BufferedInputStream.fill(java.base@11.0.9.1/BufferedInputStream.java:252)
> at
> java.io.BufferedInputStream.read(java.base@11.0.9.1/BufferedInputStream.java:271)
> - locked <0xf6487988> (a java.io.BufferedInputStream)
> at
> java.io.DataInputStream.readByte(java.base@11.0.9.1/DataInputStream.java:270)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(java.rmi@11.0.9.1/StreamRemoteCall.java:240)
> at
> sun.rmi.server.UnicastRef.invoke(java.rmi@11.0.9.1/UnicastRef.java:164)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:217)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invoke(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:162)
> at com.sun.proxy.$Proxy53.executeMethodOnObject(Unknown Source)
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrent(LuceneSearchWithRollingUpgradeTestBase.java:347)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrentCreateLuceneIndexAndCreateRegion(LuceneSearchWithRollingUpgradeTestBase.java:359)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:108)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.9.1/Native
> Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.9.1/NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.9.1/DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(java.base@11.0.9.1/Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7732) CI Failure: JMXMBeanReconnectDUnitTest.serverMXBeansOnLocatorAreRestoredAfterCrashedServerReturns failed
[
https://issues.apache.org/jira/browse/GEODE-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235036#comment-17235036
]
Geode Integration commented on GEODE-7732:
--
Seen in [DistributedTestOpenJDK11
#606|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/606]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-results/distributedTest/1605737110/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-artifacts/1605737110/distributedtestfiles-OpenJDK11-1.14.0-build.0500.tgz].
> CI Failure:
> JMXMBeanReconnectDUnitTest.serverMXBeansOnLocatorAreRestoredAfterCrashedServerReturns
> failed
>
>
> Key: GEODE-7732
> URL: https://issues.apache.org/jira/browse/GEODE-7732
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.12.0
>Reporter: Eric Shu
>Assignee: Kirk Lund
>Priority: Major
> Labels: flaky
> Fix For: 1.13.0
>
>
> This failed @
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1487
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.management.JMXMBeanReconnectDUnitTest$$Lambda$209/0x000840bb5c40.call
> in VM 2 running on Host e8b6d1c09a6c with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.management.JMXMBeanReconnectDUnitTest.setUp(JMXMBeanReconnectDUnitTest.java:177)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:59)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:59)
> at
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
>
[jira] [Commented] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235027#comment-17235027 ] ASF GitHub Bot commented on GEODE-8724: --- gaussianrecurrence commented on pull request #696: URL: https://github.com/apache/geode-native/pull/696#issuecomment-729988739 Still I think @dickcav or someone else needs to re-upload the image to docker hub as currently both latest and 1.13.1 tags are failing to compile. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8727) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated test[from_v1.2.0
[
https://issues.apache.org/jira/browse/GEODE-8727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Ingles updated GEODE-8727:
--
Summary: CI Failure:
RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
test[from_v1.2.0 (was:
RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
test[from_v1.2.0)
> CI Failure:
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> test[from_v1.2.0
>
>
> Key: GEODE-8727
> URL: https://issues.apache.org/jira/browse/GEODE-8727
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: Raymond Ingles
>Priority: Major
>
> This test hung in an upgradeTest run. Stack traces show it interacting with
> a Locator and making progress over the 15 seconds between traces.
> Artifacts are here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-artifacts/1605733271/upgradetestfiles-OpenJDK11-1.14.0-build.0500.tgz
> Here is the main test thread:
> {code:java}
> "Test worker" #27 prio=5 os_prio=0 cpu=4900.15ms elapsed=2902.12s
> tid=0x7fe70cbd4800 nid=0x1b runnable [0x7fe6d8894000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(java.base@11.0.9.1/Native
> Method)
> at
> java.net.SocketInputStream.socketRead(java.base@11.0.9.1/SocketInputStream.java:115)
> at
> java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:168)
> at
> java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:140)
> at
> java.io.BufferedInputStream.fill(java.base@11.0.9.1/BufferedInputStream.java:252)
> at
> java.io.BufferedInputStream.read(java.base@11.0.9.1/BufferedInputStream.java:271)
> - locked <0xf6487988> (a java.io.BufferedInputStream)
> at
> java.io.DataInputStream.readByte(java.base@11.0.9.1/DataInputStream.java:270)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(java.rmi@11.0.9.1/StreamRemoteCall.java:240)
> at
> sun.rmi.server.UnicastRef.invoke(java.rmi@11.0.9.1/UnicastRef.java:164)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:217)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invoke(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:162)
> at com.sun.proxy.$Proxy53.executeMethodOnObject(Unknown Source)
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrent(LuceneSearchWithRollingUpgradeTestBase.java:347)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrentCreateLuceneIndexAndCreateRegion(LuceneSearchWithRollingUpgradeTestBase.java:359)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:108)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.9.1/Native
> Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.9.1/NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.9.1/DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(java.base@11.0.9.1/Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8727) CI Failure: RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated test[from_v1.2.0
[
https://issues.apache.org/jira/browse/GEODE-8727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235026#comment-17235026
]
Geode Integration commented on GEODE-8727:
--
Seen in [UpgradeTestOpenJDK11
#589|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/589]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-results/upgradeTest/1605733271/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-artifacts/1605733271/upgradetestfiles-OpenJDK11-1.14.0-build.0500.tgz].
> CI Failure:
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> test[from_v1.2.0
>
>
> Key: GEODE-8727
> URL: https://issues.apache.org/jira/browse/GEODE-8727
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Reporter: Raymond Ingles
>Priority: Major
>
> This test hung in an upgradeTest run. Stack traces show it interacting with
> a Locator and making progress over the 15 seconds between traces.
> Artifacts are here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-artifacts/1605733271/upgradetestfiles-OpenJDK11-1.14.0-build.0500.tgz
> Here is the main test thread:
> {code:java}
> "Test worker" #27 prio=5 os_prio=0 cpu=4900.15ms elapsed=2902.12s
> tid=0x7fe70cbd4800 nid=0x1b runnable [0x7fe6d8894000]
>java.lang.Thread.State: RUNNABLE
> at java.net.SocketInputStream.socketRead0(java.base@11.0.9.1/Native
> Method)
> at
> java.net.SocketInputStream.socketRead(java.base@11.0.9.1/SocketInputStream.java:115)
> at
> java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:168)
> at
> java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:140)
> at
> java.io.BufferedInputStream.fill(java.base@11.0.9.1/BufferedInputStream.java:252)
> at
> java.io.BufferedInputStream.read(java.base@11.0.9.1/BufferedInputStream.java:271)
> - locked <0xf6487988> (a java.io.BufferedInputStream)
> at
> java.io.DataInputStream.readByte(java.base@11.0.9.1/DataInputStream.java:270)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(java.rmi@11.0.9.1/StreamRemoteCall.java:240)
> at
> sun.rmi.server.UnicastRef.invoke(java.rmi@11.0.9.1/UnicastRef.java:164)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:217)
> at
> java.rmi.server.RemoteObjectInvocationHandler.invoke(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:162)
> at com.sun.proxy.$Proxy53.executeMethodOnObject(Unknown Source)
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrent(LuceneSearchWithRollingUpgradeTestBase.java:347)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrentCreateLuceneIndexAndCreateRegion(LuceneSearchWithRollingUpgradeTestBase.java:359)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:108)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.9.1/Native
> Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.9.1/NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.9.1/DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(java.base@11.0.9.1/Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-8727) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated test[from_v1.2.0
Raymond Ingles created GEODE-8727:
-
Summary:
RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
test[from_v1.2.0
Key: GEODE-8727
URL: https://issues.apache.org/jira/browse/GEODE-8727
Project: Geode
Issue Type: Bug
Components: lucene
Reporter: Raymond Ingles
This test hung in an upgradeTest run. Stack traces show it interacting with a
Locator and making progress over the 15 seconds between traces.
Artifacts are here:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0500/test-artifacts/1605733271/upgradetestfiles-OpenJDK11-1.14.0-build.0500.tgz
Here is the main test thread:
{code:java}
"Test worker" #27 prio=5 os_prio=0 cpu=4900.15ms elapsed=2902.12s
tid=0x7fe70cbd4800 nid=0x1b runnable [0x7fe6d8894000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(java.base@11.0.9.1/Native
Method)
at
java.net.SocketInputStream.socketRead(java.base@11.0.9.1/SocketInputStream.java:115)
at
java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:168)
at
java.net.SocketInputStream.read(java.base@11.0.9.1/SocketInputStream.java:140)
at
java.io.BufferedInputStream.fill(java.base@11.0.9.1/BufferedInputStream.java:252)
at
java.io.BufferedInputStream.read(java.base@11.0.9.1/BufferedInputStream.java:271)
- locked <0xf6487988> (a java.io.BufferedInputStream)
at
java.io.DataInputStream.readByte(java.base@11.0.9.1/DataInputStream.java:270)
at
sun.rmi.transport.StreamRemoteCall.executeCall(java.rmi@11.0.9.1/StreamRemoteCall.java:240)
at
sun.rmi.server.UnicastRef.invoke(java.rmi@11.0.9.1/UnicastRef.java:164)
at
java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:217)
at
java.rmi.server.RemoteObjectInvocationHandler.invoke(java.rmi@11.0.9.1/RemoteObjectInvocationHandler.java:162)
at com.sun.proxy.$Proxy53.executeMethodOnObject(Unknown Source)
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
at
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrent(LuceneSearchWithRollingUpgradeTestBase.java:347)
at
org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeTestBase.rollServerToCurrentCreateLuceneIndexAndCreateRegion(LuceneSearchWithRollingUpgradeTestBase.java:359)
at
org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:108)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@11.0.9.1/Native
Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@11.0.9.1/NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@11.0.9.1/DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(java.base@11.0.9.1/Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235019#comment-17235019 ] ASF subversion and git services commented on GEODE-8724: Commit 4e241ffe6f6bda0254f97cdfe18929ce81d04ace in geode-native's branch refs/heads/develop from Mario Salazar de Torres [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=4e241ff ] GEODE-8724: Fix compilation using docker image (#696) - As latest tag for ubuntu base image was recently change from 18.04 to 20.04 it seems that some libraries version changed, like for example libc++. - As it seems with this new version libc++ headers are either not anymore located within /usr/include/c++/v1 or the symlink is missing. - So in order to solve that a symlink is manually created to ensure clang is able to find libc++ headers. > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235017#comment-17235017 ] ASF subversion and git services commented on GEODE-8724: Commit 4e241ffe6f6bda0254f97cdfe18929ce81d04ace in geode-native's branch refs/heads/develop from Mario Salazar de Torres [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=4e241ff ] GEODE-8724: Fix compilation using docker image (#696) - As latest tag for ubuntu base image was recently change from 18.04 to 20.04 it seems that some libraries version changed, like for example libc++. - As it seems with this new version libc++ headers are either not anymore located within /usr/include/c++/v1 or the symlink is missing. - So in order to solve that a symlink is manually created to ensure clang is able to find libc++ headers. > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-8724. - Resolution: Fixed > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-8724. --- > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8724) Fix compilation using geode-native docker image
[ https://issues.apache.org/jira/browse/GEODE-8724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17235016#comment-17235016 ] ASF GitHub Bot commented on GEODE-8724: --- pdxcodemonkey merged pull request #696: URL: https://github.com/apache/geode-native/pull/696 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Fix compilation using geode-native docker image > --- > > Key: GEODE-8724 > URL: https://issues.apache.org/jira/browse/GEODE-8724 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0, 1.13.1 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > > As geode-native was re-built and re-uploaded, it's now using the latest > version of ubuntu, which is 20.04 as of some months. > Thing is docker builds started to fail after uploading the new docker image. > This task is intended to look into the issue and propose one/several > solutions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7489) DistributionArchUnitTest is running out of memory for some users
[
https://issues.apache.org/jira/browse/GEODE-7489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernest Burghardt reassigned GEODE-7489:
---
Assignee: (was: Ernest Burghardt)
> DistributionArchUnitTest is running out of memory for some users
>
>
> Key: GEODE-7489
> URL: https://issues.apache.org/jira/browse/GEODE-7489
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Dan Smith
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This test ran out of memory when running ./gradlew build for some users. From
> the mailing list:
> {noformat}
> Any ideas why DistributionArchUnitTest would run OutOfMemoryError when
> doing a "./gradlew build"?
> I think we should move any unit tests that run OutOfMemoryError out of unit
> tests (to integration tests maybe?).
> > Task :geode:geode-core:test
> Heap dump file created [957877145 bytes in 17.227 secs]
> org.apache.geode.distributed.internal.DistributionArchUnitTest >
> classMethod FAILED
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> 6991 tests completed, 1 failed, 12 skipped
> {noformat}
> This is a relatively new test that is scanning a lot of classes for
> dependencies, so it may have memory issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison resolved GEODE-8719.
---
Resolution: Fixed
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Sarah Abbey
>Assignee: John Hutchison
>Priority: Minor
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Hutchison reassigned GEODE-8719:
-
Assignee: John Hutchison
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Sarah Abbey
>Assignee: John Hutchison
>Priority: Minor
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8721) member that should become coordinator never detects loss of current coordinator
[
https://issues.apache.org/jira/browse/GEODE-8721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234976#comment-17234976
]
ASF GitHub Bot commented on GEODE-8721:
---
echobravopapa commented on a change in pull request #5758:
URL: https://github.com/apache/geode/pull/5758#discussion_r526379316
##
File path:
geode-membership/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
##
@@ -257,6 +257,7 @@ public void run() {
return;
}
+// TODO - why are we taking two clock readings and setting
currentTimeStamp twice?
Review comment:
seems to be done to detect JVM pauses and delay suspect processing in
those cases...
##
File path:
geode-membership/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
##
@@ -1242,7 +1243,11 @@ void processMessage(FinalCheckPassedMessage m) {
if (isStopping) {
return;
}
-contactedBy(m.getSuspect());
+// if we're currently processing a final-check for this member don't
artificially update the
Review comment:
solid fix!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> member that should become coordinator never detects loss of current
> coordinator
> ---
>
> Key: GEODE-8721
> URL: https://issues.apache.org/jira/browse/GEODE-8721
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.14.0
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: pull-request-available, release-blocker
>
> During a network partition a server that should have become membership
> coordinator and shut down its side of the partition never detected the loss
> of a server on the other side of the partition. Instead it continually
> performed availability checks on that other server and the checks passed.
> Its log file had continually increasing timestamps for when it claimed the
> other server had contacted it, which was not possible due to the network
> partition (which was formed through iptable manipulation).
> At least one other server on its side of the network partition was doing the
> same thing. It looks like they were interfering with each others
> availability checks in some way.
> {noformat}
> locatorp1_26023/system.log: [info 2020/10/20 22:23:16.227 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:12 PDT 2020
> locatorp1_26023/system.log: [info 2020/10/20 22:23:16.228 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Availability check passed
> for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> bridgep1_25995/system.log: [info 2020/10/20 22:23:16.229 PDT receiver,rs-F21040449a0i3large-72-61636> tid=0x23] No longer suspecting
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> bridgep1_25998/system.log: [info 2020/10/20 22:23:17.212 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:14 PDT 2020
> bridgep1_25998/system.log: [info 2020/10/20 22:23:17.213 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Availability check passed
> for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> locatorp1_26023/system.log: [info 2020/10/20 22:23:17.232 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Performing availability
> check for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> reason=Unable to send messages to this member via JGroups
> bridgep1_25998/system.log: [info 2020/10/20 22:23:18.215 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Performing availability
> check for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> reason=Unable to send messages to this member via JGroups
> bridgep1_25995/system.log: [info 2020/10/20 22:23:21.006 PDT Timer-2,rs-F21040449a0i3large-72-61636> tid=0x21] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:16 PDT 2020
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[
https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234977#comment-17234977
]
ASF GitHub Bot commented on GEODE-8711:
---
ringles commented on a change in pull request #5749:
URL: https://github.com/apache/geode/pull/5749#discussion_r526384361
##
File path:
geode-redis/src/main/java/org/apache/geode/redis/internal/ParameterRequirements/SlowlogParameterRequirements.java
##
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.ParameterRequirements;
+
+import static org.apache.geode.redis.internal.RedisConstants.ERROR_NOT_INTEGER;
+import static
org.apache.geode.redis.internal.RedisConstants.ERROR_UNKNOWN_SLOWLOG_SUBCOMMAND;
+
+import org.apache.geode.redis.internal.netty.Command;
+import org.apache.geode.redis.internal.netty.ExecutionHandlerContext;
+
+public class SlowlogParameterRequirements implements ParameterRequirements {
+ @Override
+ public void checkParameters(Command command, ExecutionHandlerContext
context) {
+int numberOfArguments = command.getProcessedCommand().size();
+
+if (numberOfArguments < 2) {
+ throw new
RedisParametersMismatchException(command.wrongNumberOfArgumentsErrorMessage());
+} else if (numberOfArguments == 2) {
+ confirmKnownSubcommands(command);
+} else if (numberOfArguments == 3) {
+ confirmArgumentsToGetSubcommand(command);
+} else if (numberOfArguments > 3) {
Review comment:
Demoted to comment, just to keep LGTM happy.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Enable SLOWLOG command to support Redis monitoring tools
>
>
> Key: GEODE-8711
> URL: https://issues.apache.org/jira/browse/GEODE-8711
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Raymond Ingles
>Priority: Major
> Labels: pull-request-available
>
> The Redis SLOWLOG command tracks slow-executing commands. This will implement
> a placeholder to prevent errors in tools like Datadog or Redis Insights.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8726) NetstatFunction throws OutOfMemoryError
[
https://issues.apache.org/jira/browse/GEODE-8726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-8726:
--
Labels: GeodeOperationAPI (was: )
> NetstatFunction throws OutOfMemoryError
> ---
>
> Key: GEODE-8726
> URL: https://issues.apache.org/jira/browse/GEODE-8726
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.14.0
>Reporter: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI
>
> If the output of {{lsof}} is very large, {{NetstatFunction}} throws
> {{OutOfMemoryError}}.
> An upcoming commit runs distributed tests in parallel outside of docker. If
> {{lsof}} executes while many tests are running on the same machine, its
> output is very large. {{NetstatFunction}} tries to append this output onto a
> {{StringBuilder}} one line at a time. When the {{StringBuilder}} attempts to
> increase the size of its internal buffer, not enough memory is available.
> This is essentially a recurrence of GEODE-2488. The fix for that ticket made
> {{NetstatFunction}} more memory efficient, but running the tests in parallel
> creates an extreme environment where even that added efficiency is not enough.
> One possible fix: Write the {{lsof}} output to a file instead of to an
> in-memory {{StringBuilder}}.
> Example failure:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.Fix the strings or use IgnoredException.addIgnoredException to
> ignore.---Found
> suspect string in 'dunit_suspect-vm2.log' at line 566
> [fatal 2020/11/17 01:53:38.221 UTC tid=86]
> Uncaught exception in thread Thread[ClientHealthMonitor Thread,5,RMI
> Runtime]java.lang.OutOfMemoryError: Java heap space at
> java.base/java.util.Arrays.copyOf(Arrays.java:3745) at
> java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:172)
> at
> java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:538)
> at java.base/java.lang.StringBuilder.append(StringBuilder.java:174) at
> org.apache.geode.management.internal.cli.functions.NetstatFunction.executeLsof(NetstatFunction.java:178)
> at
> org.apache.geode.management.internal.cli.functions.NetstatFunction.executeCommand(NetstatFunction.java:227)
> at
> org.apache.geode.management.internal.cli.functions.NetstatFunction.execute(NetstatFunction.java:80)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:441)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:446)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:381)
> at
> org.apache.geode.distributed.internal.ClusterOperationExecutors$$Lambda$240/0x00084078f040.invoke(Unknown
> Source) at
> org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
> at
> org.apache.geode.logging.internal.executors.LoggingThreadFactory$$Lambda$230/0x00084078c840.run(Unknown
> Source) at java.base/java.lang.Thread.run(Thread.java:834)
> ---Found
> suspect string in 'dunit_suspect-vm2.log' at line 587
> [fatal 2020/11/17 01:53:38.222 UTC tid=88]
> Uncaught exception in thread Thread[Function Execution Processor2,10,RMI
> Runtime]java.lang.OutOfMemoryError: Java heap space at
> java.base/java.util.Arrays.copyOf(Arrays.java:3745) at
> java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:172)
> at
> java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:538)
> at java.base/java.lang.StringBuilder.append(StringBuilder.java:174) at
> org.apache.geode.management.internal.cli.functions.NetstatFunction.executeLsof(NetstatFunction.java:178)
> at
> org.apache.geode.management.internal.cli.functions.NetstatFunction.executeCommand(NetstatFunction.java:227)
> at
> org.apache.geode.management.internal.cli.functions.NetstatFunction.execute(NetstatFunction.java:80)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
> at
>
[jira] [Created] (GEODE-8726) NetstatFunction throws OutOfMemoryError
Dale Emery created GEODE-8726:
-
Summary: NetstatFunction throws OutOfMemoryError
Key: GEODE-8726
URL: https://issues.apache.org/jira/browse/GEODE-8726
Project: Geode
Issue Type: Bug
Components: gfsh
Affects Versions: 1.14.0
Reporter: Dale Emery
If the output of {{lsof}} is very large, {{NetstatFunction}} throws
{{OutOfMemoryError}}.
An upcoming commit runs distributed tests in parallel outside of docker. If
{{lsof}} executes while many tests are running on the same machine, its output
is very large. {{NetstatFunction}} tries to append this output onto a
{{StringBuilder}} one line at a time. When the {{StringBuilder}} attempts to
increase the size of its internal buffer, not enough memory is available.
This is essentially a recurrence of GEODE-2488. The fix for that ticket made
{{NetstatFunction}} more memory efficient, but running the tests in parallel
creates an extreme environment where even that added efficiency is not enough.
One possible fix: Write the {{lsof}} output to a file instead of to an
in-memory {{StringBuilder}}.
Example failure:
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.Fix the strings or use IgnoredException.addIgnoredException to
ignore.---Found
suspect string in 'dunit_suspect-vm2.log' at line 566
[fatal 2020/11/17 01:53:38.221 UTC tid=86]
Uncaught exception in thread Thread[ClientHealthMonitor Thread,5,RMI
Runtime]java.lang.OutOfMemoryError: Java heap space at
java.base/java.util.Arrays.copyOf(Arrays.java:3745) at
java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:172)
at
java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:538)
at java.base/java.lang.StringBuilder.append(StringBuilder.java:174) at
org.apache.geode.management.internal.cli.functions.NetstatFunction.executeLsof(NetstatFunction.java:178)
at
org.apache.geode.management.internal.cli.functions.NetstatFunction.executeCommand(NetstatFunction.java:227)
at
org.apache.geode.management.internal.cli.functions.NetstatFunction.execute(NetstatFunction.java:80)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:441)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:446)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.doFunctionExecutionThread(ClusterOperationExecutors.java:381)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors$$Lambda$240/0x00084078f040.invoke(Unknown
Source) at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:120)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory$$Lambda$230/0x00084078c840.run(Unknown
Source) at java.base/java.lang.Thread.run(Thread.java:834)
---Found
suspect string in 'dunit_suspect-vm2.log' at line 587
[fatal 2020/11/17 01:53:38.222 UTC tid=88]
Uncaught exception in thread Thread[Function Execution Processor2,10,RMI
Runtime]java.lang.OutOfMemoryError: Java heap space at
java.base/java.util.Arrays.copyOf(Arrays.java:3745) at
java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:172)
at
java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:538)
at java.base/java.lang.StringBuilder.append(StringBuilder.java:174) at
org.apache.geode.management.internal.cli.functions.NetstatFunction.executeLsof(NetstatFunction.java:178)
at
org.apache.geode.management.internal.cli.functions.NetstatFunction.executeCommand(NetstatFunction.java:227)
at
org.apache.geode.management.internal.cli.functions.NetstatFunction.execute(NetstatFunction.java:80)
at
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:201)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:441)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
[jira] [Commented] (GEODE-8623) Timing between DNS and Geode startup can result in permanent unknown host exceptions.
[
https://issues.apache.org/jira/browse/GEODE-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234970#comment-17234970
]
ASF GitHub Bot commented on GEODE-8623:
---
Bill commented on a change in pull request #5743:
URL: https://github.com/apache/geode/pull/5743#discussion_r526342190
##
File path: geode-common/src/main/java/org/apache/geode/internal/Retry.java
##
@@ -47,45 +47,44 @@ public void sleep(long sleepTime, TimeUnit sleepTimeUnit)
throws InterruptedExce
}
}
- private static final SteadyClock steadyClock = new SteadyClock();
+ private static final SteadyTimer steadyClock = new SteadyTimer();
/**
* Try the supplier function until the predicate is true or timeout occurs.
*
* @param timeout to retry for
+ * @param timeoutUnit the unit for timeout
* @param interval time between each try
- * @param timeUnit to retry for
+ * @param intervalUnit the unit for interval
* @param supplier to execute until predicate is true or times out
* @param predicate to test for retry
* @param type of return value
* @return value from supplier after it passes predicate or times out.
*/
- public static T tryFor(long timeout,
- long interval,
- TimeUnit timeUnit,
+ public static T tryFor(long timeout, TimeUnit timeoutUnit,
+ long interval, TimeUnit intervalUnit,
Supplier supplier,
Predicate predicate) throws TimeoutException, InterruptedException {
-return tryFor(timeout, interval, timeUnit, supplier, predicate,
steadyClock);
+return tryFor(timeout, timeoutUnit, interval, intervalUnit, supplier,
predicate, steadyClock);
}
@VisibleForTesting
- static T tryFor(long timeout,
- long interval,
- TimeUnit timeUnit,
+ static T tryFor(long timeout, TimeUnit timeoutUnit,
+ long interval, TimeUnit intervalUnit,
Supplier supplier,
Predicate predicate,
- Clock clock) throws TimeoutException, InterruptedException {
-long until = clock.nanoTime() + NANOSECONDS.convert(timeout, timeUnit);
+ Timer timer) throws TimeoutException, InterruptedException {
+long until = timer.nanoTime() + NANOSECONDS.convert(timeout, timeoutUnit);
T value;
do {
value = supplier.get();
if (predicate.test(value)) {
return value;
} else {
-clock.sleep(interval, timeUnit);
+timer.sleep(interval, intervalUnit);
Review comment:
I don't think any extra call is needed to implement the proposal
@jinmeiliao. The call to `timer.nanoTime()` can be done in the body of the loop
~~and the result can be used in the body and in the `while()` condition I
think~~ . I still feel like the added code complexity is worth it since the
whole point of making a stand-alone `Retry` utility like this is to be able to
use it in many situations.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Timing between DNS and Geode startup can result in permanent unknown host
> exceptions.
> -
>
> Key: GEODE-8623
> URL: https://issues.apache.org/jira/browse/GEODE-8623
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.9.0, 1.9.1, 1.10.0, 1.9.2, 1.11.0, 1.12.0, 1.13.0,
> 1.14.0, 1.13.1
>Reporter: Jacob Barrett
>Priority: Minor
> Labels: pull-request-available
>
> In a managed environment were local host name DNS entries and the startup of
> Geode happen concurrently it is possible for Geode to fail name resolution in
> the local hostname caching. If it fails to resolve the local hostname when
> loading the caching utility class then any service dependent on this name
> will fail without chance for recovery.
> {code}
> [error 2020/09/30 19:50:21.644 UTC tid=0x1] Jmx manager could not be
> started because java.net.UnknownHostException
> org.apache.geode.management.ManagementException: java.net.UnknownHostException
> at
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:133)
> at
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:432)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:181)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:127)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2063)
> at
[jira] [Commented] (GEODE-8714) Events stuck in parallel GW senders queue
[ https://issues.apache.org/jira/browse/GEODE-8714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234965#comment-17234965 ] ASF subversion and git services commented on GEODE-8714: Commit 57db39c1aed1d3fe21de5b4acbe1760f55978076 in geode's branch refs/heads/develop from Mario Ivanac [ https://gitbox.apache.org/repos/asf?p=geode.git;h=57db39c ] GEODE-8714_1: update test according to comments (#5760) > Events stuck in parallel GW senders queue > - > > Key: GEODE-8714 > URL: https://issues.apache.org/jira/browse/GEODE-8714 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > While restarting servers and gateway senders, in some cases, events are stuck > in queue, and never unqueued. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8521) Add P2P message reader threads to thread monitoring
[ https://issues.apache.org/jira/browse/GEODE-8521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234960#comment-17234960 ] ASF subversion and git services commented on GEODE-8521: Commit 8f8e9d753caf18962f5ee5933e757ecd9f8f0639 in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f8e9d7 ] GEODE-8521: Add tests for CoreLoggingExecutors (#5757) Cleanup constructors of logging executors and add tests for CoreLoggingExecutors. > Add P2P message reader threads to thread monitoring > --- > > Key: GEODE-8521 > URL: https://issues.apache.org/jira/browse/GEODE-8521 > Project: Geode > Issue Type: Wish > Components: messaging >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Add P2P message reader threads to thread monitoring to help with identifying > stuck P2P message readers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8714) Events stuck in parallel GW senders queue
[ https://issues.apache.org/jira/browse/GEODE-8714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234961#comment-17234961 ] ASF GitHub Bot commented on GEODE-8714: --- pivotal-amurmann commented on pull request #5752: URL: https://github.com/apache/geode/pull/5752#issuecomment-729907238 @mivanac I agree that all usage of deprecated functionality should be cleaned up. Unfortunately, that would take a long time. As @kohlmu-pivotal points out, we as a community need to work to make it better over time and not move us further away from our goal. Please call out if you see other PRs that are also moving us away from a cleaner, more stable, more maintainable code base! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Events stuck in parallel GW senders queue > - > > Key: GEODE-8714 > URL: https://issues.apache.org/jira/browse/GEODE-8714 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > While restarting servers and gateway senders, in some cases, events are stuck > in queue, and never unqueued. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8521) Add P2P message reader threads to thread monitoring
[ https://issues.apache.org/jira/browse/GEODE-8521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234959#comment-17234959 ] ASF subversion and git services commented on GEODE-8521: Commit 8f8e9d753caf18962f5ee5933e757ecd9f8f0639 in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8f8e9d7 ] GEODE-8521: Add tests for CoreLoggingExecutors (#5757) Cleanup constructors of logging executors and add tests for CoreLoggingExecutors. > Add P2P message reader threads to thread monitoring > --- > > Key: GEODE-8521 > URL: https://issues.apache.org/jira/browse/GEODE-8521 > Project: Geode > Issue Type: Wish > Components: messaging >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Add P2P message reader threads to thread monitoring to help with identifying > stuck P2P message readers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8521) Add P2P message reader threads to thread monitoring
[ https://issues.apache.org/jira/browse/GEODE-8521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234958#comment-17234958 ] ASF GitHub Bot commented on GEODE-8521: --- kirklund merged pull request #5757: URL: https://github.com/apache/geode/pull/5757 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add P2P message reader threads to thread monitoring > --- > > Key: GEODE-8521 > URL: https://issues.apache.org/jira/browse/GEODE-8521 > Project: Geode > Issue Type: Wish > Components: messaging >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Add P2P message reader threads to thread monitoring to help with identifying > stuck P2P message readers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[
https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234944#comment-17234944
]
ASF GitHub Bot commented on GEODE-8711:
---
sabbey37 commented on a change in pull request #5749:
URL: https://github.com/apache/geode/pull/5749#discussion_r526356811
##
File path:
geode-redis/src/main/java/org/apache/geode/redis/internal/ParameterRequirements/SlowlogParameterRequirements.java
##
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.ParameterRequirements;
+
+import static org.apache.geode.redis.internal.RedisConstants.ERROR_NOT_INTEGER;
+import static
org.apache.geode.redis.internal.RedisConstants.ERROR_UNKNOWN_SLOWLOG_SUBCOMMAND;
+
+import org.apache.geode.redis.internal.netty.Command;
+import org.apache.geode.redis.internal.netty.ExecutionHandlerContext;
+
+public class SlowlogParameterRequirements implements ParameterRequirements {
+ @Override
+ public void checkParameters(Command command, ExecutionHandlerContext
context) {
+int numberOfArguments = command.getProcessedCommand().size();
+
+if (numberOfArguments < 2) {
+ throw new
RedisParametersMismatchException(command.wrongNumberOfArgumentsErrorMessage());
+} else if (numberOfArguments == 2) {
+ confirmKnownSubcommands(command);
+} else if (numberOfArguments == 3) {
+ confirmArgumentsToGetSubcommand(command);
+} else if (numberOfArguments > 3) {
Review comment:
That totally makes sense. I'm not sure how much LGTM alerts matter?
@jdeppe-pivotal do you know?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Enable SLOWLOG command to support Redis monitoring tools
>
>
> Key: GEODE-8711
> URL: https://issues.apache.org/jira/browse/GEODE-8711
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Raymond Ingles
>Priority: Major
> Labels: pull-request-available
>
> The Redis SLOWLOG command tracks slow-executing commands. This will implement
> a placeholder to prevent errors in tools like Datadog or Redis Insights.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8720) VMDumpThreadsDistributedTest > threadDumpOfVmContainsRemoteThreads fails due to main thread state being RUNNABLE instead of TIMED_WAITING
[
https://issues.apache.org/jira/browse/GEODE-8720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-8720:
-
Labels: TestFramework (was: )
> VMDumpThreadsDistributedTest > threadDumpOfVmContainsRemoteThreads fails due
> to main thread state being RUNNABLE instead of TIMED_WAITING
> -
>
> Key: GEODE-8720
> URL: https://issues.apache.org/jira/browse/GEODE-8720
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Kirk Lund
>Priority: Major
> Labels: TestFramework
>
> {code:java}
> org.apache.geode.test.dunit.tests.VMDumpThreadsDistributedTest >
> threadDumpOfVmContainsRemoteThreads FAILED
> java.lang.AssertionError:
> Expecting:
> ""pool-2-thread-2" Id=35 TIMED_WAITING on
> java.util.concurrent.CountDownLatch$Sync@620c8150
> at sun.misc.Unsafe.park(Native Method)
> - waiting on java.util.concurrent.CountDownLatch$Sync@620c8150
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> at
> org.apache.geode.test.dunit.tests.VMDumpThreadsDistributedTest.syncMethod(VMDumpThreadsDistributedTest.java:126)
> - locked
> org.apache.geode.test.dunit.tests.VMDumpThreadsDistributedTest@4c56d308
> at
> org.apache.geode.test.dunit.tests.VMDumpThreadsDistributedTest.lambda$null$2(VMDumpThreadsDistributedTest.java:101)
> at
> org.apache.geode.test.dunit.tests.VMDumpThreadsDistributedTest$$Lambda$47/1692578668.run(Unknown
> Source)
> ...
> Number of locked synchronizers = 1
> - java.util.concurrent.ThreadPoolExecutor$Worker@e404e6b
> "pool-2-thread-1" Id=33 WAITING on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@e6c1144
> at sun.misc.Unsafe.park(Native Method)
> - waiting on
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@e6c1144
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> "RMI TCP Connection(1)-172.17.0.5" Id=32 RUNNABLE
> at sun.management.ThreadImpl.dumpThreads0(Native Method)
> at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:448)
> at org.apache.geode.test.dunit.VM.dumpThreads(VM.java:223)
> at
> org.apache.geode.test.dunit.tests.VMDumpThreadsDistributedTest$$Lambda$49/1028270293.call(Unknown
> Source)
> 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:498)
> ...
> Number of locked synchronizers = 1
> - java.util.concurrent.ThreadPoolExecutor$Worker@75bd2774
> "RMI Reaper" Id=31 WAITING on java.lang.ref.ReferenceQueue$Lock@9aaa549
> at java.lang.Object.wait(Native Method)
> - waiting on java.lang.ref.ReferenceQueue$Lock@9aaa549
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:165)
> at sun.rmi.transport.ObjectTable$Reaper.run(ObjectTable.java:351)
> at java.lang.Thread.run(Thread.java:748)
> "RMI TCP Accept-0" Id=30 RUNNABLE (in native)
> at java.net.PlainSocketImpl.socketAccept(Native Method)
> at
> java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:409)
> at java.net.ServerSocket.implAccept(ServerSocket.java:560)
> at java.net.ServerSocket.accept(ServerSocket.java:528)
> at
> sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:405)
> at
> sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:377)
> at java.lang.Thread.run(Thread.java:748)
[jira] [Commented] (GEODE-8714) Events stuck in parallel GW senders queue
[ https://issues.apache.org/jira/browse/GEODE-8714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234933#comment-17234933 ] ASF GitHub Bot commented on GEODE-8714: --- kohlmu-pivotal commented on pull request #5752: URL: https://github.com/apache/geode/pull/5752#issuecomment-729886341 @mivanac Thank you for trying to make the new look like the "old"... I do follow a the simple guide of the "Boy Scouts" "Leave the place in a better state that you found it." If I were you, there would be a great chance that I would clean up the test cases in question. That way at least I know that there is less to clean up. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Events stuck in parallel GW senders queue > - > > Key: GEODE-8714 > URL: https://issues.apache.org/jira/browse/GEODE-8714 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0 > > > While restarting servers and gateway senders, in some cases, events are stuck > in queue, and never unqueued. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8623) Timing between DNS and Geode startup can result in permanent unknown host exceptions.
[
https://issues.apache.org/jira/browse/GEODE-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234931#comment-17234931
]
ASF GitHub Bot commented on GEODE-8623:
---
Bill commented on a change in pull request #5743:
URL: https://github.com/apache/geode/pull/5743#discussion_r526342190
##
File path: geode-common/src/main/java/org/apache/geode/internal/Retry.java
##
@@ -47,45 +47,44 @@ public void sleep(long sleepTime, TimeUnit sleepTimeUnit)
throws InterruptedExce
}
}
- private static final SteadyClock steadyClock = new SteadyClock();
+ private static final SteadyTimer steadyClock = new SteadyTimer();
/**
* Try the supplier function until the predicate is true or timeout occurs.
*
* @param timeout to retry for
+ * @param timeoutUnit the unit for timeout
* @param interval time between each try
- * @param timeUnit to retry for
+ * @param intervalUnit the unit for interval
* @param supplier to execute until predicate is true or times out
* @param predicate to test for retry
* @param type of return value
* @return value from supplier after it passes predicate or times out.
*/
- public static T tryFor(long timeout,
- long interval,
- TimeUnit timeUnit,
+ public static T tryFor(long timeout, TimeUnit timeoutUnit,
+ long interval, TimeUnit intervalUnit,
Supplier supplier,
Predicate predicate) throws TimeoutException, InterruptedException {
-return tryFor(timeout, interval, timeUnit, supplier, predicate,
steadyClock);
+return tryFor(timeout, timeoutUnit, interval, intervalUnit, supplier,
predicate, steadyClock);
}
@VisibleForTesting
- static T tryFor(long timeout,
- long interval,
- TimeUnit timeUnit,
+ static T tryFor(long timeout, TimeUnit timeoutUnit,
+ long interval, TimeUnit intervalUnit,
Supplier supplier,
Predicate predicate,
- Clock clock) throws TimeoutException, InterruptedException {
-long until = clock.nanoTime() + NANOSECONDS.convert(timeout, timeUnit);
+ Timer timer) throws TimeoutException, InterruptedException {
+long until = timer.nanoTime() + NANOSECONDS.convert(timeout, timeoutUnit);
T value;
do {
value = supplier.get();
if (predicate.test(value)) {
return value;
} else {
-clock.sleep(interval, timeUnit);
+timer.sleep(interval, intervalUnit);
Review comment:
I don't think any extra call is needed to implement the proposal
@jinmeiliao. The call to `timer.nanoTime()` can be done in the body of the loop
and the result can be used in the body and in the `while()` condition I think.
I still feel like the added code complexity is worth it since the whole point
of making a stand-alone `Retry` utility like this is to be able to use it in
many situations.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Timing between DNS and Geode startup can result in permanent unknown host
> exceptions.
> -
>
> Key: GEODE-8623
> URL: https://issues.apache.org/jira/browse/GEODE-8623
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.9.0, 1.9.1, 1.10.0, 1.9.2, 1.11.0, 1.12.0, 1.13.0,
> 1.14.0, 1.13.1
>Reporter: Jacob Barrett
>Priority: Minor
> Labels: pull-request-available
>
> In a managed environment were local host name DNS entries and the startup of
> Geode happen concurrently it is possible for Geode to fail name resolution in
> the local hostname caching. If it fails to resolve the local hostname when
> loading the caching utility class then any service dependent on this name
> will fail without chance for recovery.
> {code}
> [error 2020/09/30 19:50:21.644 UTC tid=0x1] Jmx manager could not be
> started because java.net.UnknownHostException
> org.apache.geode.management.ManagementException: java.net.UnknownHostException
> at
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:133)
> at
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:432)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:181)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:127)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2063)
> at
>
[jira] [Commented] (GEODE-8623) Timing between DNS and Geode startup can result in permanent unknown host exceptions.
[
https://issues.apache.org/jira/browse/GEODE-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234929#comment-17234929
]
ASF GitHub Bot commented on GEODE-8623:
---
Bill commented on a change in pull request #5743:
URL: https://github.com/apache/geode/pull/5743#discussion_r526342190
##
File path: geode-common/src/main/java/org/apache/geode/internal/Retry.java
##
@@ -47,45 +47,44 @@ public void sleep(long sleepTime, TimeUnit sleepTimeUnit)
throws InterruptedExce
}
}
- private static final SteadyClock steadyClock = new SteadyClock();
+ private static final SteadyTimer steadyClock = new SteadyTimer();
/**
* Try the supplier function until the predicate is true or timeout occurs.
*
* @param timeout to retry for
+ * @param timeoutUnit the unit for timeout
* @param interval time between each try
- * @param timeUnit to retry for
+ * @param intervalUnit the unit for interval
* @param supplier to execute until predicate is true or times out
* @param predicate to test for retry
* @param type of return value
* @return value from supplier after it passes predicate or times out.
*/
- public static T tryFor(long timeout,
- long interval,
- TimeUnit timeUnit,
+ public static T tryFor(long timeout, TimeUnit timeoutUnit,
+ long interval, TimeUnit intervalUnit,
Supplier supplier,
Predicate predicate) throws TimeoutException, InterruptedException {
-return tryFor(timeout, interval, timeUnit, supplier, predicate,
steadyClock);
+return tryFor(timeout, timeoutUnit, interval, intervalUnit, supplier,
predicate, steadyClock);
}
@VisibleForTesting
- static T tryFor(long timeout,
- long interval,
- TimeUnit timeUnit,
+ static T tryFor(long timeout, TimeUnit timeoutUnit,
+ long interval, TimeUnit intervalUnit,
Supplier supplier,
Predicate predicate,
- Clock clock) throws TimeoutException, InterruptedException {
-long until = clock.nanoTime() + NANOSECONDS.convert(timeout, timeUnit);
+ Timer timer) throws TimeoutException, InterruptedException {
+long until = timer.nanoTime() + NANOSECONDS.convert(timeout, timeoutUnit);
T value;
do {
value = supplier.get();
if (predicate.test(value)) {
return value;
} else {
-clock.sleep(interval, timeUnit);
+timer.sleep(interval, intervalUnit);
Review comment:
I don't think any extra call is needed to implement the proposal
@jinmeiliao. The call to `timer.nanoTime()` can be done in the body of the loop
and used in the body and in the `while()` condition I think. I still feel like
the added code complexity is worth it since the whole point of making a
stand-alone `Retry` utility like this is to be able to use it in many
situations.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Timing between DNS and Geode startup can result in permanent unknown host
> exceptions.
> -
>
> Key: GEODE-8623
> URL: https://issues.apache.org/jira/browse/GEODE-8623
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.9.0, 1.9.1, 1.10.0, 1.9.2, 1.11.0, 1.12.0, 1.13.0,
> 1.14.0, 1.13.1
>Reporter: Jacob Barrett
>Priority: Minor
> Labels: pull-request-available
>
> In a managed environment were local host name DNS entries and the startup of
> Geode happen concurrently it is possible for Geode to fail name resolution in
> the local hostname caching. If it fails to resolve the local hostname when
> loading the caching utility class then any service dependent on this name
> will fail without chance for recovery.
> {code}
> [error 2020/09/30 19:50:21.644 UTC tid=0x1] Jmx manager could not be
> started because java.net.UnknownHostException
> org.apache.geode.management.ManagementException: java.net.UnknownHostException
> at
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:133)
> at
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:432)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:181)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:127)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2063)
> at
>
[jira] [Commented] (GEODE-8656) Ping not sent to the right gateway receiver endpoint when several receivers have the same hostname-for-senders value
[
https://issues.apache.org/jira/browse/GEODE-8656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234920#comment-17234920
]
ASF GitHub Bot commented on GEODE-8656:
---
bschuchardt commented on a change in pull request #5670:
URL: https://github.com/apache/geode/pull/5670#discussion_r525594024
##
File path:
geode-assembly/src/acceptanceTest/java/org/apache/geode/cache/wan/SeveralGatewayReceiversWithSamePortAndHostnameForSenders.java
##
@@ -0,0 +1,260 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+package org.apache.geode.cache.wan;
+
+import static
com.palantir.docker.compose.execution.DockerComposeExecArgument.arguments;
+import static
com.palantir.docker.compose.execution.DockerComposeExecOption.options;
+import static org.apache.geode.cache.Region.SEPARATOR;
+import static
org.apache.geode.distributed.ConfigurationProperties.DISTRIBUTED_SYSTEM_ID;
+import static org.apache.geode.distributed.ConfigurationProperties.LOCATORS;
+import static
org.apache.geode.distributed.ConfigurationProperties.REMOTE_LOCATORS;
+import static org.junit.Assert.assertEquals;
+import static org.junit.Assert.assertNotNull;
+
+import java.io.File;
+import java.net.URL;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.Properties;
+import java.util.StringTokenizer;
+
+import com.palantir.docker.compose.DockerComposeRule;
+import org.junit.BeforeClass;
+import org.junit.ClassRule;
+import org.junit.Rule;
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.Cache;
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.cache.PartitionAttributesFactory;
+import org.apache.geode.cache.Region;
+import org.apache.geode.cache.RegionFactory;
+import org.apache.geode.cache.RegionShortcut;
+import org.apache.geode.cache.persistence.PartitionOfflineException;
+import org.apache.geode.client.sni.NotOnWindowsDockerRule;
+import org.apache.geode.distributed.Locator;
+import org.apache.geode.internal.cache.ForceReattemptException;
+import org.apache.geode.internal.cache.PoolStats;
+import org.apache.geode.internal.cache.wan.AbstractGatewaySender;
+import org.apache.geode.internal.cache.wan.InternalGatewaySenderFactory;
+import org.apache.geode.test.dunit.IgnoredException;
+import org.apache.geode.test.dunit.VM;
+import org.apache.geode.test.dunit.rules.DistributedRule;
+import org.apache.geode.test.junit.categories.WanTest;
+
+
+/**
+ * These tests use two Geode sites:
+ *
+ * - One site (the remote one) consisting of a 2-server, 1-locator Geode
cluster.
+ * The servers host a partition region (region-wan) and have gateway senders
to receive events
+ * from the other site with the same value for hostname-for-senders and
listening on the
+ * same port (2324).
+ * The servers and locator run each inside a Docker container and are not
route-able
+ * from the host (where this JUnit test is running).
+ * Another Docker container is running the HAProxy image and it's set up as a
TCP load balancer.
+ * The other site connects to the locator and to the gateway receivers via the
+ * TCP load balancer that forwards traffic directed to the 20334 port to the
locator and
+ * traffic directed to the 2324 port to the receivers in a round robin fashion.
+ *
+ * - Another site consisting of a 1-server, 1-locator Geode cluster.
+ * The server hosts a partition region (region-wan) and has a parallel gateway
receiver
+ * to send events to the remote site.
+ *
+ * The aim of the tests is verify that when several gateway receivers in a
remote site
+ * share the same port and hostname-for-senders, the pings sent from the
gateway senders
+ * reach the right gateway receiver and not just any of the receivers. Failure
to do this
+ * may result in the closing of connections by a gateway receiver for not
having
+ * received the ping in time.
+ */
+@Category({WanTest.class})
+public class SeveralGatewayReceiversWithSamePortAndHostnameForSenders {
+
+ private static final int NUM_SERVERS = 2;
+
+ private static Cache cache;
+
+ private static final URL DOCKER_COMPOSE_PATH =
+
[jira] [Updated] (GEODE-8573) SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
[
https://issues.apache.org/jira/browse/GEODE-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-8573:
-
Labels: GeodeOperationAPI (was: )
> SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
>
>
> Key: GEODE-8573
> URL: https://issues.apache.org/jira/browse/GEODE-8573
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/521]
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> > testRestartSerialGatewaySendersWhilePutting[1: numDispatchers=3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest$$Lambda$356/426344166.run
> in VM 5 running on Host 538fd3213f62 with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> that uses org.apache.geode.internal.cache.wan.InternalGatewaySender,
> org.apache.geode.internal.cache.wan.InternalGatewaySenderint [Sender
> statistics unprocessed event map size] expected:<[0]> but was:<[3]> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.validateSecondaryQueueSizeStat(SerialGatewaySenderOperationsDistributedTest.java:1216)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$testRestartSerialGatewaySendersWhilePutting$bb17a952$23(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.junit.ComparisonFailure: [Sender statistics unprocessed event
> map size] expected:<[0]> but was:<[3]>
> at
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$validateSecondaryQueueSizeStat$8(SerialGatewaySenderOperationsDistributedTest.java:1219)
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-results/distributedTest/1601774166/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-artifacts/1601774166/distributedtestfiles-OpenJDK8-1.14.0-build.0389.tgz]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8573) SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
[
https://issues.apache.org/jira/browse/GEODE-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234914#comment-17234914
]
Kirk Lund commented on GEODE-8573:
--
Flakiness was caused by a previous commit. All I did was clean up the test to
be easier to understand.
> SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
>
>
> Key: GEODE-8573
> URL: https://issues.apache.org/jira/browse/GEODE-8573
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Mark Hanson
>Priority: Major
> Labels: GeodeOperationAPI
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/521]
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> > testRestartSerialGatewaySendersWhilePutting[1: numDispatchers=3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest$$Lambda$356/426344166.run
> in VM 5 running on Host 538fd3213f62 with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> that uses org.apache.geode.internal.cache.wan.InternalGatewaySender,
> org.apache.geode.internal.cache.wan.InternalGatewaySenderint [Sender
> statistics unprocessed event map size] expected:<[0]> but was:<[3]> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.validateSecondaryQueueSizeStat(SerialGatewaySenderOperationsDistributedTest.java:1216)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$testRestartSerialGatewaySendersWhilePutting$bb17a952$23(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.junit.ComparisonFailure: [Sender statistics unprocessed event
> map size] expected:<[0]> but was:<[3]>
> at
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$validateSecondaryQueueSizeStat$8(SerialGatewaySenderOperationsDistributedTest.java:1219)
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-results/distributedTest/1601774166/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-artifacts/1601774166/distributedtestfiles-OpenJDK8-1.14.0-build.0389.tgz]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-8573) SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
[
https://issues.apache.org/jira/browse/GEODE-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-8573:
Assignee: (was: Kirk Lund)
> SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
>
>
> Key: GEODE-8573
> URL: https://issues.apache.org/jira/browse/GEODE-8573
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Mark Hanson
>Priority: Major
> Labels: GeodeOperationAPI
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/521]
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> > testRestartSerialGatewaySendersWhilePutting[1: numDispatchers=3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest$$Lambda$356/426344166.run
> in VM 5 running on Host 538fd3213f62 with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> that uses org.apache.geode.internal.cache.wan.InternalGatewaySender,
> org.apache.geode.internal.cache.wan.InternalGatewaySenderint [Sender
> statistics unprocessed event map size] expected:<[0]> but was:<[3]> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.validateSecondaryQueueSizeStat(SerialGatewaySenderOperationsDistributedTest.java:1216)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$testRestartSerialGatewaySendersWhilePutting$bb17a952$23(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.junit.ComparisonFailure: [Sender statistics unprocessed event
> map size] expected:<[0]> but was:<[3]>
> at
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$validateSecondaryQueueSizeStat$8(SerialGatewaySenderOperationsDistributedTest.java:1219)
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-results/distributedTest/1601774166/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-artifacts/1601774166/distributedtestfiles-OpenJDK8-1.14.0-build.0389.tgz]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-6154) Spring-shell is not an optional dependency if you create a Cache in an application
[
https://issues.apache.org/jira/browse/GEODE-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-6154.
--
Resolution: Not A Problem
> Spring-shell is not an optional dependency if you create a Cache in an
> application
> --
>
> Key: GEODE-6154
> URL: https://issues.apache.org/jira/browse/GEODE-6154
> Project: Geode
> Issue Type: Bug
> Components: core, jmx
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The geode-core pom should be considered the pom for Geode Cache, not Geode
> Client Cache. If we want to have a separate module for clients which leaves
> out certain dependencies then that would be one approach. Moving GFSH and the
> spring-shell dependent code to another Geode module would also be another
> approach that works. But simply crippling a pom so that one of the main uses
> of Geode does not work out of box is a big no-no.
> Creating a Cache in an application using maven dependencies (geode-core
> specifically) is supported but broken because we flag spring-shell as
> optional.
> A User who creates a Cache in an application should not be forced to either
> have JMX broken or explicitly add in spring-shell to their application's
> dependencies.
> {noformat}
> 10:31:55.168 [main] WARN o.a.g.d.i.InternalDistributedSystem -
> org/springframework/shell/core/Parser
> java.lang.NoClassDefFoundError: org/springframework/shell/core/Parser
> at
> org.apache.geode.management.internal.beans.MemberMBeanBridge.(MemberMBeanBridge.java:333)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:144)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:115)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:606)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1214)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:799)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:785)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:176)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:223)
> at
> io.github.kirklund.geode.GeodeApplicationIntegrationTest.setUp(GeodeApplicationIntegrationTest.java:35)
> 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:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.ClassNotFoundException:
>
[jira] [Closed] (GEODE-6154) Spring-shell is not an optional dependency if you create a Cache in an application
[
https://issues.apache.org/jira/browse/GEODE-6154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund closed GEODE-6154.
Already fixed.
> Spring-shell is not an optional dependency if you create a Cache in an
> application
> --
>
> Key: GEODE-6154
> URL: https://issues.apache.org/jira/browse/GEODE-6154
> Project: Geode
> Issue Type: Bug
> Components: core, jmx
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The geode-core pom should be considered the pom for Geode Cache, not Geode
> Client Cache. If we want to have a separate module for clients which leaves
> out certain dependencies then that would be one approach. Moving GFSH and the
> spring-shell dependent code to another Geode module would also be another
> approach that works. But simply crippling a pom so that one of the main uses
> of Geode does not work out of box is a big no-no.
> Creating a Cache in an application using maven dependencies (geode-core
> specifically) is supported but broken because we flag spring-shell as
> optional.
> A User who creates a Cache in an application should not be forced to either
> have JMX broken or explicitly add in spring-shell to their application's
> dependencies.
> {noformat}
> 10:31:55.168 [main] WARN o.a.g.d.i.InternalDistributedSystem -
> org/springframework/shell/core/Parser
> java.lang.NoClassDefFoundError: org/springframework/shell/core/Parser
> at
> org.apache.geode.management.internal.beans.MemberMBeanBridge.(MemberMBeanBridge.java:333)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:144)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:115)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:606)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1214)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:799)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:785)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:176)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:223)
> at
> io.github.kirklund.geode.GeodeApplicationIntegrationTest.setUp(GeodeApplicationIntegrationTest.java:35)
> 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:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
> at
> com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
> at
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
> Caused by: java.lang.ClassNotFoundException:
>
[jira] [Closed] (GEODE-6202) DUnit should not enable VALIDATE_SERIALIZABLE_OBJECTS by default
[ https://issues.apache.org/jira/browse/GEODE-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund closed GEODE-6202. > DUnit should not enable VALIDATE_SERIALIZABLE_OBJECTS by default > > > Key: GEODE-6202 > URL: https://issues.apache.org/jira/browse/GEODE-6202 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > DUnit should not enable VALIDATE_SERIALIZABLE_OBJECTS by default. This was > discussed on the dev list quite a while ago and the consensus was to remove > it. > Here's the discussion from dev-list: > https://lists.apache.org/thread.html/93087da51d2cb333158d60e65513246fc55ddc76c33fef32595c66f7@%3Cdev.geode.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-6202) DUnit should not enable VALIDATE_SERIALIZABLE_OBJECTS by default
[ https://issues.apache.org/jira/browse/GEODE-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-6202. -- Resolution: Won't Fix > DUnit should not enable VALIDATE_SERIALIZABLE_OBJECTS by default > > > Key: GEODE-6202 > URL: https://issues.apache.org/jira/browse/GEODE-6202 > Project: Geode > Issue Type: Wish > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > DUnit should not enable VALIDATE_SERIALIZABLE_OBJECTS by default. This was > discussed on the dev list quite a while ago and the consensus was to remove > it. > Here's the discussion from dev-list: > https://lists.apache.org/thread.html/93087da51d2cb333158d60e65513246fc55ddc76c33fef32595c66f7@%3Cdev.geode.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-6466) RegionExpirationIntegrationTest.regionTtlWithIdleMock: org.junit.ComparisonFailure: expected: but was:<"val">
[ https://issues.apache.org/jira/browse/GEODE-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-6466: Assignee: (was: Kirk Lund) > RegionExpirationIntegrationTest.regionTtlWithIdleMock: > org.junit.ComparisonFailure: expected: but was:<"val"> > --- > > Key: GEODE-6466 > URL: https://issues.apache.org/jira/browse/GEODE-6466 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Mark Hanson >Priority: Major > Labels: GeodeOperationAPI > > org.junit.ComparisonFailure: expected: but was:<"val"> > at sun.reflect.GeneratedConstructorAccessor25.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.cache.RegionExpirationIntegrationTest.regionTtlWithIdleMock(RegionExpirationIntegrationTest.java:126) > 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:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.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:117) > at
[jira] [Updated] (GEODE-6466) RegionExpirationIntegrationTest.regionTtlWithIdleMock: org.junit.ComparisonFailure: expected: but was:<"val">
[ https://issues.apache.org/jira/browse/GEODE-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-6466: - Labels: GeodeOperationAPI (was: ) > RegionExpirationIntegrationTest.regionTtlWithIdleMock: > org.junit.ComparisonFailure: expected: but was:<"val"> > --- > > Key: GEODE-6466 > URL: https://issues.apache.org/jira/browse/GEODE-6466 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Mark Hanson >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI > > org.junit.ComparisonFailure: expected: but was:<"val"> > at sun.reflect.GeneratedConstructorAccessor25.newInstance(Unknown > Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.cache.RegionExpirationIntegrationTest.regionTtlWithIdleMock(RegionExpirationIntegrationTest.java:126) > 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:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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:498) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.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:117) > at
[jira] [Assigned] (GEODE-3689) Unable to specify custom log4j configuration file from gfsh
[
https://issues.apache.org/jira/browse/GEODE-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-3689:
Assignee: (was: Kirk Lund)
> Unable to specify custom log4j configuration file from gfsh
> ---
>
> Key: GEODE-3689
> URL: https://issues.apache.org/jira/browse/GEODE-3689
> Project: Geode
> Issue Type: Bug
> Components: gfsh, logging
>Reporter: Jens Deppe
>Priority: Major
> Labels: GeodeOperationAPI, observability
>
> When starting a server with gfsh, it does not honor a log4j configuration
> location by specifying {{--J=-Dlog4j.configurationFile=/path/to/log4j2.xml}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-3689) Unable to specify custom log4j configuration file from gfsh
[
https://issues.apache.org/jira/browse/GEODE-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-3689:
-
Labels: GeodeOperationAPI observability (was: observability)
> Unable to specify custom log4j configuration file from gfsh
> ---
>
> Key: GEODE-3689
> URL: https://issues.apache.org/jira/browse/GEODE-3689
> Project: Geode
> Issue Type: Bug
> Components: gfsh, logging
>Reporter: Jens Deppe
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, observability
>
> When starting a server with gfsh, it does not honor a log4j configuration
> location by specifying {{--J=-Dlog4j.configurationFile=/path/to/log4j2.xml}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6682) CI failure: NPE in org.apache.geode.management.internal.MBeanProxyInvocationHandler.newProxyInstance
[ https://issues.apache.org/jira/browse/GEODE-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-6682: - Labels: GeodeOperationAPI (was: ) > CI failure: NPE in > org.apache.geode.management.internal.MBeanProxyInvocationHandler.newProxyInstance > > > Key: GEODE-6682 > URL: https://issues.apache.org/jira/browse/GEODE-6682 > Project: Geode > Issue Type: Bug >Affects Versions: 1.6.0 >Reporter: Lynn Gallinat >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI > Time Spent: 20m > Remaining Estimate: 0h > > CLIENT vm_6_thr_14_managed_11_e89d343b-303b-4df0-4a2c-ffdf1b88a61a_400380 > ENDTASK[1] util.LogChecker.HydraTask_checkLogs > ERROR util.TestException: > /tmp/build/ae3c03f4/built-gemfire/test/gemfire/closed/pivotalgf-assembly/build/operationsTest/fedMBeanSet-0419-210256/managing_1_gemfire1_399019/system.log > contains java.lang.NullPointerException > at > org.apache.geode.management.internal.MBeanProxyInvocationHandler.newProxyInstance(MBeanProxyInvocationHandler.java:104) > at > org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:87) > at > org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137) > at > org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457) > at > org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > util.TestException: > /tmp/build/ae3c03f4/built-gemfire/test/gemfire/closed/pivotalgf-assembly/build/operationsTest/fedMBeanSet-0419-210256/managing_1_gemfire1_399019/system.log > contains java.lang.NullPointerException > at > org.apache.geode.management.internal.MBeanProxyInvocationHandler.newProxyInstance(MBeanProxyInvocationHandler.java:104) > at > org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:87) > at > org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137) > at > org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457) > at > org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at util.LogChecker.checkLogs(LogChecker.java:136) > at util.LogChecker.HydraTask_checkLogs(LogChecker.java:82) > 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:498) > at hydra.MethExecutor.execute(MethExecutor.java:181) > at hydra.MethExecutor.execute(MethExecutor.java:149) > at hydra.TestTask.execute(TestTask.java:192) > at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-6682) CI failure: NPE in org.apache.geode.management.internal.MBeanProxyInvocationHandler.newProxyInstance
[ https://issues.apache.org/jira/browse/GEODE-6682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-6682: Assignee: (was: Kirk Lund) > CI failure: NPE in > org.apache.geode.management.internal.MBeanProxyInvocationHandler.newProxyInstance > > > Key: GEODE-6682 > URL: https://issues.apache.org/jira/browse/GEODE-6682 > Project: Geode > Issue Type: Bug >Affects Versions: 1.6.0 >Reporter: Lynn Gallinat >Priority: Major > Labels: GeodeOperationAPI > Time Spent: 20m > Remaining Estimate: 0h > > CLIENT vm_6_thr_14_managed_11_e89d343b-303b-4df0-4a2c-ffdf1b88a61a_400380 > ENDTASK[1] util.LogChecker.HydraTask_checkLogs > ERROR util.TestException: > /tmp/build/ae3c03f4/built-gemfire/test/gemfire/closed/pivotalgf-assembly/build/operationsTest/fedMBeanSet-0419-210256/managing_1_gemfire1_399019/system.log > contains java.lang.NullPointerException > at > org.apache.geode.management.internal.MBeanProxyInvocationHandler.newProxyInstance(MBeanProxyInvocationHandler.java:104) > at > org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:87) > at > org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137) > at > org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457) > at > org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > util.TestException: > /tmp/build/ae3c03f4/built-gemfire/test/gemfire/closed/pivotalgf-assembly/build/operationsTest/fedMBeanSet-0419-210256/managing_1_gemfire1_399019/system.log > contains java.lang.NullPointerException > at > org.apache.geode.management.internal.MBeanProxyInvocationHandler.newProxyInstance(MBeanProxyInvocationHandler.java:104) > at > org.apache.geode.management.internal.MBeanProxyFactory.createProxy(MBeanProxyFactory.java:87) > at > org.apache.geode.management.internal.MBeanProxyFactory.createAllProxies(MBeanProxyFactory.java:137) > at > org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:457) > at > org.apache.geode.management.internal.FederatingManager$GIITask.call(FederatingManager.java:341) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at util.LogChecker.checkLogs(LogChecker.java:136) > at util.LogChecker.HydraTask_checkLogs(LogChecker.java:82) > 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:498) > at hydra.MethExecutor.execute(MethExecutor.java:181) > at hydra.MethExecutor.execute(MethExecutor.java:149) > at hydra.TestTask.execute(TestTask.java:192) > at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7824) Revert Public API change to ClientRegionFactory
[ https://issues.apache.org/jira/browse/GEODE-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-7824. -- Resolution: Won't Fix This change was previously reverted. > Revert Public API change to ClientRegionFactory > --- > > Key: GEODE-7824 > URL: https://issues.apache.org/jira/browse/GEODE-7824 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.13.0 >Reporter: Udo Kohlmeyer >Assignee: Kirk Lund >Priority: Major > > As per a commit to the ClientRegionFactory, the public API was changed. > Even though it was to get some consistency in the class, it does now deviate > from the released public API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6645) CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > testDataStoreEntryCount FAILED
[
https://issues.apache.org/jira/browse/GEODE-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-6645:
-
Labels: CI GeodeOperationAPI (was: CI)
> CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest >
> testDataStoreEntryCount FAILED
>
>
> Key: GEODE-6645
> URL: https://issues.apache.org/jira/browse/GEODE-6645
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.10.0
>Reporter: Lynn Hughes-Godfrey
>Assignee: Kirk Lund
>Priority: Major
> Labels: CI, GeodeOperationAPI
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/617
> {noformat}
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest >
> testDataStoreEntryCount FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run
> in VM 2 running on Host 1ee860aba5ac with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198)
> Caused by:
> org.junit.ComparisonFailure: expected:<[3]L> but was:<[2]L>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.validateEntryCount(PartitionedRegionStatsDUnitTest.java:267)
> at
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.lambda$testDataStoreEntryCount$bb17a952$18(PartitionedRegionStatsDUnitTest.java:198)
> {noformat}
> Artifacts are available here:
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-results/distributedTest/1555097363/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-artifacts/1555097363/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0176.tgz
> {noformat}
> Looking at this test, it goes through several phases of entry creation,
> destroy, destroy + put and GII (after adding a new member) for a partitioned
> region with redundantCopies=2. After adding the new member and forcing
> tombstone expiration, the newly created vm ends up with 1 less entry than
> expected (but the original two vms appear to have the expected number of
> entries (3)).
> Full stack
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run
> in VM 2 running on Host 1ee860aba5ac with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
>
[jira] [Assigned] (GEODE-6645) CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest > testDataStoreEntryCount FAILED
[
https://issues.apache.org/jira/browse/GEODE-6645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-6645:
Assignee: (was: Kirk Lund)
> CI: org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest >
> testDataStoreEntryCount FAILED
>
>
> Key: GEODE-6645
> URL: https://issues.apache.org/jira/browse/GEODE-6645
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.10.0
>Reporter: Lynn Hughes-Godfrey
>Priority: Major
> Labels: CI, GeodeOperationAPI
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/617
> {noformat}
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest >
> testDataStoreEntryCount FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run
> in VM 2 running on Host 1ee860aba5ac with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198)
> Caused by:
> org.junit.ComparisonFailure: expected:<[3]L> but was:<[2]L>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.validateEntryCount(PartitionedRegionStatsDUnitTest.java:267)
> at
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.lambda$testDataStoreEntryCount$bb17a952$18(PartitionedRegionStatsDUnitTest.java:198)
> {noformat}
> Artifacts are available here:
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-results/distributedTest/1555097363/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0176/test-artifacts/1555097363/distributedtestfiles-OpenJDK11-1.10.0-SNAPSHOT.0176.tgz
> {noformat}
> Looking at this test, it goes through several phases of entry creation,
> destroy, destroy + put and GII (after adding a new member) for a partitioned
> region with redundantCopies=2. After adding the new member and forcing
> tombstone expiration, the newly created vm ends up with 1 less entry than
> expected (but the original two vms appear to have the expected number of
> entries (3)).
> Full stack
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest$$Lambda$172/0x00084024dc40.run
> in VM 2 running on Host 1ee860aba5ac with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.PartitionedRegionStatsDUnitTest.testDataStoreEntryCount(PartitionedRegionStatsDUnitTest.java:198)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
>
[jira] [Updated] (GEODE-6070) CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
[
https://issues.apache.org/jira/browse/GEODE-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-6070:
-
Labels: GeodeOperationAPI flaky (was: GeodeCommons flaky)
> CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
> --
>
> Key: GEODE-6070
> URL: https://issues.apache.org/jira/browse/GEODE-6070
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.0
>Reporter: Helena Bales
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, flaky
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Failed with stacktrace:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest
> > testShutdownAll FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 302
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.3(server-1:496):41002 started at Thu Nov
> 15 19:47:58 UTC 2018: Message distribution has terminated
> {noformat}
> Test results can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-results/distributedTest/1542315851/classes/org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest.html#testShutdownAll
>
> Test Artifacts can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-artifacts/1542315851/distributedtestfiles-OpenJDK8-1.9.0-build.158.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8715) Redis INFO command 'Keyspace' section should not be present if no keys in database
[ https://issues.apache.org/jira/browse/GEODE-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Hutchison resolved GEODE-8715. --- Resolution: Fixed > Redis INFO command 'Keyspace' section should not be present if no keys in > database > -- > > Key: GEODE-8715 > URL: https://issues.apache.org/jira/browse/GEODE-8715 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: John Hutchison >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8357) Exhausting the high priority message thread pool can result in deadlock
[
https://issues.apache.org/jira/browse/GEODE-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-8357:
Assignee: (was: Kirk Lund)
> Exhausting the high priority message thread pool can result in deadlock
> ---
>
> Key: GEODE-8357
> URL: https://issues.apache.org/jira/browse/GEODE-8357
> Project: Geode
> Issue Type: Bug
> Components: messaging
>Affects Versions: 1.0.0-incubating, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0,
> 1.7.0, 1.8.0, 1.9.0, 1.10.0, 1.11.0, 1.12.0
>Reporter: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI
>
> The system property "DistributionManager.MAX_THREADS" default to 100:
> {noformat}
> int MAX_THREADS = Integer.getInteger("DistributionManager.MAX_THREADS", 100);
> {noformat}
> The system property used to be defined in geode-core
> ClusterDistributionManager and has moved to geode-core OperationExecutors.
> The value is used to limit ClusterOperationExecutors threadPool and
> highPriorityPool:
> {noformat}
> threadPool =
> CoreLoggingExecutors.newThreadPoolWithFeedStatistics("Pooled Message
> Processor ",
> thread -> stats.incProcessingThreadStarts(), this::doProcessingThread,
> MAX_THREADS, stats.getNormalPoolHelper(), threadMonitor,
> INCOMING_QUEUE_LIMIT, stats.getOverflowQueueHelper());
> highPriorityPool = CoreLoggingExecutors.newThreadPoolWithFeedStatistics(
> "Pooled High Priority Message Processor ",
> thread -> stats.incHighPriorityThreadStarts(), this::doHighPriorityThread,
> MAX_THREADS, stats.getHighPriorityPoolHelper(), threadMonitor,
> INCOMING_QUEUE_LIMIT, stats.getHighPriorityQueueHelper());
> {noformat}
> I have seen server startup hang when recovering lots of expired entries from
> disk while using PDX. The hang looks like a dlock request for the PDX lock is
> not receiving a response. Checking the value for the
> distributionStats#highPriorityQueueSize statistic (in VSD) shows the value
> maxed out and never dropping.
> The dlock response granting the PDX lock is stuck in the highPriorityQueue
> because there are no more highPriorityQueue threads available to process the
> response. All of the highPriorityQueue thread stack dumps show tasks such as
> recovering bucket from disk are blocked waiting for the PDX lock.
> Several changes could improve this situation, either in conjunction or
> individually:
> # improve observability to enable support to identify that this situation has
> occurred
> # increase MAX_THREADS default to 1000
> # automatically identify this situation and warn the user with a log statement
> # automatically prevent this situation
> # identify the messages that are prone to causing deadlocks and move them to
> a dedicated thread pool with a higher limit
> # move dlock messages to a new dedicated thread pool
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-6504) CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
[
https://issues.apache.org/jira/browse/GEODE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-6504:
Assignee: (was: Kirk Lund)
> CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
> -
>
> Key: GEODE-6504
> URL: https://issues.apache.org/jira/browse/GEODE-6504
> Project: Geode
> Issue Type: Bug
> Components: expiration
>Reporter: Mark Hanson
>Priority: Major
> Labels: GeodeOperationAPI
> Attachments: RegionExpirationIntegrationTest.log
>
>
> CI failure: see attached log.
>
> Failed on WindowsIntegrationTestOpenJDK11
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/272]
> {noformat}
> org.apache.geode.cache.RegionExpirationIntegrationTest >
> increaseRegionTtl[EMPTY] FAILED
> java.lang.AssertionError:
> Expecting:
> <7L>
> to be greater than or equal to:
> <8L>
> at
> org.apache.geode.cache.RegionExpirationIntegrationTest.increaseRegionTtl(RegionExpirationIntegrationTest.java:88)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6504) CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
[
https://issues.apache.org/jira/browse/GEODE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-6504:
-
Labels: GeodeOperationAPI (was: )
> CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
> -
>
> Key: GEODE-6504
> URL: https://issues.apache.org/jira/browse/GEODE-6504
> Project: Geode
> Issue Type: Bug
> Components: expiration
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI
> Attachments: RegionExpirationIntegrationTest.log
>
>
> CI failure: see attached log.
>
> Failed on WindowsIntegrationTestOpenJDK11
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/272]
> {noformat}
> org.apache.geode.cache.RegionExpirationIntegrationTest >
> increaseRegionTtl[EMPTY] FAILED
> java.lang.AssertionError:
> Expecting:
> <7L>
> to be greater than or equal to:
> <8L>
> at
> org.apache.geode.cache.RegionExpirationIntegrationTest.increaseRegionTtl(RegionExpirationIntegrationTest.java:88)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6903) CI Failure: GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection failed with Assertion
[
https://issues.apache.org/jira/browse/GEODE-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234884#comment-17234884
]
Kirk Lund commented on GEODE-6903:
--
[~eshu] I reassigned to you because I'm not really very familiar with
transactions. I did an overhaul of the test itself, but I'm not sure what I
would've done to cause it to fail (the bisect points to my commit). If you
think there's a problem in the test code that I should look at, please reassign
it back to me.
> CI Failure:
> GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection
> failed with Assertion
>
>
> Key: GEODE-6903
> URL: https://issues.apache.org/jira/browse/GEODE-6903
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.14.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: flaky
>
> {noformat}
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest
> > testExceptionHandlingGetConnection FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[2]>
> at sun.reflect.GeneratedConstructorAccessor26.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection(GemFireTransactionDataSourceIntegrationTest.java:141)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-results/integrationTest/1561170841/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-artifacts/1561170841/integrationtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0399.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-6903) CI Failure: GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection failed with Assertion
[
https://issues.apache.org/jira/browse/GEODE-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-6903:
Assignee: Eric Shu (was: Kirk Lund)
> CI Failure:
> GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection
> failed with Assertion
>
>
> Key: GEODE-6903
> URL: https://issues.apache.org/jira/browse/GEODE-6903
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.14.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: flaky
>
> {noformat}
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest
> > testExceptionHandlingGetConnection FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[2]>
> at sun.reflect.GeneratedConstructorAccessor26.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.datasource.GemFireTransactionDataSourceIntegrationTest.testExceptionHandlingGetConnection(GemFireTransactionDataSourceIntegrationTest.java:141)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-results/integrationTest/1561170841/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0399/test-artifacts/1561170841/integrationtestfiles-OpenJDK8-1.10.0-SNAPSHOT.0399.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7016) CI failure: ServerStartupRedundancyRecoveryNotificationTest > startupReportsOnlineOnlyAfterRedundancyRestored FAILED
[
https://issues.apache.org/jira/browse/GEODE-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-7016.
--
Fix Version/s: 1.14.0
Resolution: Fixed
> CI failure: ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
>
>
> Key: GEODE-7016
> URL: https://issues.apache.org/jira/browse/GEODE-7016
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.10.0
>Reporter: Anilkumar Gingade
>Assignee: Kirk Lund
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> {noformat}
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest >
> startupReportsOnlineOnlyAfterRedundancyRestored FAILED
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.startupReportsOnlineOnlyAfterRedundancyRestored(ServerStartupRedundancyRecoveryNotificationTest.java:142)
> org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
> at
> org.apache.geode.launchers.ServerStartupRedundancyRecoveryNotificationTest.stopAllMembers(ServerStartupRedundancyRecoveryNotificationTest.java:128)
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/AcceptanceTestOpenJDK8/builds/797
> Test report artifacts from this job are available at:
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.9.0-build.0258/test-artifacts/1564078711/acceptancetestfiles-OpenJDK8-9.9.0-build.0258.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[
https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234874#comment-17234874
]
ASF GitHub Bot commented on GEODE-8711:
---
ringles commented on a change in pull request #5749:
URL: https://github.com/apache/geode/pull/5749#discussion_r526307860
##
File path:
geode-redis/src/integrationTest/java/org/apache/geode/redis/internal/executor/server/AbstractSlowlogIntegrationTest.java
##
@@ -0,0 +1,146 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.executor.server;
+
+import static org.assertj.core.api.Assertions.assertThat;
+import static org.assertj.core.api.Assertions.assertThatThrownBy;
+
+import java.util.List;
+
+import org.junit.After;
+import org.junit.Before;
+import org.junit.Test;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Protocol;
+import redis.clients.jedis.util.Slowlog;
+
+import org.apache.geode.test.awaitility.GeodeAwaitility;
+import org.apache.geode.test.dunit.rules.RedisPortSupplier;
+
+public abstract class AbstractSlowlogIntegrationTest implements
RedisPortSupplier {
+
+ private Jedis jedis;
+ private static final int REDIS_CLIENT_TIMEOUT =
+ Math.toIntExact(GeodeAwaitility.getTimeout().toMillis());
+
+ @Before
+ public void setUp() {
+jedis = new Jedis("localhost", getPort(), REDIS_CLIENT_TIMEOUT);
+ }
+
+ @After
+ public void tearDown() {
+jedis.close();
+ }
+
+ abstract int getExposedPort();
+
+ @Test
+ public void shouldReturnEmptyArray_whenGetSubcommandSpecified() {
+List actualResult = jedis.slowlogGet();
+
+assertThat(actualResult.size()).isEqualTo(0);
Review comment:
Done!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Enable SLOWLOG command to support Redis monitoring tools
>
>
> Key: GEODE-8711
> URL: https://issues.apache.org/jira/browse/GEODE-8711
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Raymond Ingles
>Priority: Major
> Labels: pull-request-available
>
> The Redis SLOWLOG command tracks slow-executing commands. This will implement
> a placeholder to prevent errors in tools like Datadog or Redis Insights.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8708) CI failure in build-geode-benchmarks-image
[
https://issues.apache.org/jira/browse/GEODE-8708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Houghton resolved GEODE-8708.
Fix Version/s: 1.14.0
Resolution: Fixed
> CI failure in build-geode-benchmarks-image
> --
>
> Key: GEODE-8708
> URL: https://issues.apache.org/jira/browse/GEODE-8708
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Kamilla Aslami
>Assignee: Robert Houghton
>Priority: Major
> Fix For: 1.14.0
>
>
>
> Geode-benchmarks build fails with
>
> {noformat}
> Packer experienced an authentication error when trying to connect via SSH.
> This can happen if your username/password are wrong. You may want to
> double-check your credentials as part of your debugging process.{noformat}
>
> Full build-image log:
> {noformat}
> /tmp/build/2ebbeb81/geode-benchmarks-image/infrastructure/scripts/aws/image
> /tmp/build/2ebbeb81
> geode-benchmarks output will be in this color.==> geode-benchmarks:
> Prevalidating AMI Name: geode-benchmarks-1605228588
> geode-benchmarks: Found Image ID: ami-08f6a7b1c02ad4ece
> ==> geode-benchmarks: Creating temporary keypair:
> packer_5fadd82d-f9b2-0a6d-b69d-1f1298b31866
> ==> geode-benchmarks: Creating temporary security group for this instance:
> packer_5fadd82f-006b-570a-43dd-801c4d305269
> ==> geode-benchmarks: Authorizing access to port 22 from [0.0.0.0/0] in the
> temporary security groups...
> ==> geode-benchmarks: Launching a source AWS instance...
> ==> geode-benchmarks: Adding tags to source instance
> geode-benchmarks: Adding tag: "Name": "Packer Builder"
> geode-benchmarks: Instance ID: i-0590e362acd08ed74
> ==> geode-benchmarks: Waiting for instance (i-0590e362acd08ed74) to become
> ready...
> ==> geode-benchmarks: Using ssh communicator to connect: 18.236.218.182
> ==> geode-benchmarks: Waiting for SSH to become available...
> ==> geode-benchmarks: Error waiting for SSH: Packer experienced an
> authentication error when trying to connect via SSH. This can happen if your
> username/password are wrong. You may want to double-check your credentials as
> part of your debugging process. original error: ssh: handshake failed: ssh:
> unable to authenticate, attempted methods [publickey none], no supported
> methods remain
> ==> geode-benchmarks: Terminating the source AWS instance...
> ==> geode-benchmarks: Cleaning up any extra volumes...
> ==> geode-benchmarks: No volumes to clean up, skipping
> ==> geode-benchmarks: Deleting temporary security group...
> ==> geode-benchmarks: Deleting temporary keypair...
> Build 'geode-benchmarks' errored: Packer experienced an authentication error
> when trying to connect via SSH. This can happen if your username/password are
> wrong. You may want to double-check your credentials as part of your
> debugging process. original error: ssh: handshake failed: ssh: unable to
> authenticate, attempted methods [publickey none], no supported methods
> remain==> Some builds didn't complete successfully and had errors:
> --> geode-benchmarks: Packer experienced an authentication error when trying
> to connect via SSH. This can happen if your username/password are wrong. You
> may want to double-check your credentials as part of your debugging process.
> original error: ssh: handshake failed: ssh: unable to authenticate, attempted
> methods [publickey none], no supported methods remain==> Builds finished but
> no artifacts were created.{noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[ https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234866#comment-17234866 ] ASF GitHub Bot commented on GEODE-8711: --- lgtm-com[bot] commented on pull request #5749: URL: https://github.com/apache/geode/pull/5749#issuecomment-729847497 This pull request **introduces 1 alert** when merging dec4b25ee599a87ab54e88f061de284663c32714 into 6dae93976c14e2c60fed0cd32942ee63bf2b7521 - [view on LGTM.com](https://lgtm.com/projects/g/apache/geode/rev/pr-66c6dc830539c6ef3a7ce4c1629d29c64d3bedca) **new alerts:** * 1 for Useless comparison test This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Enable SLOWLOG command to support Redis monitoring tools > > > Key: GEODE-8711 > URL: https://issues.apache.org/jira/browse/GEODE-8711 > Project: Geode > Issue Type: Improvement > Components: redis >Affects Versions: 1.14.0 >Reporter: Raymond Ingles >Priority: Major > Labels: pull-request-available > > The Redis SLOWLOG command tracks slow-executing commands. This will implement > a placeholder to prevent errors in tools like Datadog or Redis Insights. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8521) Add P2P message reader threads to thread monitoring
[ https://issues.apache.org/jira/browse/GEODE-8521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-8521: Assignee: Darrel Schneider (was: Kirk Lund) > Add P2P message reader threads to thread monitoring > --- > > Key: GEODE-8521 > URL: https://issues.apache.org/jira/browse/GEODE-8521 > Project: Geode > Issue Type: Wish > Components: messaging >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Add P2P message reader threads to thread monitoring to help with identifying > stuck P2P message readers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[
https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234832#comment-17234832
]
ASF GitHub Bot commented on GEODE-8711:
---
ringles commented on a change in pull request #5749:
URL: https://github.com/apache/geode/pull/5749#discussion_r526254741
##
File path:
geode-redis/src/integrationTest/java/org/apache/geode/redis/internal/executor/server/SlowlogIntegrationTest.java
##
@@ -0,0 +1,39 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.executor.server;
+
+import static org.apache.geode.distributed.ConfigurationProperties.LOG_LEVEL;
+
+import org.junit.ClassRule;
+
+import org.apache.geode.redis.GeodeRedisServerRule;
+
+public class SlowlogIntegrationTest extends AbstractSlowlogIntegrationTest {
+
+ @ClassRule
+ public static GeodeRedisServerRule server = new GeodeRedisServerRule()
+ .withProperty(LOG_LEVEL, "info");
+
+ @Override
+ public int getPort() {
+return server.getPort();
+ }
+
+ @Override
+ public int getExposedPort() {
+return getPort();
+ }
Review comment:
Also done.
##
File path:
geode-redis/src/acceptanceTest/java/org/apache/geode/redis/internal/executor/server/SlowlogNativeRedisAcceptanceTest.java
##
@@ -0,0 +1,36 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.executor.server;
+
+import org.junit.ClassRule;
+
+import org.apache.geode.NativeRedisTestRule;
+
+public class SlowlogNativeRedisAcceptanceTest extends
AbstractSlowlogIntegrationTest {
+
+ @ClassRule
+ public static NativeRedisTestRule redis = new NativeRedisTestRule();
+
+ @Override
+ public int getPort() {
+return redis.getPort();
+ }
+
+ @Override
+ int getExposedPort() {
+return redis.getExposedPort();
+ }
Review comment:
Done.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Enable SLOWLOG command to support Redis monitoring tools
>
>
> Key: GEODE-8711
> URL: https://issues.apache.org/jira/browse/GEODE-8711
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Raymond Ingles
>Priority: Major
> Labels: pull-request-available
>
> The Redis SLOWLOG command tracks slow-executing commands. This will implement
> a placeholder to prevent errors in tools like Datadog or Redis Insights.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[
https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234833#comment-17234833
]
ASF GitHub Bot commented on GEODE-8711:
---
ringles commented on a change in pull request #5749:
URL: https://github.com/apache/geode/pull/5749#discussion_r526255026
##
File path:
geode-redis/src/integrationTest/java/org/apache/geode/redis/internal/executor/server/AbstractSlowlogIntegrationTest.java
##
@@ -0,0 +1,146 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.executor.server;
+
+import static org.assertj.core.api.Assertions.assertThat;
+import static org.assertj.core.api.Assertions.assertThatThrownBy;
+
+import java.util.List;
+
+import org.junit.After;
+import org.junit.Before;
+import org.junit.Test;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Protocol;
+import redis.clients.jedis.util.Slowlog;
+
+import org.apache.geode.test.awaitility.GeodeAwaitility;
+import org.apache.geode.test.dunit.rules.RedisPortSupplier;
+
+public abstract class AbstractSlowlogIntegrationTest implements
RedisPortSupplier {
+
+ private Jedis jedis;
+ private static final int REDIS_CLIENT_TIMEOUT =
+ Math.toIntExact(GeodeAwaitility.getTimeout().toMillis());
+
+ @Before
+ public void setUp() {
+jedis = new Jedis("localhost", getPort(), REDIS_CLIENT_TIMEOUT);
+ }
+
+ @After
+ public void tearDown() {
+jedis.close();
+ }
+
+ abstract int getExposedPort();
Review comment:
Done.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Enable SLOWLOG command to support Redis monitoring tools
>
>
> Key: GEODE-8711
> URL: https://issues.apache.org/jira/browse/GEODE-8711
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Raymond Ingles
>Priority: Major
> Labels: pull-request-available
>
> The Redis SLOWLOG command tracks slow-executing commands. This will implement
> a placeholder to prevent errors in tools like Datadog or Redis Insights.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[
https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234829#comment-17234829
]
ASF GitHub Bot commented on GEODE-8711:
---
ringles commented on a change in pull request #5749:
URL: https://github.com/apache/geode/pull/5749#discussion_r526252722
##
File path:
geode-redis/src/main/java/org/apache/geode/redis/internal/ParameterRequirements/SlowlogParameterRequirements.java
##
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.ParameterRequirements;
+
+import static org.apache.geode.redis.internal.RedisConstants.ERROR_NOT_INTEGER;
+import static
org.apache.geode.redis.internal.RedisConstants.ERROR_UNKNOWN_SLOWLOG_SUBCOMMAND;
+
+import org.apache.geode.redis.internal.netty.Command;
+import org.apache.geode.redis.internal.netty.ExecutionHandlerContext;
+
+public class SlowlogParameterRequirements implements ParameterRequirements {
+ @Override
+ public void checkParameters(Command command, ExecutionHandlerContext
context) {
+int numberOfArguments = command.getProcessedCommand().size();
+
+if (numberOfArguments < 2) {
+ throw new
RedisParametersMismatchException(command.wrongNumberOfArgumentsErrorMessage());
+} else if (numberOfArguments == 2) {
+ confirmKnownSubcommands(command);
+} else if (numberOfArguments == 3) {
+ confirmArgumentsToGetSubcommand(command);
+} else if (numberOfArguments > 3) {
+ throw new RedisParametersMismatchException(
+ String.format(ERROR_UNKNOWN_SLOWLOG_SUBCOMMAND,
command.getStringKey()));
+}
+ }
+
+ private void confirmKnownSubcommands(Command command) {
+if (!command.getStringKey().toLowerCase().equals("reset") &&
+!command.getStringKey().toLowerCase().equals("len") &&
+!command.getStringKey().toLowerCase().equals("get")) {
+ throw new RedisParametersMismatchException(
+ String.format(ERROR_UNKNOWN_SLOWLOG_SUBCOMMAND,
command.getStringKey()));
+}
+ }
+
+ private void confirmArgumentsToGetSubcommand(Command command) {
+if (!command.getStringKey().toLowerCase().equals("get")) {
+ throw new RedisParametersMismatchException(
+ String.format(ERROR_UNKNOWN_SLOWLOG_SUBCOMMAND,
command.getStringKey()));
+}
+try {
+ Integer.parseInt(new String(command.getProcessedCommand().get(2)));
Review comment:
Test added, and passing.
##
File path: geode-redis/README.md
##
@@ -200,16 +200,16 @@ start server \
| | SINTER
| CLUSTER INFO |
| | SINTERSTORE
| CLUSTER KEYSLOT |
| | SISMEMBER
| CLUSTER MEET |
-| | SMOVE
| CLUSTER MYID |
-| | SPOP
| CLUSTER NODES |
-| | SRANDMEMBER
| CLUSTER REPLICAS |
-| | SSCAN
| CLUSTER REPLICATE |
-| | STRLEN
| CLUSTER RESET |
-| | SUNION
| CLUSTER SAVECONFIG|
-| | SUNIONSTORE
| CLUSTER SET-CONFIG-EPOCH |
-| | TIME
| CLUSTER SETSLOT |
-| | UNLINK [1]
| CLUSTER SLAVES|
-| |
| CLUSTER SLOTS |
+| | SLOWLOG
[jira] [Commented] (GEODE-8721) member that should become coordinator never detects loss of current coordinator
[
https://issues.apache.org/jira/browse/GEODE-8721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234747#comment-17234747
]
ASF GitHub Bot commented on GEODE-8721:
---
bschuchardt commented on a change in pull request #5758:
URL: https://github.com/apache/geode/pull/5758#discussion_r526195442
##
File path:
geode-membership/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
##
@@ -130,7 +130,7 @@
public static final long MEMBER_SUSPECT_COLLECTION_INTERVAL =
Long.getLong("geode.suspect-member-collection-interval", 200);
- private volatile long currentTimeStamp;
+ volatile long currentTimeStamp;
Review comment:
seems the same as membersInFinalCheck to me, allowing a test subclass to
access it
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> member that should become coordinator never detects loss of current
> coordinator
> ---
>
> Key: GEODE-8721
> URL: https://issues.apache.org/jira/browse/GEODE-8721
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.14.0
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: pull-request-available, release-blocker
>
> During a network partition a server that should have become membership
> coordinator and shut down its side of the partition never detected the loss
> of a server on the other side of the partition. Instead it continually
> performed availability checks on that other server and the checks passed.
> Its log file had continually increasing timestamps for when it claimed the
> other server had contacted it, which was not possible due to the network
> partition (which was formed through iptable manipulation).
> At least one other server on its side of the network partition was doing the
> same thing. It looks like they were interfering with each others
> availability checks in some way.
> {noformat}
> locatorp1_26023/system.log: [info 2020/10/20 22:23:16.227 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:12 PDT 2020
> locatorp1_26023/system.log: [info 2020/10/20 22:23:16.228 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Availability check passed
> for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> bridgep1_25995/system.log: [info 2020/10/20 22:23:16.229 PDT receiver,rs-F21040449a0i3large-72-61636> tid=0x23] No longer suspecting
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> bridgep1_25998/system.log: [info 2020/10/20 22:23:17.212 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:14 PDT 2020
> bridgep1_25998/system.log: [info 2020/10/20 22:23:17.213 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Availability check passed
> for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> locatorp1_26023/system.log: [info 2020/10/20 22:23:17.232 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Performing availability
> check for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> reason=Unable to send messages to this member via JGroups
> bridgep1_25998/system.log: [info 2020/10/20 22:23:18.215 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Performing availability
> check for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> reason=Unable to send messages to this member via JGroups
> bridgep1_25995/system.log: [info 2020/10/20 22:23:21.006 PDT Timer-2,rs-F21040449a0i3large-72-61636> tid=0x21] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:16 PDT 2020
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[
https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234745#comment-17234745
]
ASF GitHub Bot commented on GEODE-8711:
---
ringles commented on a change in pull request #5749:
URL: https://github.com/apache/geode/pull/5749#discussion_r526194999
##
File path:
geode-redis/src/main/java/org/apache/geode/redis/internal/ParameterRequirements/SlowlogParameterRequirements.java
##
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.ParameterRequirements;
+
+import static org.apache.geode.redis.internal.RedisConstants.ERROR_NOT_INTEGER;
+import static
org.apache.geode.redis.internal.RedisConstants.ERROR_UNKNOWN_SLOWLOG_SUBCOMMAND;
+
+import org.apache.geode.redis.internal.netty.Command;
+import org.apache.geode.redis.internal.netty.ExecutionHandlerContext;
+
+public class SlowlogParameterRequirements implements ParameterRequirements {
+ @Override
+ public void checkParameters(Command command, ExecutionHandlerContext
context) {
+int numberOfArguments = command.getProcessedCommand().size();
+
+if (numberOfArguments < 2) {
+ throw new
RedisParametersMismatchException(command.wrongNumberOfArgumentsErrorMessage());
+} else if (numberOfArguments == 2) {
+ confirmKnownSubcommands(command);
+} else if (numberOfArguments == 3) {
+ confirmArgumentsToGetSubcommand(command);
+} else if (numberOfArguments > 3) {
Review comment:
Functionally it's the same. I agree with LGTM that it's technically
redundant... but I think it's marginally more readable, making clear to a human
reading it what the intent is. Perhaps we could add a comment instead?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Enable SLOWLOG command to support Redis monitoring tools
>
>
> Key: GEODE-8711
> URL: https://issues.apache.org/jira/browse/GEODE-8711
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Affects Versions: 1.14.0
>Reporter: Raymond Ingles
>Priority: Major
> Labels: pull-request-available
>
> The Redis SLOWLOG command tracks slow-executing commands. This will implement
> a placeholder to prevent errors in tools like Datadog or Redis Insights.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8721) member that should become coordinator never detects loss of current coordinator
[
https://issues.apache.org/jira/browse/GEODE-8721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234744#comment-17234744
]
ASF GitHub Bot commented on GEODE-8721:
---
bschuchardt commented on a change in pull request #5758:
URL: https://github.com/apache/geode/pull/5758#discussion_r526194440
##
File path:
geode-membership/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
##
@@ -152,7 +152,7 @@
/**
* Members undergoing final checks
*/
- private final List membersInFinalCheck =
+ final List membersInFinalCheck =
Review comment:
yes
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> member that should become coordinator never detects loss of current
> coordinator
> ---
>
> Key: GEODE-8721
> URL: https://issues.apache.org/jira/browse/GEODE-8721
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.14.0
>Reporter: Bruce J Schuchardt
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: pull-request-available, release-blocker
>
> During a network partition a server that should have become membership
> coordinator and shut down its side of the partition never detected the loss
> of a server on the other side of the partition. Instead it continually
> performed availability checks on that other server and the checks passed.
> Its log file had continually increasing timestamps for when it claimed the
> other server had contacted it, which was not possible due to the network
> partition (which was formed through iptable manipulation).
> At least one other server on its side of the network partition was doing the
> same thing. It looks like they were interfering with each others
> availability checks in some way.
> {noformat}
> locatorp1_26023/system.log: [info 2020/10/20 22:23:16.227 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:12 PDT 2020
> locatorp1_26023/system.log: [info 2020/10/20 22:23:16.228 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Availability check passed
> for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> bridgep1_25995/system.log: [info 2020/10/20 22:23:16.229 PDT receiver,rs-F21040449a0i3large-72-61636> tid=0x23] No longer suspecting
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> bridgep1_25998/system.log: [info 2020/10/20 22:23:17.212 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:14 PDT 2020
> bridgep1_25998/system.log: [info 2020/10/20 22:23:17.213 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Availability check passed
> for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> locatorp1_26023/system.log: [info 2020/10/20 22:23:17.232 PDT Timer-2,rs-F21040449a0i3large-72-47481> tid=0x23] Performing availability
> check for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> reason=Unable to send messages to this member via JGroups
> bridgep1_25998/system.log: [info 2020/10/20 22:23:18.215 PDT Timer-2,rs-F21040449a0i3large-72-2074> tid=0x21] Performing availability
> check for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000
> reason=Unable to send messages to this member via JGroups
> bridgep1_25995/system.log: [info 2020/10/20 22:23:21.006 PDT Timer-2,rs-F21040449a0i3large-72-61636> tid=0x21] Availability check detected
> recent message traffic for suspect member
> 10.32.109.233(locatorp2_host2_21762:21762:locator):41000 at time Tue
> Oct 20 22:23:16 PDT 2020
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8711) Enable SLOWLOG command to support Redis monitoring tools
[
https://issues.apache.org/jira/browse/GEODE-8711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234732#comment-17234732
]
ASF GitHub Bot commented on GEODE-8711:
---
sabbey37 commented on a change in pull request #5749:
URL: https://github.com/apache/geode/pull/5749#discussion_r526168133
##
File path:
geode-redis/src/integrationTest/java/org/apache/geode/redis/internal/executor/server/AbstractSlowlogIntegrationTest.java
##
@@ -0,0 +1,146 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.executor.server;
+
+import static org.assertj.core.api.Assertions.assertThat;
+import static org.assertj.core.api.Assertions.assertThatThrownBy;
+
+import java.util.List;
+
+import org.junit.After;
+import org.junit.Before;
+import org.junit.Test;
+import redis.clients.jedis.Jedis;
+import redis.clients.jedis.Protocol;
+import redis.clients.jedis.util.Slowlog;
+
+import org.apache.geode.test.awaitility.GeodeAwaitility;
+import org.apache.geode.test.dunit.rules.RedisPortSupplier;
+
+public abstract class AbstractSlowlogIntegrationTest implements
RedisPortSupplier {
+
+ private Jedis jedis;
+ private static final int REDIS_CLIENT_TIMEOUT =
+ Math.toIntExact(GeodeAwaitility.getTimeout().toMillis());
+
+ @Before
+ public void setUp() {
+jedis = new Jedis("localhost", getPort(), REDIS_CLIENT_TIMEOUT);
+ }
+
+ @After
+ public void tearDown() {
+jedis.close();
+ }
+
+ abstract int getExposedPort();
+
+ @Test
+ public void shouldReturnEmptyArray_whenGetSubcommandSpecified() {
+List actualResult = jedis.slowlogGet();
+
+assertThat(actualResult.size()).isEqualTo(0);
Review comment:
We could use `assertThat(actualResult).isEmpty()` here (and for the ones
below) . This might be preferable because if the result is not empty, the
error message will display the contents of the array rather than just the
length. Sorry I didn't notice this in the first review.
##
File path:
geode-redis/src/main/java/org/apache/geode/redis/internal/ParameterRequirements/SlowlogParameterRequirements.java
##
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
contributor license
+ * agreements. See the NOTICE file distributed with this work for additional
information regarding
+ * copyright ownership. The ASF licenses this file to You under the Apache
License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance with the
License. You may obtain a
+ * copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
distributed under the License
+ * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express
+ * or implied. See the License for the specific language governing permissions
and limitations under
+ * the License.
+ */
+
+package org.apache.geode.redis.internal.ParameterRequirements;
+
+import static org.apache.geode.redis.internal.RedisConstants.ERROR_NOT_INTEGER;
+import static
org.apache.geode.redis.internal.RedisConstants.ERROR_UNKNOWN_SLOWLOG_SUBCOMMAND;
+
+import org.apache.geode.redis.internal.netty.Command;
+import org.apache.geode.redis.internal.netty.ExecutionHandlerContext;
+
+public class SlowlogParameterRequirements implements ParameterRequirements {
+ @Override
+ public void checkParameters(Command command, ExecutionHandlerContext
context) {
+int numberOfArguments = command.getProcessedCommand().size();
+
+if (numberOfArguments < 2) {
+ throw new
RedisParametersMismatchException(command.wrongNumberOfArgumentsErrorMessage());
+} else if (numberOfArguments == 2) {
+ confirmKnownSubcommands(command);
+} else if (numberOfArguments == 3) {
+ confirmArgumentsToGetSubcommand(command);
+} else if (numberOfArguments > 3) {
Review comment:
I think LGTM is suggesting that this could just be an `else`, instead of
an `else if`
##
File path: geode-redis/README.md
##
@@ -200,16 +200,16 @@ start server \
| | SINTER
[jira] [Commented] (GEODE-8573) SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
[
https://issues.apache.org/jira/browse/GEODE-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234716#comment-17234716
]
Geode Integration commented on GEODE-8573:
--
Seen in [DistributedTestOpenJDK8
#636|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/636]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0498/test-results/distributedTest/1605680968/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0498/test-artifacts/1605680968/distributedtestfiles-OpenJDK8-1.14.0-build.0498.tgz].
> SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
>
>
> Key: GEODE-8573
> URL: https://issues.apache.org/jira/browse/GEODE-8573
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/521]
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> > testRestartSerialGatewaySendersWhilePutting[1: numDispatchers=3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest$$Lambda$356/426344166.run
> in VM 5 running on Host 538fd3213f62 with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> that uses org.apache.geode.internal.cache.wan.InternalGatewaySender,
> org.apache.geode.internal.cache.wan.InternalGatewaySenderint [Sender
> statistics unprocessed event map size] expected:<[0]> but was:<[3]> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.validateSecondaryQueueSizeStat(SerialGatewaySenderOperationsDistributedTest.java:1216)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$testRestartSerialGatewaySendersWhilePutting$bb17a952$23(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.junit.ComparisonFailure: [Sender statistics unprocessed event
> map size] expected:<[0]> but was:<[3]>
> at
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$validateSecondaryQueueSizeStat$8(SerialGatewaySenderOperationsDistributedTest.java:1219)
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-results/distributedTest/1601774166/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-artifacts/1601774166/distributedtestfiles-OpenJDK8-1.14.0-build.0389.tgz]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8573) SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
[
https://issues.apache.org/jira/browse/GEODE-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234717#comment-17234717
]
Geode Integration commented on GEODE-8573:
--
Seen in [DistributedTestOpenJDK8
#637|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/637]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0498/test-results/distributedTest/1605689411/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0498/test-artifacts/1605689411/distributedtestfiles-OpenJDK8-1.14.0-build.0498.tgz].
> SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
>
>
> Key: GEODE-8573
> URL: https://issues.apache.org/jira/browse/GEODE-8573
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/521]
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> > testRestartSerialGatewaySendersWhilePutting[1: numDispatchers=3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest$$Lambda$356/426344166.run
> in VM 5 running on Host 538fd3213f62 with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> that uses org.apache.geode.internal.cache.wan.InternalGatewaySender,
> org.apache.geode.internal.cache.wan.InternalGatewaySenderint [Sender
> statistics unprocessed event map size] expected:<[0]> but was:<[3]> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.validateSecondaryQueueSizeStat(SerialGatewaySenderOperationsDistributedTest.java:1216)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$testRestartSerialGatewaySendersWhilePutting$bb17a952$23(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.junit.ComparisonFailure: [Sender statistics unprocessed event
> map size] expected:<[0]> but was:<[3]>
> at
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$validateSecondaryQueueSizeStat$8(SerialGatewaySenderOperationsDistributedTest.java:1219)
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-results/distributedTest/1601774166/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-artifacts/1601774166/distributedtestfiles-OpenJDK8-1.14.0-build.0389.tgz]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8573) SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
[
https://issues.apache.org/jira/browse/GEODE-8573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234715#comment-17234715
]
Geode Integration commented on GEODE-8573:
--
Seen in [DistributedTestOpenJDK8
#635|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/635]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0498/test-results/distributedTest/1605668668/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0498/test-artifacts/1605668668/distributedtestfiles-OpenJDK8-1.14.0-build.0498.tgz].
> SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting
>
>
> Key: GEODE-8573
> URL: https://issues.apache.org/jira/browse/GEODE-8573
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.14.0
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/521]
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> > testRestartSerialGatewaySendersWhilePutting[1: numDispatchers=3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest$$Lambda$356/426344166.run
> in VM 5 running on Host 538fd3213f62 with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:620)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.testRestartSerialGatewaySendersWhilePutting(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest
> that uses org.apache.geode.internal.cache.wan.InternalGatewaySender,
> org.apache.geode.internal.cache.wan.InternalGatewaySenderint [Sender
> statistics unprocessed event map size] expected:<[0]> but was:<[3]> within 5
> minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.validateSecondaryQueueSizeStat(SerialGatewaySenderOperationsDistributedTest.java:1216)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$testRestartSerialGatewaySendersWhilePutting$bb17a952$23(SerialGatewaySenderOperationsDistributedTest.java:407)
> Caused by:
> org.junit.ComparisonFailure: [Sender statistics unprocessed event
> map size] expected:<[0]> but was:<[3]>
> at
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDistributedTest.lambda$validateSecondaryQueueSizeStat$8(SerialGatewaySenderOperationsDistributedTest.java:1219)
> {noformat}
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-results/distributedTest/1601774166/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0389/test-artifacts/1601774166/distributedtestfiles-OpenJDK8-1.14.0-build.0389.tgz]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8537) Memory increases whenever LRU eviction is enabled
[ https://issues.apache.org/jira/browse/GEODE-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234694#comment-17234694 ] ASF GitHub Bot commented on GEODE-8537: --- codecov-io edited a comment on pull request #687: URL: https://github.com/apache/geode-native/pull/687#issuecomment-729161638 # [Codecov](https://codecov.io/gh/apache/geode-native/pull/687?src=pr=h1) Report > Merging [#687](https://codecov.io/gh/apache/geode-native/pull/687?src=pr=desc) (f57fbc7) into [develop](https://codecov.io/gh/apache/geode-native/commit/96faa995c4e61e464f5366693a1d2616f2c28508?el=desc) (96faa99) will **decrease** coverage by `0.10%`. > The diff coverage is `89.42%`. [](https://codecov.io/gh/apache/geode-native/pull/687?src=pr=tree) ```diff @@ Coverage Diff @@ ## develop #687 +/- ## === - Coverage74.10% 74.00% -0.11% === Files 644 644 Lines5108450949 -135 === - Hits 3785437703 -151 - Misses 1323013246 +16 ``` | [Impacted Files](https://codecov.io/gh/apache/geode-native/pull/687?src=pr=tree) | Coverage Δ | | |---|---|---| | [cppcache/integration-test/testRegionMap.cpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvaW50ZWdyYXRpb24tdGVzdC90ZXN0UmVnaW9uTWFwLmNwcA==) | `100.00% <ø> (ø)` | | | [cppcache/src/EvictionController.hpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvc3JjL0V2aWN0aW9uQ29udHJvbGxlci5ocHA=) | `100.00% <ø> (ø)` | | | [cppcache/src/LRUEntriesMap.hpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvc3JjL0xSVUVudHJpZXNNYXAuaHBw) | `76.92% <ø> (ø)` | | | [cppcache/src/LRUExpMapEntry.hpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvc3JjL0xSVUV4cE1hcEVudHJ5LmhwcA==) | `11.76% <ø> (ø)` | | | [cppcache/src/LRUMapEntry.hpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvc3JjL0xSVU1hcEVudHJ5LmhwcA==) | `80.00% <ø> (ø)` | | | [cppcache/src/LocalRegion.hpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvc3JjL0xvY2FsUmVnaW9uLmhwcA==) | `86.36% <ø> (ø)` | | | [cppcache/src/RegionInternal.hpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvc3JjL1JlZ2lvbkludGVybmFsLmhwcA==) | `100.00% <ø> (ø)` | | | [cppcache/test/mock/MapEntryImplMock.hpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvdGVzdC9tb2NrL01hcEVudHJ5SW1wbE1vY2suaHBw) | `44.44% <44.44%> (ø)` | | | [cppcache/src/LRUEntriesMap.cpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvc3JjL0xSVUVudHJpZXNNYXAuY3Bw) | `60.08% <63.63%> (+8.10%)` | :arrow_up: | | [cppcache/src/LRUEntryProperties.hpp](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree#diff-Y3BwY2FjaGUvc3JjL0xSVUVudHJ5UHJvcGVydGllcy5ocHA=) | `88.88% <88.88%> (ø)` | | | ... and [23 more](https://codecov.io/gh/apache/geode-native/pull/687/diff?src=pr=tree-more) | | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/geode-native/pull/687?src=pr=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/geode-native/pull/687?src=pr=footer). Last update [96faa99...f57fbc7](https://codecov.io/gh/apache/geode-native/pull/687?src=pr=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Memory increases whenever LRU eviction is enabled > - > > Key: GEODE-8537 > URL: https://issues.apache.org/jira/browse/GEODE-8537 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.13.0 >Reporter: Mario Salazar de Torres >Assignee: Mario Salazar de Torres >Priority: Major > Labels: pull-request-available > Attachments:
[jira] [Commented] (GEODE-7822) MemoryThresholdsOffHeapDUnitTest has failures
[
https://issues.apache.org/jira/browse/GEODE-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234689#comment-17234689
]
Raymond Ingles commented on GEODE-7822:
---
CI failure:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634
{code:java}
> Task :geode-core:distributedTestClasses
[18:29:18|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:653]
> Task :geode-core:distributedTest
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:654]
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:655]
org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
testDRLoadRejection FAILED
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:656]
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$17.run in VM
1 running on Host f2f220a79b40 with 4 VMs
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:657]
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:658]
at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:659]
at
org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testDRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:664)
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:660]
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:661]
Caused by:
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:662]
java.lang.AssertionError
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:663]
at org.junit.Assert.fail(Assert.java:87)
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:664]
at org.junit.Assert.assertTrue(Assert.java:42)
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:665]
at org.junit.Assert.assertTrue(Assert.java:53)
[19:17:17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634#L5f7d9b05:666]
at
org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$17.run2(MemoryThresholdsOffHeapDUnitTest.java:660)
{code}
> MemoryThresholdsOffHeapDUnitTest has failures
> -
>
> Key: GEODE-7822
> URL: https://issues.apache.org/jira/browse/GEODE-7822
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
> Labels: flaky
>
> These two failures were seen in mass test runs...
> {noformat}
> testPRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/674
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testPRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call in
> VM 2 running on Host a57bd8581b8d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testPRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:1045)
> Caused by:
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
>
[jira] [Commented] (GEODE-7822) MemoryThresholdsOffHeapDUnitTest has failures
[
https://issues.apache.org/jira/browse/GEODE-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17234690#comment-17234690
]
Geode Integration commented on GEODE-7822:
--
Seen in [DistributedTestOpenJDK8
#634|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/634]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0497/test-results/distributedTest/1605663565/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0497/test-artifacts/1605663565/distributedtestfiles-OpenJDK8-1.14.0-build.0497.tgz].
> MemoryThresholdsOffHeapDUnitTest has failures
> -
>
> Key: GEODE-7822
> URL: https://issues.apache.org/jira/browse/GEODE-7822
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Priority: Major
> Labels: flaky
>
> These two failures were seen in mass test runs...
> {noformat}
> testPRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/674
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testPRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call in
> VM 2 running on Host a57bd8581b8d with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testPRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:1045)
> Caused by:
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$31.call(MemoryThresholdsOffHeapDUnitTest.java:1077){noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> [http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-results/distributedTest/1582515952/]
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-artifacts/1582515952/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0005.tgz]
> {noformat}
> testDRLoadRejection
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/742
> {noformat}
> {noformat}
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest >
> testDRLoadRejection FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$18.call in
> VM 2 running on Host b2c673017cde with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest.testDRLoadRejection(MemoryThresholdsOffHeapDUnitTest.java:667)
> Caused by:
>java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> org.apache.geode.cache.management.MemoryThresholdsOffHeapDUnitTest$18.call(MemoryThresholdsOffHeapDUnitTest.java:673)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-results/distributedTest/1582626992/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-mass-test-run-main/1.12.0-SNAPSHOT.0005/test-artifacts/1582626992/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0005.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-8725) Update Jetty to 9.4.34
[ https://issues.apache.org/jira/browse/GEODE-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarah Abbey updated GEODE-8725: --- Priority: Minor (was: Major) > Update Jetty to 9.4.34 > -- > > Key: GEODE-8725 > URL: https://issues.apache.org/jira/browse/GEODE-8725 > Project: Geode > Issue Type: Improvement >Reporter: Sarah Abbey >Assignee: Sarah Abbey >Priority: Minor > > Update Jetty to latest version (9.4.34) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8725) Update Jetty to 9.4.34
[ https://issues.apache.org/jira/browse/GEODE-8725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarah Abbey reassigned GEODE-8725: -- Assignee: Sarah Abbey > Update Jetty to 9.4.34 > -- > > Key: GEODE-8725 > URL: https://issues.apache.org/jira/browse/GEODE-8725 > Project: Geode > Issue Type: Improvement >Reporter: Sarah Abbey >Assignee: Sarah Abbey >Priority: Major > > Update Jetty to latest version (9.4.34) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8725) Update Jetty to 9.4.34
Sarah Abbey created GEODE-8725: -- Summary: Update Jetty to 9.4.34 Key: GEODE-8725 URL: https://issues.apache.org/jira/browse/GEODE-8725 Project: Geode Issue Type: Improvement Reporter: Sarah Abbey Update Jetty to latest version (9.4.34) -- This message was sent by Atlassian Jira (v8.3.4#803005)
