[jira] [Resolved] (GEODE-9765) Remove alb3rtobr from CODEWATCHERS
[ https://issues.apache.org/jira/browse/GEODE-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9765. - Resolution: Fixed > Remove alb3rtobr from CODEWATCHERS > -- > > Key: GEODE-9765 > URL: https://issues.apache.org/jira/browse/GEODE-9765 > Project: Geode > Issue Type: Task >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9766) Do not trigger CI for changes in CODEWATCHERS file
Alberto Bustamante Reyes created GEODE-9766: --- Summary: Do not trigger CI for changes in CODEWATCHERS file Key: GEODE-9766 URL: https://issues.apache.org/jira/browse/GEODE-9766 Project: Geode Issue Type: Improvement Components: ci Reporter: Alberto Bustamante Reyes Modifications in CODEWATCHERS file do not require to run CI tasks, it is a waste of resources to do it. Also it should be verified if this is currently happening the same for changes in CODEOWNERS file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9765) Remove alb3rtobr from CODEWATCHERS
[ https://issues.apache.org/jira/browse/GEODE-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9765: --- Assignee: Alberto Bustamante Reyes > Remove alb3rtobr from CODEWATCHERS > -- > > Key: GEODE-9765 > URL: https://issues.apache.org/jira/browse/GEODE-9765 > Project: Geode > Issue Type: Task >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9765) Remove alb3rtobr from CODEWATCHERS
Alberto Bustamante Reyes created GEODE-9765: --- Summary: Remove alb3rtobr from CODEWATCHERS Key: GEODE-9765 URL: https://issues.apache.org/jira/browse/GEODE-9765 Project: Geode Issue Type: Task Reporter: Alberto Bustamante Reyes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9235) Allow members binding to all addresses
[ https://issues.apache.org/jira/browse/GEODE-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9235: --- Assignee: (was: Alberto Bustamante Reyes) > Allow members binding to all addresses > -- > > Key: GEODE-9235 > URL: https://issues.apache.org/jira/browse/GEODE-9235 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > > *AS A* geode contributor > *I WANT TO* be able to start members with option "bind-address=0.0.0.0", > "bind-address=::" or "bind-address=*" > *SO THAT* all TCP endpoints are bound to all interfaces. > It is not currently possible to start cluster members binding to all > interfaces. That is using "bind-address=0.0.0.0" for ipv4 or > "bind-address=::" for ipv6. > Geode binds the locator and server traffic port by default to 0.0.0.0, but > the membership ports are bound by default to the local address. > Changing the default membership binding is not the best option, as it could > cause problems in existing Geode deployments. But using > "bind-address=0.0.0.0", "bind-address=::" or "bind-address=*" should be > accepted. > There is a use case that needs this binding, that is using Istio with Geode. > One of the requirements set by Istio towards applications trying to integrate > with it is that the application listening ports need to be bound to 0.0.0.0 > address (which listens on all interfaces). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9569) Geode Native User Guide build script: allow docs to be retained
[ https://issues.apache.org/jira/browse/GEODE-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9569. - Fix Version/s: 1.15.0 Resolution: Fixed > Geode Native User Guide build script: allow docs to be retained > --- > > Key: GEODE-9569 > URL: https://issues.apache.org/jira/browse/GEODE-9569 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The user guide build script allows the user to build and preview the > geode-native user guides. > A command-line option specifies whether the script generates the .NET or C++ > user guide. > When the script completes, it always deletes the generated guide. > Allow the user to keep the compiled guide. > Relevant files: > geode-native/docs/docker/preview-user-guide.sh > geode-native/docs/README.md -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9568) Geode User Guide build script: allow doc to be retained
[ https://issues.apache.org/jira/browse/GEODE-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9568. - Fix Version/s: 1.15.0 Resolution: Fixed > Geode User Guide build script: allow doc to be retained > --- > > Key: GEODE-9568 > URL: https://issues.apache.org/jira/browse/GEODE-9568 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The user guide build script allows the user to build and preview the user > guide. > When the script completes, it always deletes the user guide. > Allow the user to keep the compiled guide. > Relevant files: > dev-tools/docker/docs/preview-user-guide.sh > geode-book/README.md -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9624) Status redundancy command reports wrong value for empty regions
[
https://issues.apache.org/jira/browse/GEODE-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-9624.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> Status redundancy command reports wrong value for empty regions
> ---
>
> Key: GEODE-9624
> URL: https://issues.apache.org/jira/browse/GEODE-9624
> Project: Geode
> Issue Type: Bug
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> When a partitioned region is empty, the "status redundancy" command reports
> the current redundancy of than region as Integer.MAX_VALUE .
> This can be reproduced following these steps:
> {code:java}
> gfsh>start locator --name=locator1
> gfsh>start server --name=server1
> gfsh>start server --name=server2 --server-port=40405
> gfsh>create region --name=test --type=PARTITION_REDUNDANT_PERSISTENT
> gfsh>status redundancy
> Number of regions with zero redundant copies = 0
> Number of regions with partially satisfied redundancy = 1
> Number of regions with fully satisfied redundancy = 0
> Redundancy is partially satisfied for regions:
> test redundancy status: NOT_SATISFIED. Desired redundancy is 1 and actual
> redundancy is 2147483647.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (GEODE-6402) Create a DOAP file for the Apache Geode project
[
https://issues.apache.org/jira/browse/GEODE-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422675#comment-17422675
]
Alberto Bustamante Reyes edited comment on GEODE-6402 at 9/30/21, 10:19 AM:
doap file was added to the doap list on the Apache repo and its information is
shown on the Apache project directory:
https://projects.apache.org/project.html?geode
was (Author: alberto.bustamante.reyes):
doap file was added to the Apache repo xml file and its information is shown on
the Apache project directory:
https://projects.apache.org/project.html?geode
> Create a DOAP file for the Apache Geode project
> ---
>
> Key: GEODE-6402
> URL: https://issues.apache.org/jira/browse/GEODE-6402
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Dave Barnes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
>
> An Apache project can (and should) have a DOAP ("Description Of A Project")
> file that describes the project and provides some details. The DOAP allows
> the project to be found via language and category searches, provides release
> and repo information, etc.
> Here's a link to the Apache page that gets you started:
> [https://projects.apache.org/create.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-6402) Create a DOAP file for the Apache Geode project
[
https://issues.apache.org/jira/browse/GEODE-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-6402.
-
Resolution: Fixed
> Create a DOAP file for the Apache Geode project
> ---
>
> Key: GEODE-6402
> URL: https://issues.apache.org/jira/browse/GEODE-6402
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Dave Barnes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
>
> An Apache project can (and should) have a DOAP ("Description Of A Project")
> file that describes the project and provides some details. The DOAP allows
> the project to be found via language and category searches, provides release
> and repo information, etc.
> Here's a link to the Apache page that gets you started:
> [https://projects.apache.org/create.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6402) Create a DOAP file for the Apache Geode project
[
https://issues.apache.org/jira/browse/GEODE-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422675#comment-17422675
]
Alberto Bustamante Reyes commented on GEODE-6402:
-
doap file was added to the Apache repo xml file and its information is shown on
the Apache project directory:
https://projects.apache.org/project.html?geode
> Create a DOAP file for the Apache Geode project
> ---
>
> Key: GEODE-6402
> URL: https://issues.apache.org/jira/browse/GEODE-6402
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Dave Barnes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
>
> An Apache project can (and should) have a DOAP ("Description Of A Project")
> file that describes the project and provides some details. The DOAP allows
> the project to be found via language and category searches, provides release
> and repo information, etc.
> Here's a link to the Apache page that gets you started:
> [https://projects.apache.org/create.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9479) Document correct start up order in WAN setups
[ https://issues.apache.org/jira/browse/GEODE-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9479. - Fix Version/s: 1.15.0 Resolution: Fixed > Document correct start up order in WAN setups > - > > Key: GEODE-9479 > URL: https://issues.apache.org/jira/browse/GEODE-9479 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.15.0 > > > I recently had to deal with an issue which root cause was the incorrect start > up order of a region an a receiver ([mail > thread|https://markmail.org/thread/qq32z5hducjoqndz]) > The correct order is: > - Senders > - Region > - Receivers > I have not been able to find this info in the user guide. I think a good > place could be the "Timing of Connections" sub-chapter on the "Overview of > Multi-site Caching" chapter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9569) Geode Native User Guide build script: allow docs to be retained
[ https://issues.apache.org/jira/browse/GEODE-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9569: --- Assignee: Alberto Bustamante Reyes > Geode Native User Guide build script: allow docs to be retained > --- > > Key: GEODE-9569 > URL: https://issues.apache.org/jira/browse/GEODE-9569 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > > The user guide build script allows the user to build and preview the > geode-native user guides. > A command-line option specifies whether the script generates the .NET or C++ > user guide. > When the script completes, it always deletes the generated guide. > Allow the user to keep the compiled guide. > Relevant files: > geode-native/docs/docker/preview-user-guide.sh > geode-native/docs/README.md -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9568) Geode User Guide build script: allow doc to be retained
[ https://issues.apache.org/jira/browse/GEODE-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9568: --- Assignee: Alberto Bustamante Reyes > Geode User Guide build script: allow doc to be retained > --- > > Key: GEODE-9568 > URL: https://issues.apache.org/jira/browse/GEODE-9568 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > > The user guide build script allows the user to build and preview the user > guide. > When the script completes, it always deletes the user guide. > Allow the user to keep the compiled guide. > Relevant files: > dev-tools/docker/docs/preview-user-guide.sh > geode-book/README.md -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9479) Document correct start up order in WAN setups
[ https://issues.apache.org/jira/browse/GEODE-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9479: --- Assignee: Alberto Bustamante Reyes > Document correct start up order in WAN setups > - > > Key: GEODE-9479 > URL: https://issues.apache.org/jira/browse/GEODE-9479 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > > I recently had to deal with an issue which root cause was the incorrect start > up order of a region an a receiver ([mail > thread|https://markmail.org/thread/qq32z5hducjoqndz]) > The correct order is: > - Senders > - Region > - Receivers > I have not been able to find this info in the user guide. I think a good > place could be the "Timing of Connections" sub-chapter on the "Overview of > Multi-site Caching" chapter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9633) Region and gateway receiver init order may cause a hang
Alberto Bustamante Reyes created GEODE-9633:
---
Summary: Region and gateway receiver init order may cause a hang
Key: GEODE-9633
URL: https://issues.apache.org/jira/browse/GEODE-9633
Project: Geode
Issue Type: Bug
Reporter: Alberto Bustamante Reyes
This ticket has been created as suggested on [the dev
list|https://markmail.org/thread/qq32z5hducjoqndz].
-
I have been analyzing an issue that occurs in the following scenario:
1) I start two Geode clusters (cluster1 & cluster2) with one locator and two
servers each.
Both clusters host a partitioned region called "testregion", which is replicated
using a parallel gateway sender and a gateway receiver.
( These are [the gfsh
files|https://gist.github.com/alb3rtobr/e230623255632937fa68265f31e97f3a] I
have been using for creating the clusters)
2) I run a client connected to cluster2 performing operations on testregion.
3) cluster1 is stopped and all persistent data is deleted. And then, I create
cluster1 again.
4) At this point, the command to create "testregion" get stuck.
After checking the thread stack and the code, I found that the problem is the
following.
This thread is trapped on an infinite loop waiting for a bucket primary election
at "PartitionedRegion.waitForNoStorageOrPrimary":
{code}
"Function Execution Processor4" tid=0x55
java.lang.Thread.State: TIMED_WAITING
at java.base@11.0.11/java.lang.Object.wait(Native Method)
- waiting on org.apache.geode.internal.cache.BucketAdvisor@28be7ae0
at
app//org.apache.geode.internal.cache.BucketAdvisor.waitForPrimaryMember(BucketAdvisor.java:1433)
at
app//org.apache.geode.internal.cache.BucketAdvisor.waitForNewPrimary(BucketAdvisor.java:825)
at
app//org.apache.geode.internal.cache.BucketAdvisor.getPrimary(BucketAdvisor.java:794)
at
app//org.apache.geode.internal.cache.partitioned.RegionAdvisor.getPrimaryMemberForBucket(RegionAdvisor.java:1032)
at
app//org.apache.geode.internal.cache.PartitionedRegion.getBucketPrimary(PartitionedRegion.java:9081)
at
app//org.apache.geode.internal.cache.PartitionedRegion.waitForNoStorageOrPrimary(PartitionedRegion.java:3249)
at
app//org.apache.geode.internal.cache.PartitionedRegion.getNodeForBucketWrite(PartitionedRegion.java:3234)
at
app//org.apache.geode.internal.cache.PartitionedRegion.shadowPRWaitForBucketRecovery(PartitionedRegion.java:10110)
at
app//org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.addShadowPartitionedRegionForUserPR(ParallelGatewaySenderQueue.java:564)
at
app//org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderQueue.addShadowPartitionedRegionForUserPR(ParallelGatewaySenderQueue.java:443)
at
app//org.apache.geode.internal.cache.wan.parallel.ParallelGatewaySenderEventProcessor.addShadowPartitionedRegionForUserPR(ParallelGatewaySenderEventProcessor.java:195)
at
app//org.apache.geode.internal.cache.wan.parallel.ConcurrentParallelGatewaySenderQueue.addShadowPartitionedRegionForUserPR(ConcurrentParallelGatewaySenderQueue.java:183)
at
app//org.apache.geode.internal.cache.PartitionedRegion.postCreateRegion(PartitionedRegion.java:1177)
at
app//org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3050)
at
app//org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2910)
at
app//org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2894)
at
app//org.apache.geode.cache.RegionFactory.create(RegionFactory.java:773)
{code}
After creating testregion, the sender queue partitioned region is created. While
that region buckets are recovered the command is trapped on an infinite loop
waiting for a primary bucket election at
PartitionedRegion.waitForNoStorageOrPrimary.
This seems to be a known issue because in
PartitionedRegion.getNodeForBucketWrite, there is the following command before
calling waitForNoStorageOrPrimary (and the command has been there since Geode's
first commit!) :
{code}
// Possible race with loss of redundancy at this point.
// This loop can possibly create a soft hang if no primary is ever selected.
// This is preferable to returning null since it will prevent obtaining the
// bucket lock for bucket creation.
return waitForNoStorageOrPrimary(bucketId, "write");
{code}
Any idea about why the primary bucket is not elected?
It seems the failure is related with the fact that "testregion" is receiving
updates from the receiver before the "create region" command has finished. If
the test is repeated without traffic on cluster2 or if I create the cluster1's
receiver after creating "testregion", this problem is not happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9624) Status redundancy command reports wrong value for empty regions
[
https://issues.apache.org/jira/browse/GEODE-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-9624:
---
Assignee: Alberto Bustamante Reyes
> Status redundancy command reports wrong value for empty regions
> ---
>
> Key: GEODE-9624
> URL: https://issues.apache.org/jira/browse/GEODE-9624
> Project: Geode
> Issue Type: Bug
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> When a partitioned region is empty, the "status redundancy" command reports
> the current redundancy of than region as Integer.MAX_VALUE .
> This can be reproduced following these steps:
> {code:java}
> gfsh>start locator --name=locator1
> gfsh>start server --name=server1
> gfsh>start server --name=server2 --server-port=40405
> gfsh>create region --name=test --type=PARTITION_REDUNDANT_PERSISTENT
> gfsh>status redundancy
> Number of regions with zero redundant copies = 0
> Number of regions with partially satisfied redundancy = 1
> Number of regions with fully satisfied redundancy = 0
> Redundancy is partially satisfied for regions:
> test redundancy status: NOT_SATISFIED. Desired redundancy is 1 and actual
> redundancy is 2147483647.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9624) Status redundancy command reports wrong value for empty regions
Alberto Bustamante Reyes created GEODE-9624:
---
Summary: Status redundancy command reports wrong value for empty
regions
Key: GEODE-9624
URL: https://issues.apache.org/jira/browse/GEODE-9624
Project: Geode
Issue Type: Bug
Reporter: Alberto Bustamante Reyes
When a partitioned region is empty, the "status redundancy" command reports the
current redundancy of than region as Integer.MAX_VALUE .
This can be reproduced following these steps:
{code:java}
gfsh>start locator --name=locator1
gfsh>start server --name=server1
gfsh>start server --name=server2 --server-port=40405
gfsh>create region --name=test --type=PARTITION_REDUNDANT_PERSISTENT
gfsh>status redundancy
Number of regions with zero redundant copies = 0
Number of regions with partially satisfied redundancy = 1
Number of regions with fully satisfied redundancy = 0
Redundancy is partially satisfied for regions:
test redundancy status: NOT_SATISFIED. Desired redundancy is 1 and actual
redundancy is 2147483647.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9479) Document correct start up order in WAN setups
Alberto Bustamante Reyes created GEODE-9479: --- Summary: Document correct start up order in WAN setups Key: GEODE-9479 URL: https://issues.apache.org/jira/browse/GEODE-9479 Project: Geode Issue Type: Improvement Components: docs Reporter: Alberto Bustamante Reyes I recently had to deal with an issue which root cause was the incorrect start up order of a region an a receiver ([mail thread|https://markmail.org/thread/qq32z5hducjoqndz]) The correct order is: - Senders - Region - Receivers I have not been able to find this info in the user guide. I think a good place could be the "Timing of Connections" sub-chapter on the "Overview of Multi-site Caching" chapter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9479) Document correct start up order in WAN setups
[ https://issues.apache.org/jira/browse/GEODE-9479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-9479: Priority: Minor (was: Major) > Document correct start up order in WAN setups > - > > Key: GEODE-9479 > URL: https://issues.apache.org/jira/browse/GEODE-9479 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Priority: Minor > > I recently had to deal with an issue which root cause was the incorrect start > up order of a region an a receiver ([mail > thread|https://markmail.org/thread/qq32z5hducjoqndz]) > The correct order is: > - Senders > - Region > - Receivers > I have not been able to find this info in the user guide. I think a good > place could be the "Timing of Connections" sub-chapter on the "Overview of > Multi-site Caching" chapter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9300) write-buffer-size parameter not used when creating disk store
[ https://issues.apache.org/jira/browse/GEODE-9300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9300. - Fix Version/s: 1.15.0 Resolution: Fixed > write-buffer-size parameter not used when creating disk store > - > > Key: GEODE-9300 > URL: https://issues.apache.org/jira/browse/GEODE-9300 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Alberto Gomez >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > According to the Geode documentation, it is possible to set the write buffer > size by using --write-buffer-size when creating a disk store > ([https://geode.apache.org/docs/guide/113/tools_modules/gfsh/command-pages/create.html]). > > Nevertheless, setting a value for that parameter either by using gfsh, > cache.xml or the DiskStoreFactory.setWriteBuffer() method has no effect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9444) Improve gfsh error message when creating persistent region with no persistent gw sender
Alberto Bustamante Reyes created GEODE-9444:
---
Summary: Improve gfsh error message when creating persistent
region with no persistent gw sender
Key: GEODE-9444
URL: https://issues.apache.org/jira/browse/GEODE-9444
Project: Geode
Issue Type: Improvement
Components: gfsh
Reporter: Alberto Bustamante Reyes
The error shown in gfsh if you try to create a persistent region with a
non-persistent gateway sender is not describing the problem.
{code}
Cluster-1 gfsh>create region --name=testregion --type=PARTITION_PERSISTENT
--disk-store=regionstore --gateway-sender-id=sender
Member | Status | Message
--- | -- |
---
server1 | ERROR | An exception was caught while registering PartitionedRegion
/testregion. dumpPRId: prIdToPR Map@657410168:
server2 | ERROR | An exception was caught while registering PartitionedRegion
/testregion. dumpPRId: prIdToPR Map@985461106:
{code}
You have to check the server logs to check what happened:
{code}
[warn 2021/07/21 16:30:43.348 CEST tid=0x3a]
Initialization failed for Region /testregion
org.apache.geode.internal.cache.PartitionedRegionException: An exception was
caught while registering PartitionedRegion /testregion. dumpPRId: prIdToPR
Map@657410168:
, caused by
org.apache.geode.internal.cache.wan.GatewaySenderConfigurationException: Non
persistent gateway sender sender can not be attached to persistent region
/testregion
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9209) Complete test in DistributionConfigJUnitTest
[ https://issues.apache.org/jira/browse/GEODE-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9209. - Fix Version/s: 1.15.0 Resolution: Fixed > Complete test in DistributionConfigJUnitTest > > > Key: GEODE-9209 > URL: https://issues.apache.org/jira/browse/GEODE-9209 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.15.0 > > > testCheckerChecksValidAttribute in DistributionConfigJUnitTest has a "TODO" > comment about a missing check in the test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8282) Creating diskstore with size appened to name doesn't seem to work as documented
[
https://issues.apache.org/jira/browse/GEODE-8282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-8282.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> Creating diskstore with size appened to name doesn't seem to work as
> documented
> ---
>
> Key: GEODE-8282
> URL: https://issues.apache.org/jira/browse/GEODE-8282
> Project: Geode
> Issue Type: Bug
>Reporter: Jason Huynh
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The create diskstore --dir option is documented with:
> ...Optionally, directory names may be followed by {{#}} and the maximum
> number of megabytes that the disk store can use in the directory. For example:
> {code:java}
> --dir=/data/ds1
> --dir=/data/ds2#5000
> {code}
> When creating a disk store through gfsh with the size appended, it does not
> appear to limit the size of the directory. There also doesn't seem to be
> much validation...
> for example, when using a negative value we can see that the size described
> does not match what we expected to be our limit.
> {code:java}
> gfsh>describe disk-store --name=diskstore-2#-1000 --member=server1
> Disk Store ID : 643cb4b4-3cb0-40ec-b123-6945b23f165a
> Disk Store Name: diskstore-2#-1000
> Member ID : 192.168.0.3(server1:16006):41001
> Member Name: server1
> Allow Force Compaction : No
> Auto Compaction: Yes
> Compaction Threshold : 50
> Max Oplog Size : 1024
> Queue Size : 0
> Time Interval : 1000
> Write Buffer Size : 32768
> Disk Usage Warning Percentage : 90.0
> Disk Usage Critical Percentage : 99.0
> PDX Serialization Meta-Data Stored : No
> Disk Directory| Size
> --- |
> --
> /Users/jhuynh/apache-geode-1.12.0/bin/server1 | 2147483647
> {code}
> It also appears in code to only affect calculation of disk usage etc, but I
> didn't dig very deep. If it is used there, the negative value will probably
> mess with that calculation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-6402) Create a DOAP file for the Apache Geode project
[
https://issues.apache.org/jira/browse/GEODE-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-6402:
---
Assignee: Alberto Bustamante Reyes
> Create a DOAP file for the Apache Geode project
> ---
>
> Key: GEODE-6402
> URL: https://issues.apache.org/jira/browse/GEODE-6402
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Dave Barnes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> An Apache project can (and should) have a DOAP ("Description Of A Project")
> file that describes the project and provides some details. The DOAP allows
> the project to be found via language and category searches, provides release
> and repo information, etc.
> Here's a link to the Apache page that gets you started:
> [https://projects.apache.org/create.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-2842) Remove unnecessary @CliOption arguments
[
https://issues.apache.org/jira/browse/GEODE-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-2842.
-
Resolution: Fixed
Closing this ticket as currently there are no "@CliOption" annotations with
"mandatory = false" or using "CliMetaData.ANNOTATION_NULL_VALUE"
> Remove unnecessary @CliOption arguments
> ---
>
> Key: GEODE-2842
> URL: https://issues.apache.org/jira/browse/GEODE-2842
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Major
>
> The {{@CliOption}} annotation specifies default values for some of its fields
> (like {{mandatory}} and {{unspecifiedDefaultValue}}). Yet, we often
> explicitly set those fields to the default value. For example,
> {noformat} @CliOption(key = CliStrings.START_LOCATOR__MEMBER_NAME,
> mandatory = false,
> unspecifiedDefaultValue = CliMetaData.ANNOTATION_NULL_VALUE,
> help = CliStrings.START_LOCATOR__MEMBER_NAME__HELP) String
> memberName {noformat}
> could simply read
> {noformat} @CliOption(key = CliStrings.START_LOCATOR__MEMBER_NAME,
> help = CliStrings.START_LOCATOR__MEMBER_NAME__HELP) String
> memberName {noformat}
> Removing these redundant/unnecessary arguments will make the code a lot more
> readable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-6333) Add jetty-server dependency to geode-core
[
https://issues.apache.org/jira/browse/GEODE-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-6333.
-
Fix Version/s: 1.9.0
Resolution: Fixed
> Add jetty-server dependency to geode-core
> -
>
> Key: GEODE-6333
> URL: https://issues.apache.org/jira/browse/GEODE-6333
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Nabarun Nag
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Adding compile('org.eclipse.jetty:jetty-server:' + project.'jetty.version')
> to geode-core gradle.build
> This was done to prevent issues of class not found error when geode-core
> dependencies are added as a local maven dependency.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7154) Scripts fail with "Too many authentication failures"
[
https://issues.apache.org/jira/browse/GEODE-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-7154.
-
Resolution: Fixed
> Scripts fail with "Too many authentication failures"
>
>
> Key: GEODE-7154
> URL: https://issues.apache.org/jira/browse/GEODE-7154
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Reporter: Donal Evans
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When using the run_tests.sh script, the connection fails due to too many
> authentication failures, ultimately caused by offering too many
> authentication keys to the server:
> {noformat}./run_tests.sh -t pdxTestCluster --br DonalEvans/geode-benchmarks
> --bb feature/AddPdxTypeBenchmark --output
> ~/benchmarking/PDXTypeBenchmark/baseline -- --tests=CreatePdxFromJSONBenchmark
> FIRST_INSTANCE=52.43.142.66
> HOSTS=172.31.45.135,172.31.42.61,172.31.40.26,172.31.44.175
> Warning: Permanently added '52.43.142.66' (ECDSA) to the list of known hosts.
> Received disconnect from 52.43.142.66 port 22:2: Too many authentication
> failures
> Disconnected from 52.43.142.66 port 22{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7263) Geode Native: Dockerfile for building the user guide needs updating
[ https://issues.apache.org/jira/browse/GEODE-7263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-7263. - Resolution: Duplicate > Geode Native: Dockerfile for building the user guide needs updating > --- > > Key: GEODE-7263 > URL: https://issues.apache.org/jira/browse/GEODE-7263 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Dave Barnes >Priority: Major > > We provide a Docker file for building the Native Client User Guide ( > geode-native/docs/docker > ). When I follow README instructions, I get errors regarding unrecognized > addresses and out-of-date components. A sample: > gpg: directory '/root/.gnupg' created > gpg: keybox '/root/.gnupg/pubring.kbx' created > gpg: keyserver receive failed: Cannot assign requested address > gpg: keyserver receive failed: No data > gpg: key 105BD0E739499BDB: 7 signatures not checked due to missing keys > gpg: /root/.gnupg/trustdb.gpg: trustdb created > gpg: key 105BD0E739499BDB: public key "Piotr Kuczynski > " imported > gpg: key 3804BB82D39DC0E3: 106 signatures not checked due to missing keys > gpg: key 3804BB82D39DC0E3: public key "Michal Papis (RVM signing) > " imported > gpg: no ultimately trusted keys found > gpg: Total number processed: 2 > gpg: imported: 2 > > ... > Step 6/13 : RUN /bin/bash -l -c "rvm requirements" > ---> Running in 10c01ef4a95e > mesg: ttyname failed: Inappropriate ioctl for device > > ... > Please be aware that you just installed a ruby that requires 3 patches just > to be compiled on an up to date linux system. > This may have known and unaccounted for security vulnerabilities. > Please consider upgrading to ruby-2.6.5 which will have all of the latest > security patches. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8065) show metrics --file option not exporting data to csv
[ https://issues.apache.org/jira/browse/GEODE-8065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-8065. - Resolution: Not A Problem > show metrics --file option not exporting data to csv > > > Key: GEODE-8065 > URL: https://issues.apache.org/jira/browse/GEODE-8065 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Ashish Choudhary >Priority: Major > > Connect to gfsh and run below command to export metrics to csv file. > gfsh>show metrics --file=/Users/ashishchoudhary/Downloads/test.csv > Cluster-wide Metrics > > Category | Metric | Value > - | - | - > cluster | totalHeapSize | 886 > cache | totalRegionEntryCount | 0 > | totalRegionCount | 1 > | totalMissCount | 1 > | totalHitCount | 4 > diskstore | totalDiskUsage | 0 > | diskReadsRate | 0.0 > | diskWritesRate | 0.0 > | flushTimeAvgLatency | 0 > | totalBackupInProgress | 0 > query | activeCQCount | 0 > | queryRequestRate | 0.0 > > File saved to /Users/ashishchoudhary/Downloads/test.csv > But there is no file saved to the above location. Even if you manually create > a file and export data using above gfsh command it shows zero bytes i.e no > content after the export. > After manually creating .csv file > show metrics --file=/Users/ashishchoudhary/Downloads/test.csv > File "test.csv" already exists Overwrite? (Y/N) : Y > Cluster-wide Metrics > > Category | Metric | Value > - | - | - > cluster | totalHeapSize | 886 > cache | totalRegionEntryCount | 0 > | totalRegionCount | 1 > | totalMissCount | 1 > | totalHitCount | 4 > diskstore | totalDiskUsage | 0 > | diskReadsRate | 0.0 > | diskWritesRate | 0.0 > | flushTimeAvgLatency | 0 > | totalBackupInProgress | 0 > query | activeCQCount | 0 > | queryRequestRate | 0.0 > > File saved to /Users/ashishchoudhary/Downloads/test.csv > There is no data actually in the .csv file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8065) show metrics --file option not exporting data to csv
[ https://issues.apache.org/jira/browse/GEODE-8065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17368238#comment-17368238 ] Alberto Bustamante Reyes commented on GEODE-8065: - There is a distributed test case verifying the export to csv ( ShowMetricsDUnitTest.testShowMetricsMemberWithFileOutput() ) and it passes on develop branch. Anyway I tried the process manually, and the export works fine: the file is created and it has content inside. > show metrics --file option not exporting data to csv > > > Key: GEODE-8065 > URL: https://issues.apache.org/jira/browse/GEODE-8065 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Ashish Choudhary >Priority: Major > > Connect to gfsh and run below command to export metrics to csv file. > gfsh>show metrics --file=/Users/ashishchoudhary/Downloads/test.csv > Cluster-wide Metrics > > Category | Metric | Value > - | - | - > cluster | totalHeapSize | 886 > cache | totalRegionEntryCount | 0 > | totalRegionCount | 1 > | totalMissCount | 1 > | totalHitCount | 4 > diskstore | totalDiskUsage | 0 > | diskReadsRate | 0.0 > | diskWritesRate | 0.0 > | flushTimeAvgLatency | 0 > | totalBackupInProgress | 0 > query | activeCQCount | 0 > | queryRequestRate | 0.0 > > File saved to /Users/ashishchoudhary/Downloads/test.csv > But there is no file saved to the above location. Even if you manually create > a file and export data using above gfsh command it shows zero bytes i.e no > content after the export. > After manually creating .csv file > show metrics --file=/Users/ashishchoudhary/Downloads/test.csv > File "test.csv" already exists Overwrite? (Y/N) : Y > Cluster-wide Metrics > > Category | Metric | Value > - | - | - > cluster | totalHeapSize | 886 > cache | totalRegionEntryCount | 0 > | totalRegionCount | 1 > | totalMissCount | 1 > | totalHitCount | 4 > diskstore | totalDiskUsage | 0 > | diskReadsRate | 0.0 > | diskWritesRate | 0.0 > | flushTimeAvgLatency | 0 > | totalBackupInProgress | 0 > query | activeCQCount | 0 > | queryRequestRate | 0.0 > > File saved to /Users/ashishchoudhary/Downloads/test.csv > There is no data actually in the .csv file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9293) Add cause of error to GemFireIOException messages
[
https://issues.apache.org/jira/browse/GEODE-9293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-9293.
-
Resolution: Duplicate
The problem of the missing stacktrace was already fixed by GEODE-8124
> Add cause of error to GemFireIOException messages
> -
>
> Key: GEODE-9293
> URL: https://issues.apache.org/jira/browse/GEODE-9293
> Project: Geode
> Issue Type: Improvement
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Minor
> Labels: pull-request-available
>
> *AS A* geode user
> *I WANT TO* have more information when an IO exception occurs
> *SO THAT I* can understand and fix the root cause of the problem
> _GemFireIOException_ is used to encapsulate a given _IOException_ that happen
> in the Geode code.
> For creating a _GemFireIOException_ when a _IOException_ is catched, this
> constructor is used:
> {code}
> public GemFireIOException(String message, Throwable cause) {
> super(message, cause);
> }
> {code}
> The problem is that the _IOException_ message is not part of the
> _GemFireIOException_ message. So when a _GemFireIOException_ is logged, the
> root cause of the problem is not shown.
> For example, the following message log message:
> {{"Cache initialization for GemFireCache[id = 1081136680; isClosing = false;
> isShutDownAll = false; created = Fri Jun 19 11:42:29 UTC 2020; server =
> false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
> org.apache.geode.GemFireIOException: While starting cache server CacheServer
> on port=40404 client subscription config policy=none client subscription
> config capacity=1 client subscription config overflow directory=."}}
> It was logged at _GemFireCacheImpl_:
> {code}
> logger.error("Cache initialization for " + toString() + " failed because:",
> throwable);
> {code}
> And the _GemFireIOException_ was created in _CacheCreation_ in this way:
> {code}
> } catch (IOException ex) {
> throw new GemFireIOException(format("While starting cache server %s",
> impl), ex);
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-8282) Creating diskstore with size appened to name doesn't seem to work as documented
[
https://issues.apache.org/jira/browse/GEODE-8282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-8282:
---
Assignee: Alberto Bustamante Reyes
> Creating diskstore with size appened to name doesn't seem to work as
> documented
> ---
>
> Key: GEODE-8282
> URL: https://issues.apache.org/jira/browse/GEODE-8282
> Project: Geode
> Issue Type: Bug
>Reporter: Jason Huynh
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> The create diskstore --dir option is documented with:
> ...Optionally, directory names may be followed by {{#}} and the maximum
> number of megabytes that the disk store can use in the directory. For example:
> {code:java}
> --dir=/data/ds1
> --dir=/data/ds2#5000
> {code}
> When creating a disk store through gfsh with the size appended, it does not
> appear to limit the size of the directory. There also doesn't seem to be
> much validation...
> for example, when using a negative value we can see that the size described
> does not match what we expected to be our limit.
> {code:java}
> gfsh>describe disk-store --name=diskstore-2#-1000 --member=server1
> Disk Store ID : 643cb4b4-3cb0-40ec-b123-6945b23f165a
> Disk Store Name: diskstore-2#-1000
> Member ID : 192.168.0.3(server1:16006):41001
> Member Name: server1
> Allow Force Compaction : No
> Auto Compaction: Yes
> Compaction Threshold : 50
> Max Oplog Size : 1024
> Queue Size : 0
> Time Interval : 1000
> Write Buffer Size : 32768
> Disk Usage Warning Percentage : 90.0
> Disk Usage Critical Percentage : 99.0
> PDX Serialization Meta-Data Stored : No
> Disk Directory| Size
> --- |
> --
> /Users/jhuynh/apache-geode-1.12.0/bin/server1 | 2147483647
> {code}
> It also appears in code to only affect calculation of disk usage etc, but I
> didn't dig very deep. If it is used there, the negative value will probably
> mess with that calculation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9300) write-buffer-size parameter not used when creating disk store
[ https://issues.apache.org/jira/browse/GEODE-9300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9300: --- Assignee: Alberto Bustamante Reyes > write-buffer-size parameter not used when creating disk store > - > > Key: GEODE-9300 > URL: https://issues.apache.org/jira/browse/GEODE-9300 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Alberto Gomez >Assignee: Alberto Bustamante Reyes >Priority: Major > > According to the Geode documentation, it is possible to set the write buffer > size by using --write-buffer-size when creating a disk store > ([https://geode.apache.org/docs/guide/113/tools_modules/gfsh/command-pages/create.html]). > > Nevertheless, setting a value for that parameter either by using gfsh, > cache.xml or the DiskStoreFactory.setWriteBuffer() method has no effect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7968) User Guide - Region shortcuts quick-ref - reformat oversize table
[ https://issues.apache.org/jira/browse/GEODE-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-7968: --- Assignee: Alberto Bustamante Reyes > User Guide - Region shortcuts quick-ref - reformat oversize table > - > > Key: GEODE-7968 > URL: https://issues.apache.org/jira/browse/GEODE-7968 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > > On the Region Shortcuts Quick Reference page, > [https://geode.apache.org/docs/guide/112/reference/topics/region_shortcuts_table.html], > > the table exceeds the column width, leading to readability issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7967) User Guide - gfsh start locator - reformat oversize table
[ https://issues.apache.org/jira/browse/GEODE-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-7967: --- Assignee: Alberto Bustamante Reyes > User Guide - gfsh start locator - reformat oversize table > - > > Key: GEODE-7967 > URL: https://issues.apache.org/jira/browse/GEODE-7967 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > > On the gfsh start locator reference page, > [https://geode.apache.org/docs/guide/112/tools_modules/gfsh/command-pages/start.html#topic_591260CF25D64562A0EDD7260D2AC6D4] > the table exceeds the column width, leading to readability issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9334: --- Assignee: Alberto Bustamante Reyes > Geode Native User Guide: update dockerfile to use newer ruby & gems > --- > > Key: GEODE-9334 > URL: https://issues.apache.org/jira/browse/GEODE-9334 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > Update the Geode Native docker-based scripts to generate the user guides, > following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9334) Geode Native User Guide: update dockerfile to use newer ruby & gems
Alberto Bustamante Reyes created GEODE-9334: --- Summary: Geode Native User Guide: update dockerfile to use newer ruby & gems Key: GEODE-9334 URL: https://issues.apache.org/jira/browse/GEODE-9334 Project: Geode Issue Type: Improvement Components: docs, native client Reporter: Alberto Bustamante Reyes Update the Geode Native docker-based scripts to generate the user guides, following the same process done for Geode User Guide (GEODE-9042) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9042) Geode User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9042. - Fix Version/s: 1.15.0 Resolution: Fixed > Geode User Guide: update dockerfile to use newer ruby & gems > > > Key: GEODE-9042 > URL: https://issues.apache.org/jira/browse/GEODE-9042 > Project: Geode > Issue Type: Improvement > Components: docs, tools >Affects Versions: 1.13.1 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The scripts that build the user guide are pinned at Ruby 2.3.0 and Bookbinder > 1.10.14. > These need to be updated to Ruby 2.5.3 (or later) and Bookbinder 1.10.15 in > order to support current deployment infrastructure. > Path to the Bookbinder gem: > http://docs-wiki.cfapps.io/wiki/bookbinder/installing-bookbinder.html#v10 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9312) Uplift Bookbinder to 10.1.17
[ https://issues.apache.org/jira/browse/GEODE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9312. - Fix Version/s: 1.15.0 Resolution: Fixed > Uplift Bookbinder to 10.1.17 > > > Key: GEODE-9312 > URL: https://issues.apache.org/jira/browse/GEODE-9312 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Uplift Bookbinder to use new 10.1.17 version, which solves the problems with > mimemagic library reported in GEODE-9042. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9211) Locator and server launcher have references to GemFire
[ https://issues.apache.org/jira/browse/GEODE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9211. - Fix Version/s: 1.15.0 Resolution: Fixed > Locator and server launcher have references to GemFire > -- > > Key: GEODE-9211 > URL: https://issues.apache.org/jira/browse/GEODE-9211 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.15.0 > > > LocatorLauncher and ServerLauncher classes have a lot of references to > "GemFire" in Javadocs. They should be substituted by "Geode". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8951) Unnecessary messaging in WAN locator discovery
[
https://issues.apache.org/jira/browse/GEODE-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-8951.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> Unnecessary messaging in WAN locator discovery
> --
>
> Key: GEODE-8951
> URL: https://issues.apache.org/jira/browse/GEODE-8951
> Project: Geode
> Issue Type: Improvement
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Bruce J Schuchardt
>Assignee: Alberto Bustamante Reyes
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> While debugging another issue I noticed that a locator was trying to send a
> notice to another locator in its cluster telling it that the recipient had
> joined.
>
> [warn 2021/02/16 15:16:56.195 PST locatorgemfire_4_3_host2_9736
> tid=0x153] Locator Membership listener
> permanently failed to exchange locator information
> *rs-GEM-3188-VJ1459-1a0i3large-hydra-client-1:27878* with
> *rs-GEM-3188-VJ1459-1a0i3large-hydra-client-2:28778* after 3 retry attempts
>
> This messaging is unnecessary. The locator that this message was being sent
> to already knows about itself. This is being done in
> _DistributeLocatorsRunnable.run()._
>
> {code:java}
> for (DistributionLocatorId remoteLocator : entry.getValue()) {
> // Notify known remote locator about the advertised locator.
> LocatorJoinMessage advertiseNewLocatorMessage = new
> LocatorJoinMessage(
> joiningLocatorDistributedSystemId, joiningLocator,
> localLocatorId, "");
> sendMessage(remoteLocator, advertiseNewLocatorMessage,
> failedMessages);
> // Notify the advertised locator about remote known locator.
> LocatorJoinMessage advertiseKnownLocatorMessage =
> new LocatorJoinMessage(entry.getKey(), remoteLocator,
> localLocatorId, "");
> sendMessage(joiningLocator, advertiseKnownLocatorMessage,
> failedMessages);
> }
> {code}
> It should check to see if the joiningLocator ID is equal to the remoteLocator
> ID and, if so, not create messages in that iteration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9312) Uplift Bookbinder to 10.1.17
[ https://issues.apache.org/jira/browse/GEODE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9312: --- Assignee: Alberto Bustamante Reyes > Uplift Bookbinder to 10.1.17 > > > Key: GEODE-9312 > URL: https://issues.apache.org/jira/browse/GEODE-9312 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > Uplift Bookbinder to use new 10.1.17 version, which solves the problems with > mimemagic library reported in GEODE-9042. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9312) Uplift Bookbinder to 10.1.17
[ https://issues.apache.org/jira/browse/GEODE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-9312: Parent: GEODE-9042 Issue Type: Sub-task (was: Improvement) > Uplift Bookbinder to 10.1.17 > > > Key: GEODE-9312 > URL: https://issues.apache.org/jira/browse/GEODE-9312 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > Uplift Bookbinder to use new 10.1.17 version, which solves the problems with > mimemagic library reported in GEODE-9042. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9312) Uplift Bookbinder to 10.1.17
Alberto Bustamante Reyes created GEODE-9312: --- Summary: Uplift Bookbinder to 10.1.17 Key: GEODE-9312 URL: https://issues.apache.org/jira/browse/GEODE-9312 Project: Geode Issue Type: Improvement Components: docs Reporter: Alberto Bustamante Reyes Uplift Bookbinder to use new 10.1.17 version, which solves the problems with mimemagic library reported in GEODE-9042. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9042) Geode User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350464#comment-17350464 ] Alberto Bustamante Reyes commented on GEODE-9042: - Thanks Dave, I will continue with this ticket then > Geode User Guide: update dockerfile to use newer ruby & gems > > > Key: GEODE-9042 > URL: https://issues.apache.org/jira/browse/GEODE-9042 > Project: Geode > Issue Type: Improvement > Components: docs, tools >Affects Versions: 1.13.1 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > > The scripts that build the user guide are pinned at Ruby 2.3.0 and Bookbinder > 1.10.14. > These need to be updated to Ruby 2.5.3 (or later) and Bookbinder 1.10.15 in > order to support current deployment infrastructure. > Path to the Bookbinder gem: > http://docs-wiki.cfapps.io/wiki/bookbinder/installing-bookbinder.html#v10 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GEODE-9288) DeployedJarTest fails because JavaCompiler.compile() fails to delete temporaryClassesDirectory
[
https://issues.apache.org/jira/browse/GEODE-9288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350343#comment-17350343
]
Alberto Bustamante Reyes edited comment on GEODE-9288 at 5/24/21, 10:51 AM:
Lets see if after changing to "Files.createTempDirectory()" this issue is not
reproduced again
was (Author: alberto.bustamante.reyes):
Lets see if after changing to "Files.createTempDirectory()" this issue is
reproduced again
> DeployedJarTest fails because JavaCompiler.compile() fails to delete
> temporaryClassesDirectory
> --
>
> Key: GEODE-9288
> URL: https://issues.apache.org/jira/browse/GEODE-9288
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> DeployedJarTest.throwsIfFileIsNotValidJarFile() test failed in Windows CI
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/225
> The problem did not reproduce on macOS in 1000 runs.
> I notice that the JavaCompiler constructor calls the deprecated
> Files.createTempDir(). I wonder if there might be a race condition where two
> test processes (at once) think they own that temp dir and so they can both
> delete it.
> We might consider replacing that deprecated call with the recommended
> Files.createTempDirectory() which may be more robust. Looking at the
> deprecated method and the recommended substitute the latter might have less
> of a chance of collision due to its use of random suffixes (versus the
> former's monotonically-increasing ints).
> {code:java}
> org.apache.geode.deployment.internal.DeployedJarTest >
> throwsIfFileIsNotValidJarFile FAILED
> java.io.IOException: Unable to delete directory
> C:\Users\geode\AppData\Local\Temp\1621373797371-0\classes.
> at
> org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1212)
> at
> org.apache.geode.test.compiler.JavaCompiler.compile(JavaCompiler.java:90)
> at
> org.apache.geode.test.compiler.JarBuilder.buildJarFromClassNames(JarBuilder.java:79)
> at
> org.apache.geode.deployment.internal.DeployedJarTest.createJarFile(DeployedJarTest.java:82)
> at
> org.apache.geode.deployment.internal.DeployedJarTest.throwsIfFileIsNotValidJarFile(DeployedJarTest.java:47)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9288) DeployedJarTest fails because JavaCompiler.compile() fails to delete temporaryClassesDirectory
[
https://issues.apache.org/jira/browse/GEODE-9288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-9288.
-
Fix Version/s: 1.15.0
Resolution: Fixed
Lets see if after changing to "Files.createTempDirectory()" this issue is
reproduced again
> DeployedJarTest fails because JavaCompiler.compile() fails to delete
> temporaryClassesDirectory
> --
>
> Key: GEODE-9288
> URL: https://issues.apache.org/jira/browse/GEODE-9288
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> DeployedJarTest.throwsIfFileIsNotValidJarFile() test failed in Windows CI
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/225
> The problem did not reproduce on macOS in 1000 runs.
> I notice that the JavaCompiler constructor calls the deprecated
> Files.createTempDir(). I wonder if there might be a race condition where two
> test processes (at once) think they own that temp dir and so they can both
> delete it.
> We might consider replacing that deprecated call with the recommended
> Files.createTempDirectory() which may be more robust. Looking at the
> deprecated method and the recommended substitute the latter might have less
> of a chance of collision due to its use of random suffixes (versus the
> former's monotonically-increasing ints).
> {code:java}
> org.apache.geode.deployment.internal.DeployedJarTest >
> throwsIfFileIsNotValidJarFile FAILED
> java.io.IOException: Unable to delete directory
> C:\Users\geode\AppData\Local\Temp\1621373797371-0\classes.
> at
> org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1212)
> at
> org.apache.geode.test.compiler.JavaCompiler.compile(JavaCompiler.java:90)
> at
> org.apache.geode.test.compiler.JarBuilder.buildJarFromClassNames(JarBuilder.java:79)
> at
> org.apache.geode.deployment.internal.DeployedJarTest.createJarFile(DeployedJarTest.java:82)
> at
> org.apache.geode.deployment.internal.DeployedJarTest.throwsIfFileIsNotValidJarFile(DeployedJarTest.java:47)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9293) Add cause of error to GemFireIOException messages
[
https://issues.apache.org/jira/browse/GEODE-9293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes updated GEODE-9293:
Priority: Minor (was: Major)
> Add cause of error to GemFireIOException messages
> -
>
> Key: GEODE-9293
> URL: https://issues.apache.org/jira/browse/GEODE-9293
> Project: Geode
> Issue Type: Improvement
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Minor
>
> *AS A* geode user
> *I WANT TO* have more information when an IO exception occurs
> *SO THAT I* can understand and fix the root cause of the problem
> _GemFireIOException_ is used to encapsulate a given _IOException_ that happen
> in the Geode code.
> For creating a _GemFireIOException_ when a _IOException_ is catched, this
> constructor is used:
> {code}
> public GemFireIOException(String message, Throwable cause) {
> super(message, cause);
> }
> {code}
> The problem is that the _IOException_ message is not part of the
> _GemFireIOException_ message. So when a _GemFireIOException_ is logged, the
> root cause of the problem is not shown.
> For example, the following message log message:
> {{"Cache initialization for GemFireCache[id = 1081136680; isClosing = false;
> isShutDownAll = false; created = Fri Jun 19 11:42:29 UTC 2020; server =
> false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
> org.apache.geode.GemFireIOException: While starting cache server CacheServer
> on port=40404 client subscription config policy=none client subscription
> config capacity=1 client subscription config overflow directory=."}}
> It was logged at _GemFireCacheImpl_:
> {code}
> logger.error("Cache initialization for " + toString() + " failed because:",
> throwable);
> {code}
> And the _GemFireIOException_ was created in _CacheCreation_ in this way:
> {code}
> } catch (IOException ex) {
> throw new GemFireIOException(format("While starting cache server %s",
> impl), ex);
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9293) Add cause of error to GemFireIOException messages
[
https://issues.apache.org/jira/browse/GEODE-9293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes updated GEODE-9293:
Summary: Add cause of error to GemFireIOException messages (was: Add root
cause to GemFireIOException messages)
> Add cause of error to GemFireIOException messages
> -
>
> Key: GEODE-9293
> URL: https://issues.apache.org/jira/browse/GEODE-9293
> Project: Geode
> Issue Type: Improvement
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> *AS A* geode user
> *I WANT TO* have more information when an IO exception occurs
> *SO THAT I* can understand and fix the root cause of the problem
> _GemFireIOException_ is used to encapsulate a given _IOException_ that happen
> in the Geode code.
> For creating a _GemFireIOException_ when a _IOException_ is catched, this
> constructor is used:
> {code}
> public GemFireIOException(String message, Throwable cause) {
> super(message, cause);
> }
> {code}
> The problem is that the _IOException_ message is not part of the
> _GemFireIOException_ message. So when a _GemFireIOException_ is logged, the
> root cause of the problem is not shown.
> For example, the following message log message:
> {{"Cache initialization for GemFireCache[id = 1081136680; isClosing = false;
> isShutDownAll = false; created = Fri Jun 19 11:42:29 UTC 2020; server =
> false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
> org.apache.geode.GemFireIOException: While starting cache server CacheServer
> on port=40404 client subscription config policy=none client subscription
> config capacity=1 client subscription config overflow directory=."}}
> It was logged at _GemFireCacheImpl_:
> {code}
> logger.error("Cache initialization for " + toString() + " failed because:",
> throwable);
> {code}
> And the _GemFireIOException_ was created in _CacheCreation_ in this way:
> {code}
> } catch (IOException ex) {
> throw new GemFireIOException(format("While starting cache server %s",
> impl), ex);
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9293) Add root cause to GemFireIOException messages
[
https://issues.apache.org/jira/browse/GEODE-9293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-9293:
---
Assignee: Alberto Bustamante Reyes
> Add root cause to GemFireIOException messages
> -
>
> Key: GEODE-9293
> URL: https://issues.apache.org/jira/browse/GEODE-9293
> Project: Geode
> Issue Type: Improvement
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> *AS A* geode user
> *I WANT TO* have more information when an IO exception occurs
> *SO THAT I* can understand and fix the root cause of the problem
> _GemFireIOException_ is used to encapsulate a given _IOException_ that happen
> in the Geode code.
> For creating a _GemFireIOException_ when a _IOException_ is catched, this
> constructor is used:
> {code}
> public GemFireIOException(String message, Throwable cause) {
> super(message, cause);
> }
> {code}
> The problem is that the _IOException_ message is not part of the
> _GemFireIOException_ message. So when a _GemFireIOException_ is logged, the
> root cause of the problem is not shown.
> For example, the following message log message:
> {{"Cache initialization for GemFireCache[id = 1081136680; isClosing = false;
> isShutDownAll = false; created = Fri Jun 19 11:42:29 UTC 2020; server =
> false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
> org.apache.geode.GemFireIOException: While starting cache server CacheServer
> on port=40404 client subscription config policy=none client subscription
> config capacity=1 client subscription config overflow directory=."}}
> It was logged at _GemFireCacheImpl_:
> {code}
> logger.error("Cache initialization for " + toString() + " failed because:",
> throwable);
> {code}
> And the _GemFireIOException_ was created in _CacheCreation_ in this way:
> {code}
> } catch (IOException ex) {
> throw new GemFireIOException(format("While starting cache server %s",
> impl), ex);
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9293) Add root cause to GemFireIOException messages
Alberto Bustamante Reyes created GEODE-9293:
---
Summary: Add root cause to GemFireIOException messages
Key: GEODE-9293
URL: https://issues.apache.org/jira/browse/GEODE-9293
Project: Geode
Issue Type: Improvement
Reporter: Alberto Bustamante Reyes
*AS A* geode user
*I WANT TO* have more information when an IO exception occurs
*SO THAT I* can understand and fix the root cause of the problem
_GemFireIOException_ is used to encapsulate a given _IOException_ that happen
in the Geode code.
For creating a _GemFireIOException_ when a _IOException_ is catched, this
constructor is used:
{code}
public GemFireIOException(String message, Throwable cause) {
super(message, cause);
}
{code}
The problem is that the _IOException_ message is not part of the
_GemFireIOException_ message. So when a _GemFireIOException_ is logged, the
root cause of the problem is not shown.
For example, the following message log message:
{{"Cache initialization for GemFireCache[id = 1081136680; isClosing = false;
isShutDownAll = false; created = Fri Jun 19 11:42:29 UTC 2020; server = false;
copyOnRead = false; lockLease = 120; lockTimeout = 60] failed because:
org.apache.geode.GemFireIOException: While starting cache server CacheServer on
port=40404 client subscription config policy=none client subscription config
capacity=1 client subscription config overflow directory=."}}
It was logged at _GemFireCacheImpl_:
{code}
logger.error("Cache initialization for " + toString() + " failed because:",
throwable);
{code}
And the _GemFireIOException_ was created in _CacheCreation_ in this way:
{code}
} catch (IOException ex) {
throw new GemFireIOException(format("While starting cache server %s",
impl), ex);
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9282) Add alb3rtobr to CODEWATCHERS file
[ https://issues.apache.org/jira/browse/GEODE-9282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9282. - Resolution: Fixed > Add alb3rtobr to CODEWATCHERS file > -- > > Key: GEODE-9282 > URL: https://issues.apache.org/jira/browse/GEODE-9282 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > > I would like to be added as code watcher for some parts of Geode code -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9288) DeployedJarTest fails because JavaCompiler.compile() fails to delete temporaryClassesDirectory
[
https://issues.apache.org/jira/browse/GEODE-9288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-9288:
---
Assignee: Alberto Bustamante Reyes
> DeployedJarTest fails because JavaCompiler.compile() fails to delete
> temporaryClassesDirectory
> --
>
> Key: GEODE-9288
> URL: https://issues.apache.org/jira/browse/GEODE-9288
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> DeployedJarTest.throwsIfFileIsNotValidJarFile() test failed in Windows CI
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/225
> The problem did not reproduce on macOS in 1000 runs.
> I notice that the JavaCompiler constructor calls the deprecated
> Files.createTempDir(). I wonder if there might be a race condition where two
> test processes (at once) think they own that temp dir and so they can both
> delete it.
> We might consider replacing that deprecated call with the recommended
> Files.createTempDirectory() which may be more robust. Looking at the
> deprecated method and the recommended substitute the latter might have less
> of a chance of collision due to its use of random suffixes (versus the
> former's monotonically-increasing ints).
> {code:java}
> org.apache.geode.deployment.internal.DeployedJarTest >
> throwsIfFileIsNotValidJarFile FAILED
> java.io.IOException: Unable to delete directory
> C:\Users\geode\AppData\Local\Temp\1621373797371-0\classes.
> at
> org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1212)
> at
> org.apache.geode.test.compiler.JavaCompiler.compile(JavaCompiler.java:90)
> at
> org.apache.geode.test.compiler.JarBuilder.buildJarFromClassNames(JarBuilder.java:79)
> at
> org.apache.geode.deployment.internal.DeployedJarTest.createJarFile(DeployedJarTest.java:82)
> at
> org.apache.geode.deployment.internal.DeployedJarTest.throwsIfFileIsNotValidJarFile(DeployedJarTest.java:47)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9284) only download geode-old-versions for upgradeTest
[ https://issues.apache.org/jira/browse/GEODE-9284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9284: --- Assignee: Robert Houghton > only download geode-old-versions for upgradeTest > > > Key: GEODE-9284 > URL: https://issues.apache.org/jira/browse/GEODE-9284 > Project: Geode > Issue Type: Improvement > Components: build, ci >Affects Versions: 1.15.0 >Reporter: Robert Houghton >Assignee: Robert Houghton >Priority: Major > Labels: pull-request-available > > Geode has an `upgradeTest` facet intended to do tests that involve previous > Geode releases. Ensure that only for those tests runtime, do we download and > unzip the old versions of Geode. Any other time, doing so is a waste. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9282) Add alb3rtobr to CODEWATCHERS file
[ https://issues.apache.org/jira/browse/GEODE-9282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9282: --- Assignee: Alberto Bustamante Reyes > Add alb3rtobr to CODEWATCHERS file > -- > > Key: GEODE-9282 > URL: https://issues.apache.org/jira/browse/GEODE-9282 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > I would like to be added as code watcher for some parts of Geode code -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9282) Add alb3rtobr to CODEWATCHERS file
Alberto Bustamante Reyes created GEODE-9282: --- Summary: Add alb3rtobr to CODEWATCHERS file Key: GEODE-9282 URL: https://issues.apache.org/jira/browse/GEODE-9282 Project: Geode Issue Type: Improvement Reporter: Alberto Bustamante Reyes I would like to be added as code watcher for some parts of Geode code -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-8951) Unnecessary messaging in WAN locator discovery
[
https://issues.apache.org/jira/browse/GEODE-8951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-8951:
---
Assignee: Alberto Bustamante Reyes
> Unnecessary messaging in WAN locator discovery
> --
>
> Key: GEODE-8951
> URL: https://issues.apache.org/jira/browse/GEODE-8951
> Project: Geode
> Issue Type: Improvement
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Bruce J Schuchardt
>Assignee: Alberto Bustamante Reyes
>Priority: Minor
>
> While debugging another issue I noticed that a locator was trying to send a
> notice to another locator in its cluster telling it that the recipient had
> joined.
>
> [warn 2021/02/16 15:16:56.195 PST locatorgemfire_4_3_host2_9736
> tid=0x153] Locator Membership listener
> permanently failed to exchange locator information
> *rs-GEM-3188-VJ1459-1a0i3large-hydra-client-1:27878* with
> *rs-GEM-3188-VJ1459-1a0i3large-hydra-client-2:28778* after 3 retry attempts
>
> This messaging is unnecessary. The locator that this message was being sent
> to already knows about itself. This is being done in
> _DistributeLocatorsRunnable.run()._
>
> {code:java}
> for (DistributionLocatorId remoteLocator : entry.getValue()) {
> // Notify known remote locator about the advertised locator.
> LocatorJoinMessage advertiseNewLocatorMessage = new
> LocatorJoinMessage(
> joiningLocatorDistributedSystemId, joiningLocator,
> localLocatorId, "");
> sendMessage(remoteLocator, advertiseNewLocatorMessage,
> failedMessages);
> // Notify the advertised locator about remote known locator.
> LocatorJoinMessage advertiseKnownLocatorMessage =
> new LocatorJoinMessage(entry.getKey(), remoteLocator,
> localLocatorId, "");
> sendMessage(joiningLocator, advertiseKnownLocatorMessage,
> failedMessages);
> }
> {code}
> It should check to see if the joiningLocator ID is equal to the remoteLocator
> ID and, if so, not create messages in that iteration.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9250) CI failure: DeployWithGroupsDUnitTest > undeployJarFromAllServersWithRestart FAILED
[
https://issues.apache.org/jira/browse/GEODE-9250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17343251#comment-17343251
]
Alberto Bustamante Reyes commented on GEODE-9250:
-
I have been taking a look, but I have not been able to find a root cause.
The test case has the following steps:
1: A jar file is deployed in two servers
2: The jar file is undeployed
3: Server's VM are restarted, and Geode server are started again using groups.
Then it is verified that the jar file is still undeployed.
The problem occurred when server2 VM is was restarted. This action is performed
using "bounce()" method, but it did not work properly this time.
Server 1 VM is bounced successfully:
{code:java}
[info 2021/05/07 14:36:16.703 GMT tid=0x1b] Bounced 1. New pid
is 1248 and version is 10240.0.0
{code}
But when server2 VM is bounced:
{code:java}
[info 2021/05/07 14:36:16.727 GMT tid=0x1b] Bouncing 2 old pid
is 89 and version is 10240.0.0
[vm2] [info 2021/05/07 14:36:19.515 GMT tid=0x1] VM2 is launching with
PID 1307
[vm2] gemfire.DUnitLauncher.RMI_PORT=22500
{code}
At this point, on a successful tests execution we should see a info log message
from Test worker saying "Bounced 2. New pid is ", but:
{code:java}
[info 2021/05/07 14:36:19.676 GMT tid=0x1b] Executing command:
disconnect
Command result for :
Disconnecting from: cce5ec2eafa6[22504]
Disconnected from : cce5ec2eafa6[22504]
[info 2021/05/07 14:36:19.683 GMT tid=0x1b] Executing command:
exit
[info 2021/05/07 14:36:19.684 GMT tid=0x1b] java.rmi.NoSuchObjectException: no such object in
table
{code}
> CI failure: DeployWithGroupsDUnitTest > undeployJarFromAllServersWithRestart
> FAILED
> ---
>
> Key: GEODE-9250
> URL: https://issues.apache.org/jira/browse/GEODE-9250
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Owen Nichols
>Priority: Major
>
> {noformat}
> org.apache.geode.management.internal.cli.commands.DeployWithGroupsDUnitTest >
> undeployJarFromAllServersWithRestart FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.DistributedRestoreSystemProperties$$Lambda$381/0x00010066f040.run
> in VM 2 running on Host cce5ec2eafa6 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> ...
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:140)
> ...
> Caused by:
> java.lang.NullPointerException
> at
> org.apache.geode.test.dunit.rules.DistributedRestoreSystemProperties.invokeAfter(DistributedRestoreSystemProperties.java:70)
> at
> org.apache.geode.test.dunit.rules.DistributedRestoreSystemProperties.lambda$after$bb17a952$1(DistributedRestoreSystemProperties.java:44)
> 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.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> 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
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:359)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:562)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:796)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:677)
> ...{noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9230) Remove magic numbers in GfshParserAutoCompletionIntegrationTest
[ https://issues.apache.org/jira/browse/GEODE-9230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9230. - Fix Version/s: 1.15.0 Resolution: Fixed > Remove magic numbers in GfshParserAutoCompletionIntegrationTest > --- > > Key: GEODE-9230 > URL: https://issues.apache.org/jira/browse/GEODE-9230 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > GfshParserAutoCompletionIntegrationTest uses magic numbers in some tests. > They depend on the number of possible parameters of "start server" command. > That means that when a new parameter is added to the "start server" command, > some tests verifying the gfsh autocompletion feature are impacted, which has > no sense. > The number of parameters can be calculated instead of hardcoded in order to > remove this dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-8877) Configurable membership bind address
[ https://issues.apache.org/jira/browse/GEODE-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-8877. - Resolution: Won't Fix > Configurable membership bind address > > > Key: GEODE-8877 > URL: https://issues.apache.org/jira/browse/GEODE-8877 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > > Geode binds the locator and server traffic port by default to 0.0.0.0, but > the membership ports are bound to the local address. > There is a use case that needs this binding to be configurable ([link to the > conversation in the dev list|http://markmail.org/thread/7dwtygtgfcitboy3]): > We would like to use Istio with Geode. For that, a sidecar container (Envoy) > has to be added in each Geode pod. That sidecar container intercepts and > handles all incoming and outgoing traffic for that pod. One of the > requirements set by Istio towards applications trying to integrate with it is > that the application listening ports need to be bound to either localhost or > 0.0.0.0 address (which listens on all interfaces). > > Geode binds the locator and server traffic port by default to 0.0.0.0, but > the membership ports are bound to the pod IP. > And with Envoy listening on the pod IP for incoming traffic and proxying > everything towards localhost, applications binding to pod IPs won't receive > any traffic. > We have tried using the "bind-address" parameter, but that doesn't work for > our case. Geode binds the listening ports to the configured address, but it > also shares that same address to other members in the system as the address > to be used to reach it. If we configure that address to localhost, it just > won't work. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9235) Allow members binding to all addresses
[ https://issues.apache.org/jira/browse/GEODE-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9235: --- Assignee: Alberto Bustamante Reyes > Allow members binding to all addresses > -- > > Key: GEODE-9235 > URL: https://issues.apache.org/jira/browse/GEODE-9235 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > *AS A* geode contributor > *I WANT TO* be able to start members with option "bind-address=0.0.0.0", > "bind-address=::" or "bind-address=*" > *SO THAT* all TCP endpoints are bound to all interfaces. > It is not currently possible to start cluster members binding to all > interfaces. That is using "bind-address=0.0.0.0" for ipv4 or > "bind-address=::" for ipv6. > Geode binds the locator and server traffic port by default to 0.0.0.0, but > the membership ports are bound by default to the local address. > Changing the default membership binding is not the best option, as it could > cause problems in existing Geode deployments. But using > "bind-address=0.0.0.0", "bind-address=::" or "bind-address=*" should be > accepted. > There is a use case that needs this binding, that is using Istio with Geode. > One of the requirements set by Istio towards applications trying to integrate > with it is that the application listening ports need to be bound to 0.0.0.0 > address (which listens on all interfaces). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9235) Allow members binding to all addresses
Alberto Bustamante Reyes created GEODE-9235: --- Summary: Allow members binding to all addresses Key: GEODE-9235 URL: https://issues.apache.org/jira/browse/GEODE-9235 Project: Geode Issue Type: Improvement Reporter: Alberto Bustamante Reyes *AS A* geode contributor *I WANT TO* be able to start members with option "bind-address=0.0.0.0", "bind-address=::" or "bind-address=*" *SO THAT* all TCP endpoints are bound to all interfaces. It is not currently possible to start cluster members binding to all interfaces. That is using "bind-address=0.0.0.0" for ipv4 or "bind-address=::" for ipv6. Geode binds the locator and server traffic port by default to 0.0.0.0, but the membership ports are bound by default to the local address. Changing the default membership binding is not the best option, as it could cause problems in existing Geode deployments. But using "bind-address=0.0.0.0", "bind-address=::" or "bind-address=*" should be accepted. There is a use case that needs this binding, that is using Istio with Geode. One of the requirements set by Istio towards applications trying to integrate with it is that the application listening ports need to be bound to 0.0.0.0 address (which listens on all interfaces). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9230) Remove magic numbers in GfshParserAutoCompletionIntegrationTest
[ https://issues.apache.org/jira/browse/GEODE-9230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9230: --- Assignee: Alberto Bustamante Reyes > Remove magic numbers in GfshParserAutoCompletionIntegrationTest > --- > > Key: GEODE-9230 > URL: https://issues.apache.org/jira/browse/GEODE-9230 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > GfshParserAutoCompletionIntegrationTest uses magic numbers in some tests. > They depend on the number of possible parameters of "start server" command. > That means that when a new parameter is added to the "start server" command, > some tests verifying the gfsh autocompletion feature are impacted, which has > no sense. > The number of parameters can be calculated instead of hardcoded in order to > remove this dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9230) Remove magic numbers in GfshParserAutoCompletionIntegrationTest
Alberto Bustamante Reyes created GEODE-9230: --- Summary: Remove magic numbers in GfshParserAutoCompletionIntegrationTest Key: GEODE-9230 URL: https://issues.apache.org/jira/browse/GEODE-9230 Project: Geode Issue Type: Improvement Reporter: Alberto Bustamante Reyes GfshParserAutoCompletionIntegrationTest uses magic numbers in some tests. They depend on the number of possible parameters of "start server" command. That means that when a new parameter is added to the "start server" command, some tests verifying the gfsh autocompletion feature are impacted, which has no sense. The number of parameters can be calculated instead of hardcoded in order to remove this dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9226) Refactor StartMemberUtils.resolveWorkingDir
[
https://issues.apache.org/jira/browse/GEODE-9226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-9226:
---
Assignee: Alberto Bustamante Reyes
> Refactor StartMemberUtils.resolveWorkingDir
> ---
>
> Key: GEODE-9226
> URL: https://issues.apache.org/jira/browse/GEODE-9226
> Project: Geode
> Issue Type: Improvement
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> StartMemberUtils contains utility methods used by StartLocatorCommand &
> StartServerCommand.
> One of them is resolveWorkingDir which returns the working directory to be
> used by the member. Part of the logic of this procedure is placed outside the
> function:
> {code}
> workingDirectory = StartMemberUtils.resolveWorkingDir(workingDirectory ==
> null ? null : new File(workingDirectory), new File(memberName));
> {code}
> This causes that unit tests of that function need to create an instance of
> StartLocatorCommand & StartServerCommand classes.
> And this has two negative consequences:
> * When a new startup parameter is added to locators and/or server, the tests
> of resolveWorkingDir have to be modified.
> * Tests are duplicated: there is a test class for every class using
> resolveWorkingDir (StartLocatorCommandWorkingDirectoryTest &
> StartServerCommandWorkingDirectoryTest).
> The function and the tests should be refactored to improve the code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9226) Refactor StartMemberUtils.resolveWorkingDir
Alberto Bustamante Reyes created GEODE-9226:
---
Summary: Refactor StartMemberUtils.resolveWorkingDir
Key: GEODE-9226
URL: https://issues.apache.org/jira/browse/GEODE-9226
Project: Geode
Issue Type: Improvement
Reporter: Alberto Bustamante Reyes
StartMemberUtils contains utility methods used by StartLocatorCommand &
StartServerCommand.
One of them is resolveWorkingDir which returns the working directory to be used
by the member. Part of the logic of this procedure is placed outside the
function:
{code}
workingDirectory = StartMemberUtils.resolveWorkingDir(workingDirectory == null
? null : new File(workingDirectory), new File(memberName));
{code}
This causes that unit tests of that function need to create an instance of
StartLocatorCommand & StartServerCommand classes.
And this has two negative consequences:
* When a new startup parameter is added to locators and/or server, the tests of
resolveWorkingDir have to be modified.
* Tests are duplicated: there is a test class for every class using
resolveWorkingDir (StartLocatorCommandWorkingDirectoryTest &
StartServerCommandWorkingDirectoryTest).
The function and the tests should be refactored to improve the code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9211) Locator and server launcher have references to GemFire
Alberto Bustamante Reyes created GEODE-9211: --- Summary: Locator and server launcher have references to GemFire Key: GEODE-9211 URL: https://issues.apache.org/jira/browse/GEODE-9211 Project: Geode Issue Type: Improvement Reporter: Alberto Bustamante Reyes LocatorLauncher and ServerLauncher classes have a lot of references to "GemFire" in Javadocs. They should be substituted by "Geode". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9211) Locator and server launcher have references to GemFire
[ https://issues.apache.org/jira/browse/GEODE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-9211: Priority: Minor (was: Major) > Locator and server launcher have references to GemFire > -- > > Key: GEODE-9211 > URL: https://issues.apache.org/jira/browse/GEODE-9211 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > > LocatorLauncher and ServerLauncher classes have a lot of references to > "GemFire" in Javadocs. They should be substituted by "Geode". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9211) Locator and server launcher have references to GemFire
[ https://issues.apache.org/jira/browse/GEODE-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9211: --- Assignee: Alberto Bustamante Reyes > Locator and server launcher have references to GemFire > -- > > Key: GEODE-9211 > URL: https://issues.apache.org/jira/browse/GEODE-9211 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > LocatorLauncher and ServerLauncher classes have a lot of references to > "GemFire" in Javadocs. They should be substituted by "Geode". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9209) Complete test in DistributionConfigJUnitTest
[ https://issues.apache.org/jira/browse/GEODE-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-9209: Priority: Minor (was: Major) > Complete test in DistributionConfigJUnitTest > > > Key: GEODE-9209 > URL: https://issues.apache.org/jira/browse/GEODE-9209 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > > testCheckerChecksValidAttribute in DistributionConfigJUnitTest has a "TODO" > comment about a missing check in the test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9209) Complete test in DistributionConfigJUnitTest
Alberto Bustamante Reyes created GEODE-9209: --- Summary: Complete test in DistributionConfigJUnitTest Key: GEODE-9209 URL: https://issues.apache.org/jira/browse/GEODE-9209 Project: Geode Issue Type: Improvement Reporter: Alberto Bustamante Reyes testCheckerChecksValidAttribute in DistributionConfigJUnitTest has a "TODO" comment about a missing check in the test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9209) Complete test in DistributionConfigJUnitTest
[ https://issues.apache.org/jira/browse/GEODE-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9209: --- Assignee: Alberto Bustamante Reyes > Complete test in DistributionConfigJUnitTest > > > Key: GEODE-9209 > URL: https://issues.apache.org/jira/browse/GEODE-9209 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > testCheckerChecksValidAttribute in DistributionConfigJUnitTest has a "TODO" > comment about a missing check in the test. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-4709) Sample output missing in gfsh docs for 'list gateways'
[ https://issues.apache.org/jira/browse/GEODE-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-4709. - Fix Version/s: 1.15.0 Resolution: Fixed > Sample output missing in gfsh docs for 'list gateways' > -- > > Key: GEODE-4709 > URL: https://issues.apache.org/jira/browse/GEODE-4709 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.15.0 > > > It looks like all other 'list' commands have both Example commands and Sample > Output except for 'list gateways'. Please add. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-5337) Geode1.5 end-port is not exclusive when creating a gateway-receiver
[
https://issues.apache.org/jira/browse/GEODE-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-5337.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> Geode1.5 end-port is not exclusive when creating a gateway-receiver
>
>
> Key: GEODE-5337
> URL: https://issues.apache.org/jira/browse/GEODE-5337
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Cui Chenxiao
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> When created, a gateway-receiver shall be assign a range of port to use.
> In document
> [http://geode.apache.org/docs/guide/16/tools_modules/gfsh/command-pages/create.html#topic_a4x_pb1_dk],
> the description for --end-port says "The {{ENDPORT}} value is exclusive
> while the {{STARTPORT}} value is inclusive. ".
>
> However, sometimes, the port number of endport is also assigned to receiver
> anyway. Besides, in code for gatewayreceiver, the endport will be randomly
> assigned to receiver.
>
> I supposed this shall be a document bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-8282) Creating diskstore with size appened to name doesn't seem to work as documented
[
https://issues.apache.org/jira/browse/GEODE-8282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-8282:
---
Assignee: (was: Alberto Bustamante Reyes)
> Creating diskstore with size appened to name doesn't seem to work as
> documented
> ---
>
> Key: GEODE-8282
> URL: https://issues.apache.org/jira/browse/GEODE-8282
> Project: Geode
> Issue Type: Bug
>Reporter: Jason Huynh
>Priority: Major
>
> The create diskstore --dir option is documented with:
> ...Optionally, directory names may be followed by {{#}} and the maximum
> number of megabytes that the disk store can use in the directory. For example:
> {code:java}
> --dir=/data/ds1
> --dir=/data/ds2#5000
> {code}
> When creating a disk store through gfsh with the size appended, it does not
> appear to limit the size of the directory. There also doesn't seem to be
> much validation...
> for example, when using a negative value we can see that the size described
> does not match what we expected to be our limit.
> {code:java}
> gfsh>describe disk-store --name=diskstore-2#-1000 --member=server1
> Disk Store ID : 643cb4b4-3cb0-40ec-b123-6945b23f165a
> Disk Store Name: diskstore-2#-1000
> Member ID : 192.168.0.3(server1:16006):41001
> Member Name: server1
> Allow Force Compaction : No
> Auto Compaction: Yes
> Compaction Threshold : 50
> Max Oplog Size : 1024
> Queue Size : 0
> Time Interval : 1000
> Write Buffer Size : 32768
> Disk Usage Warning Percentage : 90.0
> Disk Usage Critical Percentage : 99.0
> PDX Serialization Meta-Data Stored : No
> Disk Directory| Size
> --- |
> --
> /Users/jhuynh/apache-geode-1.12.0/bin/server1 | 2147483647
> {code}
> It also appears in code to only affect calculation of disk usage etc, but I
> didn't dig very deep. If it is used there, the negative value will probably
> mess with that calculation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-4709) Sample output missing in gfsh docs for 'list gateways'
[ https://issues.apache.org/jira/browse/GEODE-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-4709: --- Assignee: Alberto Bustamante Reyes > Sample output missing in gfsh docs for 'list gateways' > -- > > Key: GEODE-4709 > URL: https://issues.apache.org/jira/browse/GEODE-4709 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Assignee: Alberto Bustamante Reyes >Priority: Minor > > It looks like all other 'list' commands have both Example commands and Sample > Output except for 'list gateways'. Please add. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4709) Sample output missing in gfsh docs for 'list gateways'
[ https://issues.apache.org/jira/browse/GEODE-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-4709: Priority: Minor (was: Major) > Sample output missing in gfsh docs for 'list gateways' > -- > > Key: GEODE-4709 > URL: https://issues.apache.org/jira/browse/GEODE-4709 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Diane Hardman >Priority: Minor > > It looks like all other 'list' commands have both Example commands and Sample > Output except for 'list gateways'. Please add. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-5337) Geode1.5 end-port is not exclusive when creating a gateway-receiver
[
https://issues.apache.org/jira/browse/GEODE-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-5337:
---
Assignee: Alberto Bustamante Reyes
> Geode1.5 end-port is not exclusive when creating a gateway-receiver
>
>
> Key: GEODE-5337
> URL: https://issues.apache.org/jira/browse/GEODE-5337
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Cui Chenxiao
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Fix For: 1.5.0
>
>
> When created, a gateway-receiver shall be assign a range of port to use.
> In document
> [http://geode.apache.org/docs/guide/16/tools_modules/gfsh/command-pages/create.html#topic_a4x_pb1_dk],
> the description for --end-port says "The {{ENDPORT}} value is exclusive
> while the {{STARTPORT}} value is inclusive. ".
>
> However, sometimes, the port number of endport is also assigned to receiver
> anyway. Besides, in code for gatewayreceiver, the endport will be randomly
> assigned to receiver.
>
> I supposed this shall be a document bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-5958) Geode Native API docs contain proprietary links
[ https://issues.apache.org/jira/browse/GEODE-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-5958. - Fix Version/s: 1.9.0 Resolution: Fixed > Geode Native API docs contain proprietary links > --- > > Key: GEODE-5958 > URL: https://issues.apache.org/jira/browse/GEODE-5958 > Project: Geode > Issue Type: Bug > Components: docs, native client >Reporter: Dave Barnes >Priority: Major > Fix For: 1.9.0 > > > * geode-native/docs/api/unix_index.html and > geode-native/docs/api/win_index.html contain proprietary references. > * geode-native/docs/CMakeLists.txt refers to these files, installing them as > the top-level index files in the api doc directories for cpp and dotnet > * The generated API docs have an incorrect version number, should be the > same as Geode (e.g. "1.8") -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9188) Move upgrade info from wiki to user guide
[ https://issues.apache.org/jira/browse/GEODE-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes updated GEODE-9188: Priority: Minor (was: Major) > Move upgrade info from wiki to user guide > - > > Key: GEODE-9188 > URL: https://issues.apache.org/jira/browse/GEODE-9188 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Alberto Bustamante Reyes >Priority: Minor > > I have found there is a confluence wiki page containing information about > rolling upgrades: > https://cwiki.apache.org/confluence/display/GEODE/Notes+for+rolling+upgrade+updates > For keeping the wiki tidy, it should be evaluated if the info contained in > this page should be added to the user guide, as after GEODE-8946 there is an > upgrade chapter in the user guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9188) Move upgrade info from wiki to user guide
Alberto Bustamante Reyes created GEODE-9188: --- Summary: Move upgrade info from wiki to user guide Key: GEODE-9188 URL: https://issues.apache.org/jira/browse/GEODE-9188 Project: Geode Issue Type: Improvement Components: docs Reporter: Alberto Bustamante Reyes I have found there is a confluence wiki page containing information about rolling upgrades: https://cwiki.apache.org/confluence/display/GEODE/Notes+for+rolling+upgrade+updates For keeping the wiki tidy, it should be evaluated if the info contained in this page should be added to the user guide, as after GEODE-8946 there is an upgrade chapter in the user guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9063) Make mandatory options to appear first when autocompleting in gfsh
[ https://issues.apache.org/jira/browse/GEODE-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9063. - Fix Version/s: 1.15.0 Resolution: Fixed > Make mandatory options to appear first when autocompleting in gfsh > -- > > Key: GEODE-9063 > URL: https://issues.apache.org/jira/browse/GEODE-9063 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > When writting a command in gfsh followed by "--" and then pressing "tab" to > obtain command completion suggestions, the mandatory options should be shown > in first place. > This was recently fixed in GEODE-9034 for "create gateway-sender" but there > are some more commands to be fixed: > * change log-level > * create disk-store > * create jndi-binding > * destroy gateway-sender > * export data > * import data > * remove -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9042) Geode User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9042: --- Assignee: Alberto Bustamante Reyes > Geode User Guide: update dockerfile to use newer ruby & gems > > > Key: GEODE-9042 > URL: https://issues.apache.org/jira/browse/GEODE-9042 > Project: Geode > Issue Type: Improvement > Components: docs, tools >Affects Versions: 1.13.1 >Reporter: Dave Barnes >Assignee: Alberto Bustamante Reyes >Priority: Major > > The scripts that build the user guide are pinned at Ruby 2.3.0 and Bookbinder > 1.10.14. > These need to be updated to Ruby 2.5.3 (or later) and Bookbinder 1.10.15 in > order to support current deployment infrastructure. > Path to the Bookbinder gem: > http://docs-wiki.cfapps.io/wiki/bookbinder/installing-bookbinder.html#v10 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9042) Geode User Guide: update dockerfile to use newer ruby & gems
[ https://issues.apache.org/jira/browse/GEODE-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309051#comment-17309051 ] Alberto Bustamante Reyes commented on GEODE-9042: - The problem with mimemagic library is affecting more than 500.000 repositories: https://www.theregister.com/2021/03/25/ruby_rails_code/ It seems Bookbinder should use version 0.3.6 to avoid license issues. > Geode User Guide: update dockerfile to use newer ruby & gems > > > Key: GEODE-9042 > URL: https://issues.apache.org/jira/browse/GEODE-9042 > Project: Geode > Issue Type: Improvement > Components: docs, tools >Affects Versions: 1.13.1 >Reporter: Dave Barnes >Priority: Major > > The scripts that build the user guide are pinned at Ruby 2.3.0 and Bookbinder > 1.10.14. > These need to be updated to Ruby 2.5.3 (or later) and Bookbinder 1.10.15 in > order to support current deployment infrastructure. > Path to the Bookbinder gem: > http://docs-wiki.cfapps.io/wiki/bookbinder/installing-bookbinder.html#v10 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9042) Geode User Guide: update dockerfile to use newer ruby & gems
[
https://issues.apache.org/jira/browse/GEODE-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17309035#comment-17309035
]
Alberto Bustamante Reyes commented on GEODE-9042:
-
Hi [~dbarnes]. Updating Bookbinder to 1.10.5 is not enough, as that version is
affected by a recent issue with mimemagic ruby gem. The authors removed old
versions, and Bookbinder uses mimemagic 0.3.2, which is not available anymore.
The change affected a lot of software projects, and it seems it is solved by
using an updated version, with that has to be fixed by Bookbinder team.
The manual process to generate the documentation [described
here|https://github.com/apache/geode/tree/develop/geode-book#building-the-documentation]
is impacted. And also the automatic process based on Docker images.
I tried first using what is in develop branch, which is Bookbinder 1.10.14, and
after I changed the geode-book/Gemfile to use 1.10.15, but in both cases the
result is the same: after moving to "final_app" folder and running "bundle
install", this error is shown:
{code:java}
$ bundle install
Fetching gem metadata from http://rubygems.org/
Resolving dependencies...
Your bundle is locked to mimemagic (0.3.2), but that version could not be found
in any of the sources listed in your Gemfile. If you haven't changed sources,
that means the author of mimemagic (0.3.2) has
removed it. You'll need to update your bundle to a version other than mimemagic
(0.3.2) that hasn't been removed in order to install.
{code}
Bookbinder team should create a newer version updating the dependencies, to
avoid the usage of mimemagic 0.3.2
> Geode User Guide: update dockerfile to use newer ruby & gems
>
>
> Key: GEODE-9042
> URL: https://issues.apache.org/jira/browse/GEODE-9042
> Project: Geode
> Issue Type: Improvement
> Components: docs, tools
>Affects Versions: 1.13.1
>Reporter: Dave Barnes
>Priority: Major
>
> The scripts that build the user guide are pinned at Ruby 2.3.0 and Bookbinder
> 1.10.14.
> These need to be updated to Ruby 2.5.3 (or later) and Bookbinder 1.10.15 in
> order to support current deployment infrastructure.
> Path to the Bookbinder gem:
> http://docs-wiki.cfapps.io/wiki/bookbinder/installing-bookbinder.html#v10
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9062) DataSerializableJUnitTest fails in StressTest task
[
https://issues.apache.org/jira/browse/GEODE-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-9062.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> DataSerializableJUnitTest fails in StressTest task
> --
>
> Key: GEODE-9062
> URL: https://issues.apache.org/jira/browse/GEODE-9062
> Project: Geode
> Issue Type: Bug
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> DataSerializableJUnitTest is failing if executed using the "repeatUnitTest"
> gradle task. I dont know what is causing this failure, but I got the error
> when verifying a PR ( [https://concourse.apachegeode-ci.info/builds/17155] )
> and I realized it is failing in develop branch too.
> {code}
> ~/git/apache/geode (develop) $ ./gradlew geode-core:repeatUnitTest
> --tests=DataSerializableJUnitTest
> ...
> org.apache.geode.internal.DataSerializableJUnitTest > testUDDS2 FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.geode.internal.DataSerializableJUnitTest.testUDDS2(DataSerializableJUnitTest.java:2284)
> org.apache.geode.internal.DataSerializableJUnitTest > testUDDS4 FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.geode.internal.DataSerializableJUnitTest.testUDDS4(DataSerializableJUnitTest.java:2307)
> org.apache.geode.internal.DataSerializableJUnitTest > testSupportedClasses
> FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.geode.internal.DataSerializableJUnitTest.testSupportedClasses(DataSerializableJUnitTest.java:2260)
> 11100 tests completed, 297 failed, 200 skipped
> > Task :geode-core:repeatUnitTest FAILED
> > Task :combineReports
> All test reports at /home/alb3rtobr/git/apache/geode/build/reports/combined
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geode-core:repeatUnitTest'.
> > There were failing tests. See the report at:
> > file:///home/alb3rtobr/git/apache/geode/geode-core/build/reports/repeatUnitTest/index.html
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output. Run with --scan to get full insights.
> * Get more help at https://help.gradle.org
> BUILD FAILED in 1m 8s
> 36 actionable tasks: 2 executed, 34 up-to-date
> ~/git/apache/geode (develop) $ git log -n 1
> commit a45dbf94de2f35b869a3dd0e1cf945f5282e2fd0 (HEAD -> develop,
> origin/develop, origin/HEAD)
> Author: Mario Kevo <48509719+mk...@users.noreply.github.com>
> Date: Wed Mar 24 10:25:29 2021 +0100
> GEODE-8962: add an option to escape dollar($) character in the query (#6044)
>
> * GEODE-8962: add an option to escape dollar($) character in the query
> {code}
> Three tests are failing: testSupportedClasses, testUDDS2 and testUDDS4.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9066) Docker-based documentation generation is broken
[
https://issues.apache.org/jira/browse/GEODE-9066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-9066.
-
Resolution: Duplicate
> Docker-based documentation generation is broken
> ---
>
> Key: GEODE-9066
> URL: https://issues.apache.org/jira/browse/GEODE-9066
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> `view-docs.sh` script is not working, it seems one Ruby dependency has to be
> updated
> {code}
> $ ./view-docs.sh
> Building geode/docsbuild:0.1 image...
> sha256:c79da695299c58856b901cd309fdcf785ee1bce0451d687fd9592d1371562916
> Building geode/docsbuild:0.1-alb3rtobr image...
> sha256:524290937f1c0fd846ef87bc7e1edb53a98f3af997e3a25b54b2eb66def890ad
> Starting up web server...
> Fetching gem metadata from http://rubygems.org/
> Fetching version metadata from http://rubygems.org/.
> Resolving dependencies...
> Your bundle is locked to mimemagic (0.3.2), but that version could not be
> found in any of the sources listed in your Gemfile. If you haven't changed
> sources, that means the author of mimemagic (0.3.2) has
> removed it. You'll need to update your bundle to a different version of
> mimemagic (0.3.2) that hasn't been removed in order to install.
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9066) Docker-based documentation generation is broken
[
https://issues.apache.org/jira/browse/GEODE-9066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-9066:
---
Assignee: Alberto Bustamante Reyes
> Docker-based documentation generation is broken
> ---
>
> Key: GEODE-9066
> URL: https://issues.apache.org/jira/browse/GEODE-9066
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> `view-docs.sh` script is not working, it seems one Ruby dependency has to be
> updated
> {code}
> $ ./view-docs.sh
> Building geode/docsbuild:0.1 image...
> sha256:c79da695299c58856b901cd309fdcf785ee1bce0451d687fd9592d1371562916
> Building geode/docsbuild:0.1-alb3rtobr image...
> sha256:524290937f1c0fd846ef87bc7e1edb53a98f3af997e3a25b54b2eb66def890ad
> Starting up web server...
> Fetching gem metadata from http://rubygems.org/
> Fetching version metadata from http://rubygems.org/.
> Resolving dependencies...
> Your bundle is locked to mimemagic (0.3.2), but that version could not be
> found in any of the sources listed in your Gemfile. If you haven't changed
> sources, that means the author of mimemagic (0.3.2) has
> removed it. You'll need to update your bundle to a different version of
> mimemagic (0.3.2) that hasn't been removed in order to install.
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9066) Docker-based documentation generation is broken
Alberto Bustamante Reyes created GEODE-9066:
---
Summary: Docker-based documentation generation is broken
Key: GEODE-9066
URL: https://issues.apache.org/jira/browse/GEODE-9066
Project: Geode
Issue Type: Improvement
Components: docs
Reporter: Alberto Bustamante Reyes
`view-docs.sh` script is not working, it seems one Ruby dependency has to be
updated
{code}
$ ./view-docs.sh
Building geode/docsbuild:0.1 image...
sha256:c79da695299c58856b901cd309fdcf785ee1bce0451d687fd9592d1371562916
Building geode/docsbuild:0.1-alb3rtobr image...
sha256:524290937f1c0fd846ef87bc7e1edb53a98f3af997e3a25b54b2eb66def890ad
Starting up web server...
Fetching gem metadata from http://rubygems.org/
Fetching version metadata from http://rubygems.org/.
Resolving dependencies...
Your bundle is locked to mimemagic (0.3.2), but that version could not be found
in any of the sources listed in your Gemfile. If you haven't changed sources,
that means the author of mimemagic (0.3.2) has
removed it. You'll need to update your bundle to a different version of
mimemagic (0.3.2) that hasn't been removed in order to install.
...
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9063) Make mandatory options to appear first when autocompleting in gfsh
Alberto Bustamante Reyes created GEODE-9063: --- Summary: Make mandatory options to appear first when autocompleting in gfsh Key: GEODE-9063 URL: https://issues.apache.org/jira/browse/GEODE-9063 Project: Geode Issue Type: Improvement Components: gfsh Reporter: Alberto Bustamante Reyes When writting a command in gfsh followed by "--" and then pressing "tab" to obtain command completion suggestions, the mandatory options should be shown in first place. This was recently fixed in GEODE-9034 for "create gateway-sender" but there are some more commands to be fixed: * change log-level * create disk-store * create jndi-binding * destroy gateway-sender * export data * import data * remove -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9063) Make mandatory options to appear first when autocompleting in gfsh
[ https://issues.apache.org/jira/browse/GEODE-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes reassigned GEODE-9063: --- Assignee: Alberto Bustamante Reyes > Make mandatory options to appear first when autocompleting in gfsh > -- > > Key: GEODE-9063 > URL: https://issues.apache.org/jira/browse/GEODE-9063 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > > When writting a command in gfsh followed by "--" and then pressing "tab" to > obtain command completion suggestions, the mandatory options should be shown > in first place. > This was recently fixed in GEODE-9034 for "create gateway-sender" but there > are some more commands to be fixed: > * change log-level > * create disk-store > * create jndi-binding > * destroy gateway-sender > * export data > * import data > * remove -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9062) DataSerializableJUnitTest fails in StressTest task
[
https://issues.apache.org/jira/browse/GEODE-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes updated GEODE-9062:
Description:
DataSerializableJUnitTest is failing if executed using the "repeatUnitTest"
gradle task. I dont know what is causing this failure, but I got the error when
verifying a PR ( [https://concourse.apachegeode-ci.info/builds/17155] ) and I
realized it is failing in develop branch too.
{code}
~/git/apache/geode (develop) $ ./gradlew geode-core:repeatUnitTest
--tests=DataSerializableJUnitTest
...
org.apache.geode.internal.DataSerializableJUnitTest > testUDDS2 FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testUDDS2(DataSerializableJUnitTest.java:2284)
org.apache.geode.internal.DataSerializableJUnitTest > testUDDS4 FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testUDDS4(DataSerializableJUnitTest.java:2307)
org.apache.geode.internal.DataSerializableJUnitTest > testSupportedClasses
FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testSupportedClasses(DataSerializableJUnitTest.java:2260)
11100 tests completed, 297 failed, 200 skipped
> Task :geode-core:repeatUnitTest FAILED
> Task :combineReports
All test reports at /home/alb3rtobr/git/apache/geode/build/reports/combined
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-core:repeatUnitTest'.
> There were failing tests. See the report at:
> file:///home/alb3rtobr/git/apache/geode/geode-core/build/reports/repeatUnitTest/index.html
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 1m 8s
36 actionable tasks: 2 executed, 34 up-to-date
~/git/apache/geode (develop) $ git log -n 1
commit a45dbf94de2f35b869a3dd0e1cf945f5282e2fd0 (HEAD -> develop,
origin/develop, origin/HEAD)
Author: Mario Kevo <48509719+mk...@users.noreply.github.com>
Date: Wed Mar 24 10:25:29 2021 +0100
GEODE-8962: add an option to escape dollar($) character in the query (#6044)
* GEODE-8962: add an option to escape dollar($) character in the query
{code}
Three tests are failing: testSupportedClasses, testUDDS2 and testUDDS4.
was:
DataSerializableJUnitTest is failing if executed using the "repeatUnitTest"
gradle task. I dont know what is causing this failure, but I got the error when
verifying a PR ( [https://concourse.apachegeode-ci.info/builds/17155] ) and I
realized it is failing in develop branch too.
{code}
alb3rtobr@alb3rtobr-XPS ~/git/apache/geode (develop) $ ./gradlew
geode-core:repeatUnitTest --tests=DataSerializableJUnitTest
...
org.apache.geode.internal.DataSerializableJUnitTest > testUDDS2 FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testUDDS2(DataSerializableJUnitTest.java:2284)
org.apache.geode.internal.DataSerializableJUnitTest > testUDDS4 FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testUDDS4(DataSerializableJUnitTest.java:2307)
org.apache.geode.internal.DataSerializableJUnitTest > testSupportedClasses
FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testSupportedClasses(DataSerializableJUnitTest.java:2260)
11100 tests completed, 297 failed, 200 skipped
> Task :geode-core:repeatUnitTest FAILED
> Task :combineReports
All test reports at /home/alb3rtobr/git/apache/geode/build/reports/combined
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-core:repeatUnitTest'.
> There were failing tests. See the report
[jira] [Resolved] (GEODE-9041) Add optional reviewer to CODEWATCHERS
[ https://issues.apache.org/jira/browse/GEODE-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Bustamante Reyes resolved GEODE-9041. - Fix Version/s: 1.15.0 Resolution: Fixed > Add optional reviewer to CODEWATCHERS > - > > Key: GEODE-9041 > URL: https://issues.apache.org/jira/browse/GEODE-9041 > Project: Geode > Issue Type: Improvement >Reporter: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > I'd like to be added to a couple of sections in the CODEWATCHERS file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9062) DataSerializableJUnitTest fails in StressTest task
[
https://issues.apache.org/jira/browse/GEODE-9062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-9062:
---
Assignee: Alberto Bustamante Reyes
> DataSerializableJUnitTest fails in StressTest task
> --
>
> Key: GEODE-9062
> URL: https://issues.apache.org/jira/browse/GEODE-9062
> Project: Geode
> Issue Type: Bug
>Reporter: Alberto Bustamante Reyes
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> DataSerializableJUnitTest is failing if executed using the "repeatUnitTest"
> gradle task. I dont know what is causing this failure, but I got the error
> when verifying a PR ( [https://concourse.apachegeode-ci.info/builds/17155] )
> and I realized it is failing in develop branch too.
> {code}
> alb3rtobr@alb3rtobr-XPS ~/git/apache/geode (develop) $ ./gradlew
> geode-core:repeatUnitTest --tests=DataSerializableJUnitTest
> ...
> org.apache.geode.internal.DataSerializableJUnitTest > testUDDS2 FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.geode.internal.DataSerializableJUnitTest.testUDDS2(DataSerializableJUnitTest.java:2284)
> org.apache.geode.internal.DataSerializableJUnitTest > testUDDS4 FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.geode.internal.DataSerializableJUnitTest.testUDDS4(DataSerializableJUnitTest.java:2307)
> org.apache.geode.internal.DataSerializableJUnitTest > testSupportedClasses
> FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:87)
> at org.junit.Assert.assertTrue(Assert.java:42)
> at org.junit.Assert.assertFalse(Assert.java:65)
> at org.junit.Assert.assertFalse(Assert.java:75)
> at
> org.apache.geode.internal.DataSerializableJUnitTest.testSupportedClasses(DataSerializableJUnitTest.java:2260)
> 11100 tests completed, 297 failed, 200 skipped
> > Task :geode-core:repeatUnitTest FAILED
> > Task :combineReports
> All test reports at /home/alb3rtobr/git/apache/geode/build/reports/combined
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geode-core:repeatUnitTest'.
> > There were failing tests. See the report at:
> > file:///home/alb3rtobr/git/apache/geode/geode-core/build/reports/repeatUnitTest/index.html
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output. Run with --scan to get full insights.
> * Get more help at https://help.gradle.org
> BUILD FAILED in 1m 8s
> 36 actionable tasks: 2 executed, 34 up-to-date
> alb3rtobr@alb3rtobr-XPS ~/git/apache/geode (develop) $ git log -n 1
> commit a45dbf94de2f35b869a3dd0e1cf945f5282e2fd0 (HEAD -> develop,
> origin/develop, origin/HEAD)
> Author: Mario Kevo <48509719+mk...@users.noreply.github.com>
> Date: Wed Mar 24 10:25:29 2021 +0100
> GEODE-8962: add an option to escape dollar($) character in the query (#6044)
>
> * GEODE-8962: add an option to escape dollar($) character in the query
> {code}
> Three tests are failing: testSupportedClasses, testUDDS2 and testUDDS4.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9062) DataSerializableJUnitTest fails in StressTest task
Alberto Bustamante Reyes created GEODE-9062:
---
Summary: DataSerializableJUnitTest fails in StressTest task
Key: GEODE-9062
URL: https://issues.apache.org/jira/browse/GEODE-9062
Project: Geode
Issue Type: Bug
Reporter: Alberto Bustamante Reyes
DataSerializableJUnitTest is failing if executed using the "repeatUnitTest"
gradle task. I dont know what is causing this failure, but I got the error when
verifying a PR ( [https://concourse.apachegeode-ci.info/builds/17155] ) and I
realized it is failing in develop branch too.
{code}
alb3rtobr@alb3rtobr-XPS ~/git/apache/geode (develop) $ ./gradlew
geode-core:repeatUnitTest --tests=DataSerializableJUnitTest
...
org.apache.geode.internal.DataSerializableJUnitTest > testUDDS2 FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testUDDS2(DataSerializableJUnitTest.java:2284)
org.apache.geode.internal.DataSerializableJUnitTest > testUDDS4 FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testUDDS4(DataSerializableJUnitTest.java:2307)
org.apache.geode.internal.DataSerializableJUnitTest > testSupportedClasses
FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertFalse(Assert.java:65)
at org.junit.Assert.assertFalse(Assert.java:75)
at
org.apache.geode.internal.DataSerializableJUnitTest.testSupportedClasses(DataSerializableJUnitTest.java:2260)
11100 tests completed, 297 failed, 200 skipped
> Task :geode-core:repeatUnitTest FAILED
> Task :combineReports
All test reports at /home/alb3rtobr/git/apache/geode/build/reports/combined
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-core:repeatUnitTest'.
> There were failing tests. See the report at:
> file:///home/alb3rtobr/git/apache/geode/geode-core/build/reports/repeatUnitTest/index.html
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 1m 8s
36 actionable tasks: 2 executed, 34 up-to-date
alb3rtobr@alb3rtobr-XPS ~/git/apache/geode (develop) $ git log -n 1
commit a45dbf94de2f35b869a3dd0e1cf945f5282e2fd0 (HEAD -> develop,
origin/develop, origin/HEAD)
Author: Mario Kevo <48509719+mk...@users.noreply.github.com>
Date: Wed Mar 24 10:25:29 2021 +0100
GEODE-8962: add an option to escape dollar($) character in the query (#6044)
* GEODE-8962: add an option to escape dollar($) character in the query
{code}
Three tests are failing: testSupportedClasses, testUDDS2 and testUDDS4.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9059) Remove DataSerializer.DUMP_SERIALIZED references from docs
Alberto Bustamante Reyes created GEODE-9059:
---
Summary: Remove DataSerializer.DUMP_SERIALIZED references from docs
Key: GEODE-9059
URL: https://issues.apache.org/jira/browse/GEODE-9059
Project: Geode
Issue Type: Improvement
Components: docs
Reporter: Alberto Bustamante Reyes
System property "DataSerializer.DUMP_SERIALIZED" is not used in code but it is
mentioned in documentation in
"geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb"
{quote}
To determine if you are using standard Java serialization, specify the
-DDataSerializer.DUMP_SERIALIZED=true upon process execution. Then check your
log for messages of this form:
DataSerializer Serializing an instance of
Any classes list are being serialized with standard Java serialization.
{quote}
Seems these logs can be obtained by using log markers, but it should be
documented.
>From InternalDataSerializer.basicWriteObject:
{code}
if (logger.isTraceEnabled(LogMarker.SERIALIZER_ANNOUNCE_TYPE_WRITTEN_VERBOSE)){
logger.trace(LogMarker.SERIALIZER_ANNOUNCE_TYPE_WRITTEN_VERBOSE,
"DataSerializer Serializing an instance of {}",
o.getClass().getName());
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8985) documentation speaks of start-recovery-delay when it means startup-recovery-delay
[
https://issues.apache.org/jira/browse/GEODE-8985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes resolved GEODE-8985.
-
Fix Version/s: 1.15.0
Resolution: Fixed
> documentation speaks of start-recovery-delay when it means
> startup-recovery-delay
> -
>
> Key: GEODE-8985
> URL: https://issues.apache.org/jira/browse/GEODE-8985
> Project: Geode
> Issue Type: Task
> Components: docs
>Affects Versions: 1.15.0
>Reporter: Bill Burcham
>Assignee: Alberto Bustamante Reyes
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
> Attachments: image-2021-03-01-11-34-08-373.png
>
>
> There is no such thing as {{start-recovery-delay}} yet the documentation
> mentions it in a few places. Replace with {{startup-recovery-delay}}
> (partition attribute)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8801) properties.html contains inaccurate information
[
https://issues.apache.org/jira/browse/GEODE-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17303523#comment-17303523
]
Alberto Bustamante Reyes commented on GEODE-8801:
-
I will also transform the document to markdown format. It will be easier to
edit the file.
> properties.html contains inaccurate information
> ---
>
> Key: GEODE-8801
> URL: https://issues.apache.org/jira/browse/GEODE-8801
> Project: Geode
> Issue Type: Improvement
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> The file {{org/apache/geode/internal/cache/properties.html}} contains a list
> of several System properties that are used by Geode, as well as their default
> values. This list is for developer reference and is not referred to in any
> user-facing documentation, but is possibly incomplete and has not been
> maintained for some time.
> # Any properties referred to in the file that are no longer used should be
> removed
> # Any default values in the file that do not match the actual default should
> be updated
> # The "Public" field for each property is no longer meaningful and can be
> removed
> # Any System properties that are used by Geode but not listed in the file
> should be added
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-8801) properties.html contains inaccurate information
[
https://issues.apache.org/jira/browse/GEODE-8801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Bustamante Reyes reassigned GEODE-8801:
---
Assignee: Alberto Bustamante Reyes
> properties.html contains inaccurate information
> ---
>
> Key: GEODE-8801
> URL: https://issues.apache.org/jira/browse/GEODE-8801
> Project: Geode
> Issue Type: Improvement
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Alberto Bustamante Reyes
>Priority: Major
>
> The file {{org/apache/geode/internal/cache/properties.html}} contains a list
> of several System properties that are used by Geode, as well as their default
> values. This list is for developer reference and is not referred to in any
> user-facing documentation, but is possibly incomplete and has not been
> maintained for some time.
> # Any properties referred to in the file that are no longer used should be
> removed
> # Any default values in the file that do not match the actual default should
> be updated
> # The "Public" field for each property is no longer meaningful and can be
> removed
> # Any System properties that are used by Geode but not listed in the file
> should be added
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
