[jira] [Commented] (GEODE-6777) Create gateway senders command should only return when DistributedSystemMXBean reflects creation status
[
https://issues.apache.org/jira/browse/GEODE-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860409#comment-16860409
]
Aaron Lindsey commented on GEODE-6777:
--
Can this be closed since the PR is merged?
> Create gateway senders command should only return when
> DistributedSystemMXBean reflects creation status
> ---
>
> Key: GEODE-6777
> URL: https://issues.apache.org/jira/browse/GEODE-6777
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jens Deppe
>Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently, the following sequence of commands will fail:
> {noformat}
> $GEODE_HOME/bin/gfsh -e "connect --locator=localhost[10334]" \
> -e "create gateway-sender --id=gs --parallel=false
> --remote-distributed-system-id=1" \
> -e "create region --name=region --type=REPLICATE
> --gateway-sender-id=gs"{noformat}
> With an error indicating that the gateway sender does not exist. This is due
> to the time it takes for the creation to be registered in the
> {{DistributedSystemMXBean}}. We should only return from this command once the
> appropriate constructs are visible in the bean.
> Once fixed, we can remove
> {{MemberVM.waitUntilGatewaySendersAreReadyOnExactlyThisManyServers}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5222) JMX metric exposed in an MBean
[ https://issues.apache.org/jira/browse/GEODE-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852358#comment-16852358 ] Aaron Lindsey commented on GEODE-5222: -- In [RegionMXBean|[https://geode.apache.org/releases/latest/javadoc/org/apache/geode/management/RegionMXBean.html]], there are examples of metrics that return -1 (int) or -1.0 (float) under scenarios when the value is not applicable. In one such example, getPutLocalRate() returns ManagementConstants.NOT_AVAILABLE_FLOAT when the region is not a partitioned region . I think we could do the same thing here when the operator does not specify directory sizes. > JMX metric exposed in an MBean > -- > > Key: GEODE-5222 > URL: https://issues.apache.org/jira/browse/GEODE-5222 > Project: Geode > Issue Type: Improvement > Components: docs, persistence >Reporter: Nick Vallely >Assignee: Alberto Bustamante Reyes >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Given I need to scale down or scale up my servers based on usage > When I setup my monitoring of JMX metrics through an MBean > Then I have the ability to see Disk Free Percentage > AND Disk Free in Bytes > AND Disk Used Percentage > AND Disk Used in Bytes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-5222) JMX metric exposed in an MBean
[ https://issues.apache.org/jira/browse/GEODE-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852358#comment-16852358 ] Aaron Lindsey edited comment on GEODE-5222 at 5/30/19 8:59 PM: --- In RegionMXBean, there are examples of metrics that return -1 (int) or -1.0 (float) under scenarios when the value is not applicable. In one such example, getPutLocalRate() returns ManagementConstants.NOT_AVAILABLE_FLOAT when the region is not a partitioned region . I think we could do the same thing here when the operator does not specify directory sizes. was (Author: aaronlindsey): In [RegionMXBean|[https://geode.apache.org/releases/latest/javadoc/org/apache/geode/management/RegionMXBean.html]], there are examples of metrics that return -1 (int) or -1.0 (float) under scenarios when the value is not applicable. In one such example, getPutLocalRate() returns ManagementConstants.NOT_AVAILABLE_FLOAT when the region is not a partitioned region . I think we could do the same thing here when the operator does not specify directory sizes. > JMX metric exposed in an MBean > -- > > Key: GEODE-5222 > URL: https://issues.apache.org/jira/browse/GEODE-5222 > Project: Geode > Issue Type: Improvement > Components: docs, persistence >Reporter: Nick Vallely >Assignee: Alberto Bustamante Reyes >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > Given I need to scale down or scale up my servers based on usage > When I setup my monitoring of JMX metrics through an MBean > Then I have the ability to see Disk Free Percentage > AND Disk Free in Bytes > AND Disk Used Percentage > AND Disk Used in Bytes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5222) JMX metric exposed in an MBean
[ https://issues.apache.org/jira/browse/GEODE-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851367#comment-16851367 ] Aaron Lindsey commented on GEODE-5222: -- The operator has the ability to not specify a directory size when creating a disk store. In this case, the system will assume unlimited storage. What should these metrics show for disk free and disk free/used percentage when the directory size is not specified? > JMX metric exposed in an MBean > -- > > Key: GEODE-5222 > URL: https://issues.apache.org/jira/browse/GEODE-5222 > Project: Geode > Issue Type: Improvement > Components: docs, persistence >Reporter: Nick Vallely >Assignee: Alberto Bustamante Reyes >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > Given I need to scale down or scale up my servers based on usage > When I setup my monitoring of JMX metrics through an MBean > Then I have the ability to see Disk Free Percentage > AND Disk Free in Bytes > AND Disk Used Percentage > AND Disk Used in Bytes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6783) Remove Thread.sleep() from GatewayReceiverMetricsTest @before method
[ https://issues.apache.org/jira/browse/GEODE-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16842574#comment-16842574 ] Aaron Lindsey commented on GEODE-6783: -- Linked issue must be resolved before removing Thread.sleep() > Remove Thread.sleep() from GatewayReceiverMetricsTest @before method > > > Key: GEODE-6783 > URL: https://issues.apache.org/jira/browse/GEODE-6783 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Aaron Lindsey >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6783) Remove Thread.sleep() from GatewayReceiverMetricsTest @before method
Aaron Lindsey created GEODE-6783: Summary: Remove Thread.sleep() from GatewayReceiverMetricsTest @before method Key: GEODE-6783 URL: https://issues.apache.org/jira/browse/GEODE-6783 Project: Geode Issue Type: Improvement Components: statistics Reporter: Aaron Lindsey -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6683) java.lang.NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey updated GEODE-6683:
-
Fix Version/s: 1.10.0
> java.lang.NullPointerException
> --
>
> Key: GEODE-6683
> URL: https://issues.apache.org/jira/browse/GEODE-6683
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Affects Versions: 1.6.0
>Reporter: YE LIN
>Assignee: Aaron Lindsey
>Priority: Major
> Labels: observability
> Fix For: 1.10.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> when Pulse is ran without embedded mode in Locator, throw NullPointException
> during running code : repository.getJavaSslProperties().stringPropertyNames()
> look like repository.javaSslProperties is null.
> {noformat}
> 2019-04-24 02:08:06,767 INFO o.a.g.t.p.i.d.JMXDataUpdater
> [http-nio-7070-exec-1] Locator has found a jmx manager: Host=10.116.37.211 &
> Port=1099, with SSL
> 2019-04-24 02:08:06,773 FATAL o.a.g.t.p.i.d.JMXDataUpdater
> [http-nio-7070-exec-1] null
> java.lang.NullPointerException: null
> at
> org.apache.geode.tools.pulse.internal.data.JMXDataUpdater.connect(JMXDataUpdater.java:217)
> [classes/:?]
> at
> org.apache.geode.tools.pulse.internal.data.Cluster.connectToGemFire(Cluster.java:2805)
> [classes/:?]
> at
> org.apache.geode.tools.pulse.internal.data.Repository.getCluster(Repository.java:139)
> [classes/:?]
> at
> org.apache.geode.tools.pulse.internal.security.GemFireAuthenticationProvider.authenticate(GemFireAuthenticationProvider.java:57)
> [classes/:?]
> at
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-6683) java.lang.NullPointerException
[
https://issues.apache.org/jira/browse/GEODE-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey resolved GEODE-6683.
--
Resolution: Fixed
> java.lang.NullPointerException
> --
>
> Key: GEODE-6683
> URL: https://issues.apache.org/jira/browse/GEODE-6683
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Affects Versions: 1.6.0
>Reporter: YE LIN
>Assignee: Aaron Lindsey
>Priority: Major
> Labels: observability
> Fix For: 1.10.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> when Pulse is ran without embedded mode in Locator, throw NullPointException
> during running code : repository.getJavaSslProperties().stringPropertyNames()
> look like repository.javaSslProperties is null.
> {noformat}
> 2019-04-24 02:08:06,767 INFO o.a.g.t.p.i.d.JMXDataUpdater
> [http-nio-7070-exec-1] Locator has found a jmx manager: Host=10.116.37.211 &
> Port=1099, with SSL
> 2019-04-24 02:08:06,773 FATAL o.a.g.t.p.i.d.JMXDataUpdater
> [http-nio-7070-exec-1] null
> java.lang.NullPointerException: null
> at
> org.apache.geode.tools.pulse.internal.data.JMXDataUpdater.connect(JMXDataUpdater.java:217)
> [classes/:?]
> at
> org.apache.geode.tools.pulse.internal.data.Cluster.connectToGemFire(Cluster.java:2805)
> [classes/:?]
> at
> org.apache.geode.tools.pulse.internal.data.Repository.getCluster(Repository.java:139)
> [classes/:?]
> at
> org.apache.geode.tools.pulse.internal.security.GemFireAuthenticationProvider.authenticate(GemFireAuthenticationProvider.java:57)
> [classes/:?]
> at
> org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:174)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-6683) java.lang.NullPointerException
[ https://issues.apache.org/jira/browse/GEODE-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Lindsey reassigned GEODE-6683: Assignee: Aaron Lindsey (was: Kirk Lund) > java.lang.NullPointerException > -- > > Key: GEODE-6683 > URL: https://issues.apache.org/jira/browse/GEODE-6683 > Project: Geode > Issue Type: Bug > Components: pulse >Affects Versions: 1.6.0 >Reporter: YE LIN >Assignee: Aaron Lindsey >Priority: Major > Labels: observability > > *Context:* > when Pulse is ran without embedded mode in Locator, throw NullPointException > during running code : repository.getJavaSslProperties().stringPropertyNames() > look like repository.javaSslProperties is null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
