Re: [DISCUSS] Someone to update 3rd-party libraries used by Geode
Thanks for the reminder, Dave. I'll have a go at it. On 9/10/20, 9:36 AM, "Dave Barnes" wrote: Hello Apache Geode Community, We need a volunteer to update the 3rd-party libraries used by Geode. This consists of going through the libraries we depend on and updating each to the latest version that works with our code. It would be nice to get this done within the next week or two so that we have time to shake out issues before the next release. Regards, Dave Barnes on behalf of the Apache Geode Team
Re: Proper location for debugging tools
The main geode repo has a dev-tools directory, that’s a good spot for scripts. If it’s specific to native client I’d put it in geode-native but if not the geode repo seems fine. -Dan > On Sep 11, 2020, at 1:41 PM, Blake Bender wrote: > > Hi all, > > I have a Python script I’ve used quite a bit for diagnosing/debugging issues > in geode-native that can decode a whole lot of protocol information from a > debug-level log file. I think it comes in pretty handy, and would like to > share. Just a quick question, though – where’s the right place to put it? > It’s currently in a private repo, so I could create a new OSS repo for it, or > I could do something like create a /tools folder in the native tree and > submit it there in a PR. There’s also a sort-of shared tools area in the > Geode repo proper, which isn’t as odd a choice as it first seems, because the > script could be enhanced pretty readily to read Java client logs and decode > the same info. Anyone have any strongly-held opinions? > > Thanks, > > Blake >
Proper location for debugging tools
Hi all, I have a Python script I’ve used quite a bit for diagnosing/debugging issues in geode-native that can decode a whole lot of protocol information from a debug-level log file. I think it comes in pretty handy, and would like to share. Just a quick question, though – where’s the right place to put it? It’s currently in a private repo, so I could create a new OSS repo for it, or I could do something like create a /tools folder in the native tree and submit it there in a PR. There’s also a sort-of shared tools area in the Geode repo proper, which isn’t as odd a choice as it first seems, because the script could be enhanced pretty readily to read Java client logs and decode the same info. Anyone have any strongly-held opinions? Thanks, Blake
Re: Colocated regions missing some buckets after restart
Are you seeing no-buckets for persistent regions or non-persistent. The buckets are created dynamically; when data is added to corresponding buckets... When server is restarted, in case of in-memory regions as the data is not there, the bucket region may not have been created (my suspicion). Can you try adding data and see if the co-located bucket region gets created in respective nodes/server. -Anil. On 9/11/20, 9:46 AM, "Mario Kevo" wrote: Hi geode-dev, We have a system with two servers and a few regions. One region is persistent and other are not but they are colocated with this persistent region. After servers restart on some region we can see that they don't have any bucket. gfsh>show metrics --member=server-1 --region=/region1 --categories=partition Metrics for region:/region1 On Member server-1 Category |Metric| Value - | | - partition | putLocalRate | 0.0 | putRemoteRate| 0.0 | putRemoteLatency | 0 | putRemoteAvgLatency | 0 | bucketCount | 0 | primaryBucketCount | 0 | configuredRedundancy | 1 | actualRedundancy | 0 | numBucketsWithoutRedundancy | 113 | totalBucketSize | 0 gfsh>show metrics --member=server-0 --region=/region1 --categories=partition Metrics for region:/region1 On Member server-0 Category |Metric| Value - | | - partition | putLocalRate | 0.0 | putRemoteRate| 0.0 | putRemoteLatency | 0 | putRemoteAvgLatency | 0 | bucketCount | 113 | primaryBucketCount | 56 | configuredRedundancy | 1 | actualRedundancy | 0 | numBucketsWithoutRedundancy | 113 | totalBucketSize | 0 The persistent region is ok, but some of these colocated regions has this issue. We also wait some time, but it doesn't change. Does anyone have some idea about this problem, what causing the issue? The issue can be easily reproduced with two locators, two servers, one persistent region and few non-persistent regions colocated with persistent one. After restart both servers and try to do show metrics command you will got this issue for some regions. BR, Mario
Colocated regions missing some buckets after restart
Hi geode-dev, We have a system with two servers and a few regions. One region is persistent and other are not but they are colocated with this persistent region. After servers restart on some region we can see that they don't have any bucket. gfsh>show metrics --member=server-1 --region=/region1 --categories=partition Metrics for region:/region1 On Member server-1 Category |Metric| Value - | | - partition | putLocalRate | 0.0 | putRemoteRate| 0.0 | putRemoteLatency | 0 | putRemoteAvgLatency | 0 | bucketCount | 0 | primaryBucketCount | 0 | configuredRedundancy | 1 | actualRedundancy | 0 | numBucketsWithoutRedundancy | 113 | totalBucketSize | 0 gfsh>show metrics --member=server-0 --region=/region1 --categories=partition Metrics for region:/region1 On Member server-0 Category |Metric| Value - | | - partition | putLocalRate | 0.0 | putRemoteRate| 0.0 | putRemoteLatency | 0 | putRemoteAvgLatency | 0 | bucketCount | 113 | primaryBucketCount | 56 | configuredRedundancy | 1 | actualRedundancy | 0 | numBucketsWithoutRedundancy | 113 | totalBucketSize | 0 The persistent region is ok, but some of these colocated regions has this issue. We also wait some time, but it doesn't change. Does anyone have some idea about this problem, what causing the issue? The issue can be easily reproduced with two locators, two servers, one persistent region and few non-persistent regions colocated with persistent one. After restart both servers and try to do show metrics command you will got this issue for some regions. BR, Mario
