Got it. Thank you Barry. Sushil Chaudhary Email: [email protected]
From: Barry Oglesby <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, July 11, 2016 at 1:25 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Monitoring the latency and disc through put The start server command won't pick up the properties from that directory by default. You'll need to specify the directory like: gfsh>start server ... --properties-file=/path/to/gemfire.properties btw - if you're starting a locator (and you should be), you shouldn't also specify mcast-port. In that case, the locator is the member discovery mechanism. So, define a gemfire.properties file in a config dir like: log-level=config log-file=cacheserver.log mcast-port=0 locators=localhost[21212] statistic-archive-file=cacheserver.gfs statistic-sampling-enabled=true conserve-sockets=false enable-time-statistics=true Start the locator like: gfsh> start locator --name=locator1 --port=21212 Start the server like: start server --name=server1 --properties-file=config/gemfire.properties You cacheserver.log file should contain: ### GemFire Properties defined with file:/path/to/config/gemfire.properties ### conserve-sockets=false enable-time-statistics=true locators=localhost[21212] log-file=cacheserver.log log-level=config mcast-port=0 statistic-archive-file=cacheserver.gfs statistic-sampling-enabled=true Thanks, Barry Oglesby On Mon, Jul 11, 2016 at 7:05 AM, Chaudhary, Sushil (CONT) <[email protected]<mailto:[email protected]>> wrote: Barry, I re-started the geode server. Still it is not picking up the properties from apache-geode-1.0.0-incubating.M2/config/gemfire.properties. It is stuck at its default values as below. Something wrong here. Do I need to supply property name as arg in the server. This is how I am starting the server and locator: gfsh>start locator --name=locator1 --port=9009 --mcast-port=10338 --max-heap=50G; gfsh>start server --name=server1 --mcast-port=10338 --server-port=40404 --max-heap=50G --off-heap-memory-size=50G --critical-off-heap-percentage=90; Thanks, Sushil Chaudhary Cell #: 408-466-2004<tel:408-466-2004> Email: [email protected]<mailto:[email protected]> From: Barry Oglesby <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, July 7, 2016 at 2:46 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Monitoring the latency and disc through put Yes, thats right. Its doesn't get re-loaded into a running system. Thanks, Barry Oglesby On Thu, Jul 7, 2016 at 11:31 AM, Chaudhary, Sushil (CONT) <[email protected]<mailto:[email protected]>> wrote: Hi, I am setting it in geode/config/gemfire.properites. Looks like I need to restart IMDB to see it reflected in the log. server1.log [info 2016/07/07 10:45:47.416 EDT server1 <main> tid=0x1] Startup Configuration: ### GemFire Properties defined with system property ### mcast-port=10338 off-heap-memory-size=50G use-cluster-configuration=true ### GemFire Properties defined with api ### name=server1 ### GemFire Properties defined with launcher ### locators=10.205.82.40[9009] log-file=server1.log ### GemFire Properties using default values ### ack-severe-alert-threshold=0 ack-wait-threshold=15 archive-disk-space-limit=0 archive-file-size-limit=0 async-distribution-timeout=0 async-max-queue-size=8 async-queue-timeout=60000 bind-address= cache-xml-file=cache.xml cluster-configuration-dir=/home/ec2-user/server1 cluster-ssl-ciphers=any cluster-ssl-enabled=false cluster-ssl-keystore= cluster-ssl-keystore-password= cluster-ssl-keystore-type= cluster-ssl-protocols=any cluster-ssl-require-authentication=true cluster-ssl-truststore= cluster-ssl-truststore-password= conflate-events=server conserve-sockets=true delta-propagation=true deploy-working-dir=. disable-auto-reconnect=false disable-tcp=false distributed-system-id=-1 distributed-transactions=false durable-client-id= durable-client-timeout=300 enable-cluster-configuration=true enable-network-partition-detection=false enable-time-statistics=false enforce-unique-host=false gateway-ssl-ciphers=any Sushil Chaudhary Email: [email protected]<mailto:[email protected]> From: Barry Oglesby <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, July 7, 2016 at 1:04 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Monitoring the latency and disc through put If I set statistic-sampling-enabled=false, I don't see any rate stats either. Sushil: How are you setting enable-time-stats=true? Do you have a server log you can post? Thanks, Barry Oglesby On Thu, Jul 7, 2016 at 9:36 AM, Swapnil Bawaskar <[email protected]<mailto:[email protected]>> wrote: Hi Sushil, According to the docs<http://geode.docs.pivotal.io/docs/reference/topics/gemfire_properties.html>, you need to set two more properties as described below: enable-time-statistics Boolean instructing the system to track time-based statistics for the distributed system and caching. Disabled by default for performance reasons and not recommended for production environments. You must also configurestatistics-sampling-enabled to true and specify a statistics-archive-file. false On Thu, Jul 7, 2016 at 9:10 AM, Chaudhary, Sushil (CONT) <[email protected]<mailto:[email protected]>> wrote: Barry, Thanks for the below. I have had enable-time-statistics=true in gemfire.properties. But still I do see lantecies as 0. Am I missing something ? Cluster-wide Region Metrics Category | Metric | Value --------- | ---------------------------- | ------- cluster | member count | 2 | region entry count | 7453666 region | lastModifiedTime | -1 | lastAccessedTime | -1 | missCount | -1 | hitCount | -1 | hitRatio | -1 | getsRate | 33158 | putsRate | 16580 | createsRate | 0 | destroyRate | 0 | putAllRate | 0 partition | putLocalRate | 16580 | putRemoteRate | 0 | putRemoteLatency | 0 | putRemoteAvgLatency | 0 | bucketCount | 113 | primaryBucketCount | 113 | numBucketsWithoutRedundancy | 0 | totalBucketSize | 7453666 | averageBucketSize | 32980 diskstore | totalEntriesOnlyOnDisk | 0 | diskReadsRate | 0 | diskWritesRate | 0 | totalDiskWriteInProgress | 0 | diskTaskWaiting | 0 callback | cacheWriterCallsAvgLatency | 0 | cacheListenerCallsAvgLatency | 0 eviction | lruEvictionRate | 0 | lruDestroyRate | 0 Sushil Chaudhary Email: [email protected]<mailto:[email protected]> From: Barry Oglesby <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Wednesday, July 6, 2016 at 5:43 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Monitoring the latency and disc through put You can also use the gfsh show metrics command to see rates and latencies like: gfsh -e "connect --locator=localhost[23456]" -e "show metrics --region=/data" That will log output for the 'data' region like below. The rate stats are per second. The latency stats are in nanoseconds. You'll need to set enable-time-statistics=true to see latencies. Executing - show metrics --region=/data Cluster-wide Region Metrics Category | Metric | Value --------- | ---------------------------- | ------ cluster | member count | 2 | region entry count | 10000 region | lastModifiedTime | -1 | lastAccessedTime | -1 | missCount | -1 | hitCount | -1 | hitRatio | -1 | getsRate | 0 | putsRate | 10396 | createsRate | 0 | destroyRate | 0 | putAllRate | 0 partition | putLocalRate | 5189 | putRemoteRate | 5207 | putRemoteLatency | 160965 | putRemoteAvgLatency | 163281 | bucketCount | 226 | primaryBucketCount | 113 | numBucketsWithoutRedundancy | 0 | totalBucketSize | 20000 | averageBucketSize | 44 diskstore | totalEntriesOnlyOnDisk | 0 | diskReadsRate | 0 | diskWritesRate | 0 | totalDiskWriteInProgress | 0 | diskTaskWaiting | 0 callback | cacheWriterCallsAvgLatency | 0 | cacheListenerCallsAvgLatency | 0 eviction | lruEvictionRate | 0 | lruDestroyRate | 0 Thanks, Barry Oglesby On Wed, Jul 6, 2016 at 2:31 PM, Chaudhary, Sushil (CONT) <[email protected]<mailto:[email protected]>> wrote: Thanks John, let me try with the same. Sushil Chaudhary From: John Blum <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Wednesday, July 6, 2016 at 5:21 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Monitoring the latency and disc through put You have to enable stats on your application-defined Regions. You do that via the API<http://data-docs-samples.cfapps.io/docs-gemfire/latest/javadocs/japi/com/gemstone/gemfire/cache/RegionFactory.html#setStatisticsEnabled(boolean)> [1], or with cache.xml<http://gemfire.docs.pivotal.io/docs-gemfire/latest/reference/topics/cache_xml.html#region-attributes> [2] (search for statistics-enabled) for via Spring Data GemFire, by example... <gfe:partitioned-region id="Example" statistics="true"/> Note, the default value is false, since recording statistics will incur more overhead. Hope this helps. Cheers, John [1] [2] http://gemfire.docs.pivotal.io/docs-gemfire/latest/reference/topics/cache_xml.html#region-attributes On Wed, Jul 6, 2016 at 2:12 PM, Chaudhary, Sushil (CONT) <[email protected]<mailto:[email protected]>> wrote: Hi, I am using geode with Apex. Can anyone please guide me how can I monitor latency and through put for each get and put. I am not getting stars on Geode UI, it always says Zero. Sushil Chaudhary Cell #: 408-466-2004<tel:408-466-2004> Email: [email protected]<mailto:[email protected]> ________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. -- -John 503-504-8657<tel:503-504-8657> john.blum10101 (skype) ________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. ________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. ________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. ________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer. ________________________________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
