GemFire

可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试): 问题: I am trying to understand how to host a Spring Boot Gemfire server process. I found this example Spring Gemfire Server The problem I am having is the the server I am trying to add to the cluster is not showing up in the cluster after I start the process. Here are the steps I am taking: Start a new locator locally (default port): gfsh>start locator --name=loc-one I want to add this SpringBootGemfireServer to the cluster: note I have commented out the embeded locator start-up - I want to add this to the existing locator already running

locator 启动 locator gfsh> start locator --name=locator1 指定端口启动 gfsh> start locator --name=locator1 --port=12105 指定端口和绑定 ip 启动 gfsh> start locator --name=locator1 --port=12105 --bind-address=10.10.10.110 查看 locator 状态 gfsh> status locator --name=locator1 gfsh> status locator --host=localhost --port=10334 连接 locator gfsh> connect gfsh> connect --locator=localhost[10335] 关闭 locator gfsh> stop locator --name=locator1 关闭整个集群 gfsh> shutdown --include-locators=true server 启动 server gfsh> start server --name=server1 指定 locator 启动 gfsh> start server --name=server1 --locators=localhost[10334] 指定端口和

Is it possible to have a ClientCache with ClientRegionShortcut.PROXY along with programmatic control over entry TTL settings (i.e. entries present in the server)? I see the entry expiration ttl settings working fine with ClientRegionShortcut.CACHING_PROXY_HEAP_LRU . In this case I can see the entries getting invalidated in server after the configured timeout in seconds, but that is not the case for ClientRegionShortcut.PROXY settings Is it NOT possible to dynamically control the entry-ttl settings for a ClientCache ? Below code/config works with ClientRegionShortcut.CACHING_PROXY_HEAP_LRU and

We are working on a layered Java application that talks directly to Gemfire. We need to be able to generate unique "long" sequence numbers, guaranteed unique across all nodes of the application. (Not all nodes are clustered) Normally I would create a sequence in Oracle, but in this case, even though our Gemfire configuration has a connection to the relational database for write behind persistence, our application has no other knowledge of the database. What would be the best way to generate those guaranteed unique long values, without going to the database? The first question to ask yourself

I am having some memory issues with my application and need help understanding these statistics. Unix 'top' shows these stats for my process- VSZ: 37.4g RSS: 20.0g So, this means 20g is currently swapped in for the process and in use. However, when I print stats from within my application using Runtime class, I get this: Runtime.totalMemory() : 9.8G Runtime.freeMemory() : 3.6G Runtime.maxMemory() : 14.3G Why doesn't [Runtime.totalMemory() - Runtime.freeMemory()] match RSS? This is the memory currently in use by the process. There is a huge difference between the two numbers. Also, does the

I am new to Geode, and have started the default locator and server according to Geode in 5 minutes and then the .Net client with which I am running the tests from here // 1. Create a cache CacheFactory cacheFactory = CacheFactory.CreateCacheFactory(); Cache cache = cacheFactory.Create(); // 2. Create default region attributes using region factory RegionFactory regionFactory = cache.CreateRegionFactory(RegionShortcut.CACHING_PROXY); // 3. Create a region IRegion<int, string> region = regionFactory.Create<int, string>("exampleRegion"); // 4. Put some entries region[111] = "Value1"; region[123] =

最近，在工作中遇到一个问题，问题描述：一个用户在登录成功以后会把用户信息存储在session当中，这时session所在服务器为server1，那么用户在session失效之前如果再次使用app，那么可能会被路由到server2，这时问题来了，server没有该用户的session，所以需要用户重新登录，这时的用户体验会非常不好，所以我们想如何实现多台server之间共享session，让用户状态得以保存。 当然业界已经有很多成熟的解决方案，我罗列如下： 1.服务器实现的session复制或session共享，这类型的共享session是和服务器紧密相关的，比如webSphere或JBOSS在搭建集群时候可以配置实现session复制或session共享，但是这种方式有一个致命的缺点，就是不好扩展和移植，比如我们更换服务器，那么就要修改服务器配置。 2.利用成熟的技术做session复制，比如12306使用的gemfire，比如常见的内存数据库如redis或memorycache，这类方案虽然比较普适，但是严重依赖于第三方，这样当第三方服务器出现问题的时候，那么将是应用的灾难。 3.将session维护在客户端，很容易想到就是利用cookie，但是客户端存在风险，数据不安全，而且可以存放的数据量比较小，所以将session维护在客户端还要对session中的信息加密。