Re: new wiki content

[Anilkumar Gingade]

Agree with Dan, its more about troubleshooting/fixing issue.

Will it be a good idea to organize them as:

Troubleshooting:
- When system encounters OOM
- When critical heap...

When i read it as design, i was expecting, system design instruction based
on certain requirement. Just my thoughts...
E.g.: For 10GB of data store, what is the memory requirement for 3 node
system...

-Anil.







On Tue, Jun 7, 2016 at 2:17 PM, Dan Smith  wrote:

> Nice, a bunch of good information here! Maybe these pages should move under
> Application Development->Troubleshooting?
>
> I think the OOME thrown page needs some work. I don't think there is such a
> thing a system that is designed such that an OOME doesn't matter. The
> system should be designed such that it doesn't run out of memory. If you
> see a member die with an OOME, then that probably requires more action than
> just restarting the member - you need to figure out why it ran out of
> memory and try to address the problem.
>
> In the Critical Heap Exceeded page, it says this: "With operations not
> completing, the system may revoke the membership of the member that
> is above the critical-heap-percentage. " I wasn't aware that there is
> anything to kick out members with critical heap. Can you clarify under what
> conditions members will be kicked out instead of throwing a
> LowMemoryException?
>
> -Dan
>
> On Tue, Jun 7, 2016 at 1:19 PM, Karen Miller  wrote:
>
> > Feedback and suggestions welcomed on a newly added Apache Geode
> > (incubating) wiki subject at
> >   https://cwiki.apache.org/confluence/display/GEODE/Index
> > The content is under the new category of Handling User Issues and Design.
> >
> > The first subject addressed is that of heap memory space and what happens
> > when a Geode
> > member exceeds threshold values in its heap allocation.
> >
> > This content targets users designing with Geode, aiming to expand into
> > that elusive target of best practices in design.
> >
> >
> >
> >
>

[GitHub] incubator-geode pull request #151: GEODE-744: Incorrect use of APP_FETCH_SIZ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-geode/pull/151


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-geode issue #151: GEODE-744: Incorrect use of APP_FETCH_SIZE in GF...

[jinmeiliao]

Github user jinmeiliao commented on the issue:

https://github.com/apache/incubator-geode/pull/151
  
+1


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-geode issue #151: GEODE-744: Incorrect use of APP_FETCH_SIZE in GF...

[jinmeiliao]

Github user jinmeiliao commented on the issue:

https://github.com/apache/incubator-geode/pull/151
  
Not sure if this works, the example it gives are those queries
echo "query --query=\"select count(*) from /replicatedRegion.keySet\"" >> 
query_region.gfsh
echo "query --query=\"SELECT COUNT(*) FROM /replicatedRegion.keySet\"" >> 
query_region.gfsh

would count() be the same as count(*)?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Review Request 48383: fix IllegalStateException from importNewObject

[Darrel Schneider]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/48383/
---

Review request for geode, Eric Shu, Scott Jewell, Ken Howe, and Sai Boorlagadda.


Bugs: GEODE-1508
https://issues.apache.org/jira/browse/GEODE-1508


Repository: geode


Description
---

The code in EntryEventImpl that calls importNewObject
is now careful to never call importNewObject with isSerialized false
if prefersNewSerialized is true.
The same bug was fixed for importOldObject.
Unit tests have been added for the code in EntryEventImpl
that calls both importNewObject and importOldObject.


Diffs
-

  
geode-core/src/main/java/com/gemstone/gemfire/internal/cache/EntryEventImpl.java
 c4849be2c0863e6badf6eeaf1ccfaaf826d57584 
  
geode-core/src/test/java/com/gemstone/gemfire/internal/cache/EntryEventImplTest.java
 800527f2927cc775cf89426f12fc6eb6c48f77bb 

Diff: https://reviews.apache.org/r/48383/diff/


Testing
---

precheckin


Thanks,

Darrel Schneider

[GitHub] incubator-geode issue #151: GEODE-744: Incorrect use of APP_FETCH_SIZE in GF...

[jinmeiliao]

Github user jinmeiliao commented on the issue:

https://github.com/apache/incubator-geode/pull/151
  
I don't think this would fix the problem. The problem is that the following 
two queries would return different results. Your change would still make them 
do that.

query --query=\"select count(*) from /replicatedRegion.keySet\"
query --query=\"SELECT COUNT(*) FROM /replicatedRegion.keySet\"

I believe what Jens suggests is to convert the query string to 
lowercase/uppercase first and then checks for "contains" limit or count.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #333 was SUCCESSFUL (with 1407 tests). Change made by John Blum .

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #333 was successful.
---
Scheduled with changes by John Blum .
1409 tests in total.

https://build.spring.io/browse/SGF-NAG-333/




--
Code Changes
--
John Blum  (4684a57952eae7829458db72ed29e97fe8a70244):

>SGF-499 - Prevent SDG-defined Pools from being destroyed before the Regions 
>that use them.
>(cherry picked from commit 1bca49630997ed3a331428704de1931dc4c967c9)
>Signed-off-by: John Blum 



--
This message is automatically generated by Atlassian Bamboo

[GitHub] incubator-geode pull request #152: GEODE-68: GFSH SYS_HOST_NAME variable sho...

[kjduling]

Github user kjduling commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/152#discussion_r66156949
  
--- Diff: 
geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/Gfsh.java
 ---
@@ -279,7 +281,12 @@ protected Gfsh(boolean launchShell, String[] args, 
GfshConfig gfshConfig) throws
   private void initializeEnvironment() {
 env.put(ENV_SYS_USER,  System.getProperty("user.name"));
 env.put(ENV_SYS_USER_HOME, System.getProperty("user.home"));
-env.put(ENV_SYS_HOST_NAME, System.getProperty("user.name"));
+try {
+  env.put(ENV_SYS_HOST_NAME,   
InetAddress.getLocalHost().getHostName());
--- End diff --

I think we might need to back up and define exactly what is meant by 
hostname.  Are we talking about the name of the machine or the DNS value for a 
specific NIC?

For example,
If I run the 'hostname' command from the terminal, I get one name for my 
system.
If I run the java code above, I receive the same name.  This is equivalent 
to calling the C lib gethostname(3).

If I run this with the suggested call, I receive the name of my en4 
interface, or my 'default', which is not the same value.  

Which is the expected behavior?  The name of the machine or the name of the 
NIC on the default route?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: new wiki content

[Dan Smith]

Nice, a bunch of good information here! Maybe these pages should move under
Application Development->Troubleshooting?

I think the OOME thrown page needs some work. I don't think there is such a
thing a system that is designed such that an OOME doesn't matter. The
system should be designed such that it doesn't run out of memory. If you
see a member die with an OOME, then that probably requires more action than
just restarting the member - you need to figure out why it ran out of
memory and try to address the problem.

In the Critical Heap Exceeded page, it says this: "With operations not
completing, the system may revoke the membership of the member that
is above the critical-heap-percentage. " I wasn't aware that there is
anything to kick out members with critical heap. Can you clarify under what
conditions members will be kicked out instead of throwing a
LowMemoryException?

-Dan

On Tue, Jun 7, 2016 at 1:19 PM, Karen Miller  wrote:

> Feedback and suggestions welcomed on a newly added Apache Geode
> (incubating) wiki subject at
>   https://cwiki.apache.org/confluence/display/GEODE/Index
> The content is under the new category of Handling User Issues and Design.
>
> The first subject addressed is that of heap memory space and what happens
> when a Geode
> member exceeds threshold values in its heap allocation.
>
> This content targets users designing with Geode, aiming to expand into
> that elusive target of best practices in design.
>
>
>
>

Re: new wiki content

[Dave Barnes]

Good stuff, Karen. Complements the material in App Dev -> troubleshooting
without duplicating it. A nice addition to the wiki!

On Tue, Jun 7, 2016 at 1:19 PM, Karen Miller  wrote:

> Feedback and suggestions welcomed on a newly added Apache Geode
> (incubating) wiki subject at
>   https://cwiki.apache.org/confluence/display/GEODE/Index
> The content is under the new category of Handling User Issues and Design.
>
> The first subject addressed is that of heap memory space and what happens
> when a Geode
> member exceeds threshold values in its heap allocation.
>
> This content targets users designing with Geode, aiming to expand into
> that elusive target of best practices in design.
>
>
>
>

[GitHub] incubator-geode pull request #152: GEODE-68: GFSH SYS_HOST_NAME variable sho...

[bschuchardt]

Github user bschuchardt commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/152#discussion_r66147139
  
--- Diff: 
geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/Gfsh.java
 ---
@@ -279,7 +281,12 @@ protected Gfsh(boolean launchShell, String[] args, 
GfshConfig gfshConfig) throws
   private void initializeEnvironment() {
 env.put(ENV_SYS_USER,  System.getProperty("user.name"));
 env.put(ENV_SYS_USER_HOME, System.getProperty("user.home"));
-env.put(ENV_SYS_HOST_NAME, System.getProperty("user.name"));
+try {
+  env.put(ENV_SYS_HOST_NAME,   
InetAddress.getLocalHost().getHostName());
--- End diff --

Use SocketCreator.getLocalHost() and SocketCreator.getHostName().  
SocketCreator caches host names to avoid going to DNS when the host name is 
already known.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-geode pull request #152: GEODE-68: GFSH SYS_HOST_NAME variable sho...

[metatype]

Github user metatype commented on a diff in the pull request:

https://github.com/apache/incubator-geode/pull/152#discussion_r66146482
  
--- Diff: 
geode-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/Gfsh.java
 ---
@@ -279,7 +281,12 @@ protected Gfsh(boolean launchShell, String[] args, 
GfshConfig gfshConfig) throws
   private void initializeEnvironment() {
 env.put(ENV_SYS_USER,  System.getProperty("user.name"));
 env.put(ENV_SYS_USER_HOME, System.getProperty("user.home"));
-env.put(ENV_SYS_HOST_NAME, System.getProperty("user.name"));
+try {
+  env.put(ENV_SYS_HOST_NAME,   
InetAddress.getLocalHost().getHostName());
--- End diff --

@bschuchardt Do we have utility code for doing hostname lookup?  Do you see 
any problems with timeouts or DNS failures here?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

new wiki content

[Karen Miller]

Feedback and suggestions welcomed on a newly added Apache Geode
(incubating) wiki subject at
  https://cwiki.apache.org/confluence/display/GEODE/Index
The content is under the new category of Handling User Issues and Design.

The first subject addressed is that of heap memory space and what happens
when a Geode
member exceeds threshold values in its heap allocation.

This content targets users designing with Geode, aiming to expand into that
elusive target of best practices in design.

[GitHub] incubator-geode pull request #152: GEODE-68: GFSH SYS_HOST_NAME variable sho...

[kjduling]

GitHub user kjduling opened a pull request:

https://github.com/apache/incubator-geode/pull/152

GEODE-68: GFSH SYS_HOST_NAME variable should report hostname if avail…

Populate the SYS_HOST_NAME variable with the system host name if possible.  
Otherwise, set it to localhost.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kjduling/incubator-geode feature/GEODE-68

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-geode/pull/152.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #152


commit 32b75112ff51e6dda35635f82bdcf47a6afdaee8
Author: Kevin J. Duling 
Date:   2016-06-07T20:06:58Z

GEODE-68: GFSH SYS_HOST_NAME variable should report hostname if available




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-geode pull request #151: GEODE-744: Incorrect use of APP_FETCH_SIZ...

[kjduling]

GitHub user kjduling opened a pull request:

https://github.com/apache/incubator-geode/pull/151

GEODE-744: Incorrect use of APP_FETCH_SIZE in GFSH

Changed the test to be case-insensitive.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kjduling/incubator-geode feature/GEODE-744

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-geode/pull/151.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #151


commit c02dd1c1f2d176b5ce6316516278a064d8b2afaa
Author: Kevin J. Duling 
Date:   2016-06-07T19:29:19Z

GEODE-744: Incorrect use of APP_FETCH_SIZE in GFSH




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

IntelliJ code formatter - Please Read

[Bruce Schuchardt]

If you are using IntelliJ and have used the eclipseFormatterProfile.xml 
to configure the code-style of the editor please take a moment and 
switch to the intellijIdeaCodeStyle.xml profile.


The Eclipse profile does not properly configure IntelliJ's code style.  
Import-statements, for instance, are arranged completely differently if 
you use the Eclipse profile and this can cause a lot of noise in diffs 
on ReviewBoard.

Re: [REMINDER] [VIRTUAL] Geode Clubhouse next TOMORROW - Weds, June 8, 9AM PDT - Cluster Replication via WAN Gateway

[Gregory Chase]

Just a reminder that there's a Geode Clubhouse about WAN-based Replication
tomorrow, 9AM PDT.

Please join us on tomorrow, June 8th, 2016 at:
https://pivotalcommunity.adobeconnect.com/clubhouse/

On Wed, Jun 1, 2016 at 4:46 PM, Gregory Chase  wrote:

> Greetings Geode Community
>
> It's time for the next Apache Geode Clubhouse Meeting on June 8th!
>
> Each meeting starts with a user technology discussion topic, followed by a
> contributor & committer discussion of open JIRA issues, release
> coordination, and open Q&A.
>
> User Tech Talk: Cluster Replication via WAN Gateway
>
> Mike Stolz, Committer to Apache Geode, and Product Manager for GemFire
> will talk about how Geode and GemFire users make use of the WAN Gateway
> feature to enable cluster to cluster replication.
>
> For more information about this feature, see the recently posted blog 
> Active/Active
> WAN-based Replication in Apache Geode
> 
> .
>
> About the speaker: Mike leads the Product Management team for Gemfire. He 
> brings
> a long history in the Financial Services community to Pivotal.
>
> Standing agenda:
>
> -Open Jiras, and ways to contribute
> -Next release coordination
> -Open Q&A
>
> Please join us on June 8th, 2016 at:
> https://pivotalcommunity.adobeconnect.com/clubhouse/
>
> 6/8 San Francisco, CA 9:00 AM PDT UTC-8 hours
> 6/8 New York, NY 12:00 PM EDT UTC-5 hours
>
> As always, this meeting will be recorded and posted.
>
> 
> Adobe Connect tips: For issues with Chrome.  A little icon appears in the
> address bar.  It's EASY to miss. You click it and it allows Adobe to use
> the mic, even if you select 'allow' in the popup, it doesn't work until you
> change it in address bar too.
>
> Also, preload as much content as is possible to help bandwidth issues.
> 
> If you have never attended an Adobe Connect meeting before:
>
> Test your connection:
>
> https://pivotalcommunity.adobeconnect.com/common/help/en/support/meeting_test.htm
>
> Get a quick overview: http://www.adobe.com/products/adobeconnect.html
>
> --
> Greg Chase
>
> Global Head, Big Data Communities
> http://www.pivotal.io/big-data
>
> Pivotal Software
> http://www.pivotal.io/
>
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Build failed in Jenkins: Geode-nightly #492

[Apache Jenkins Server]

See 

Changes:

[jiliao] GEODE-1331: gfsh.bat on Windows is incorrect.

[boglesby] GEODE-11: Added support for lucene index profile exchange

[boglesby] GEODE-1471: GatewayEventFilter callbacks are now invoked on

[eshu] GEODE-1491: Make sure when checking if a transaction is completed from

[jchen] GEODE-1498 CI Failure:

[dschneider] GEODE-1464: remove sqlf code

--
[...truncated 990 lines...]
Download 
https://repo1.maven.org/maven2/org/apache/lucene/lucene-test-framework/6.0.0/lucene-test-framework-6.0.0.jar
Download 
https://repo1.maven.org/maven2/org/apache/lucene/lucene-codecs/6.0.0/lucene-codecs-6.0.0.jar
Download 
https://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/randomizedtesting-runner/2.3.2/randomizedtesting-runner-2.3.2.jar
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-lucene:processTestResources
:geode-lucene:testClasses
:geode-lucene:checkMissedTests
:geode-lucene:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest

com.gemstone.gemfire.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest > 
returnCorrectResultsAfterRebalance FAILED
java.lang.AssertionError: Suspicious strings were written to the log during 
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1007

[error 2016/06/07 11:34:57.154 UTC  tid=0x4c] Unable to save to 
lucene index
com.gemstone.gemfire.internal.cache.BucketNotFoundException: User bucket 
was not found for region Partitioned Region @70a434f4 [path='/region'; 
dataPolicy=PARTITION; prId=92; isDestroyed=false; isClosed=false; 
retryTimeout=360; serialNumber=7; partition 
attributes=PartitionAttributes@1366242326[redundantCopies=1;localMaxMemory=409;totalMaxMemory=2147483647;totalNumBuckets=113;partitionResolver=null;colocatedWith=null;recoveryDelay=-1;startupRecoveryDelay=0;FixedPartitionAttributes=null;partitionListeners=null];
 on VM asf904(14098):1026]key 2 callbackarg null
at 
com.gemstone.gemfire.cache.lucene.internal.PartitionedRepositoryManager.getRepository(PartitionedRepositoryManager.java:102)
at 
com.gemstone.gemfire.cache.lucene.internal.LuceneEventListener.processEvents(LuceneEventListener.java:72)
at 
com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:168)
at 
com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:87)
at 
com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:613)
at 
com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1058)

---
Found suspect string in log4j at line 1038

[error 2016/06/07 11:34:57.205 UTC  tid=0x4c] Unable to save to 
lucene index
com.gemstone.gemfire.internal.cache.BucketNotFoundException: User bucket 
was not found for region Partitioned Region @70a434f4 [path='/region'; 
dataPolicy=PARTITION; prId=92; isDestroyed=false; isClosed=false; 
retryTimeout=360; serialNumber=7; partition 
attributes=PartitionAttributes@1366242326[redundantCopies=1;localMaxMemory=409;totalMaxMemory=2147483647;totalNumBuckets=113;partitionResolver=null;colocatedWith=null;recoveryDelay=-1;startupRecoveryDelay=0;FixedPartitionAttributes=null;partitionListeners=null];
 on VM asf904(14098):1026]key 2 callbackarg null
at 
com.gemstone.gemfire.cache.lucene.internal.PartitionedRepositoryManager.getRepository(PartitionedRepositoryManager.java:102)
at 
com.gemstone.gemfire.cache.lucene.internal.LuceneEventListener.processEvents(LuceneEventListener.java:72)
at 
com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:168)
at 
com.gemstone.gemfire.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:87)
at 
com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:613)
at 
com.gemstone.gemfire.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1058)

---
Found suspect string in log4j at line 1047

[error 2016/06/07 11:34:57.256 UTC  tid=0x4c] Unable to save to 
lucene ind