incubator-geode git commit: GEODE-1986: correctly set the flag indicating if cluster configuration service is running or not on a locator.

[jinmeiliao]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop f079f3709 -> 584337b32


GEODE-1986: correctly set the flag indicating if cluster configuration service 
is running or not on a locator.


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/584337b3
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/584337b3
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/584337b3

Branch: refs/heads/develop
Commit: 584337b323b3713ec95dbb8934862dc83a65757f
Parents: f079f37
Author: Jinmei Liao 
Authored: Tue Oct 11 14:01:33 2016 -0700
Committer: Jinmei Liao 
Committed: Wed Oct 12 09:40:26 2016 -0700

--
 .../internal/InternalDistributedSystem.java | 68 +++-
 .../geode/internal/cache/GemFireCacheImpl.java  |  6 +-
 ...lusterConfigWithEmbededLocatorDUnitTest.java | 67 +++
 3 files changed, 107 insertions(+), 34 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/584337b3/geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
--
diff --git 
a/geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
 
b/geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
index 17303c1..848a86e 100644
--- 
a/geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
+++ 
b/geode-core/src/main/java/org/apache/geode/distributed/internal/InternalDistributedSystem.java
@@ -98,15 +98,13 @@ import org.apache.geode.internal.offheap.MemoryAllocator;
 import org.apache.geode.internal.offheap.OffHeapStorage;
 import org.apache.geode.internal.statistics.DummyStatisticsImpl;
 import org.apache.geode.internal.statistics.GemFireStatSampler;
-import org.apache.geode.internal.statistics.platform.LinuxProcFsStatistics;
 import org.apache.geode.internal.statistics.LocalStatisticsImpl;
-import org.apache.geode.internal.statistics.platform.OsStatisticsFactory;
 import org.apache.geode.internal.statistics.StatisticsImpl;
 import org.apache.geode.internal.statistics.StatisticsManager;
 import org.apache.geode.internal.statistics.StatisticsTypeFactoryImpl;
+import org.apache.geode.internal.statistics.platform.LinuxProcFsStatistics;
+import org.apache.geode.internal.statistics.platform.OsStatisticsFactory;
 import org.apache.geode.internal.tcp.ConnectionTable;
-import org.apache.geode.internal.util.concurrent.StoppableCondition;
-import org.apache.geode.internal.util.concurrent.StoppableReentrantLock;
 import org.apache.geode.management.ManagementException;
 import org.apache.geode.security.GemFireSecurityException;
 
@@ -733,39 +731,45 @@ public class InternalDistributedSystem extends 
DistributedSystem implements OsSt
*/
   private void startInitLocator() throws InterruptedException {
 String locatorString = this.originalConfig.getStartLocator();
-if (locatorString.length() > 0) {
-  // when reconnecting we don't want to join with a colocated locator 
unless
-  // there is a quorum of the old members available
-  if (attemptingToReconnect && !this.isConnected) {
-if (this.quorumChecker != null) {
-  logger.info("performing a quorum check to see if location services 
can be started early");
-  if (!quorumChecker.checkForQuorum(3 * 
this.config.getMemberTimeout())) {
-logger.info("quorum check failed - not allowing location services 
to start early");
-return;
-  }
-  logger.info("Quorum check passed - allowing location services to 
start early");
+if (locatorString.length()==0) {
+  return;
+}
+
+// when reconnecting we don't want to join with a colocated locator unless
+// there is a quorum of the old members available
+if (attemptingToReconnect && !this.isConnected) {
+  if (this.quorumChecker != null) {
+logger.info("performing a quorum check to see if location services can 
be started early");
+if (!quorumChecker.checkForQuorum(3 * this.config.getMemberTimeout())) 
{
+  logger.info("quorum check failed - not allowing location services to 
start early");
+  return;
 }
+logger.info("Quorum check passed - allowing location services to start 
early");
   }
-  DistributionLocatorId locId = new DistributionLocatorId(locatorString);
-  try {
-this.startedLocator = InternalLocator.createLocator(locId.getPort(), 
null, null, this.logWriter, // LOG: this is after IDS has created 
LogWriterLoggers and Appenders
-  this.securityLogWriter, // LOG: this is after IDS has created 
LogWriterLoggers and Appenders
-  locId.getHost(), locId.g

incubator-geode git commit: GEODE-1979: refactor SecurityClusterConfig to remove the flakiness.

[jinmeiliao]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop 584337b32 -> e15657e9d


GEODE-1979: refactor SecurityClusterConfig to remove the flakiness.

* add more test cases to cover more scenarios


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/e15657e9
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/e15657e9
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/e15657e9

Branch: refs/heads/develop
Commit: e15657e9de8bffdc8fa25249fcee86c46ce79928
Parents: 584337b
Author: Jinmei Liao 
Authored: Tue Oct 11 09:43:33 2016 -0700
Committer: Jinmei Liao 
Committed: Wed Oct 12 09:42:04 2016 -0700

--
 .../ClusterConfigWithoutSecurityDUnitTest.java  | 102 ++
 .../SecurityClusterConfigDUnitTest.java | 107 +--
 .../SecurityWithoutClusterConfigDUnitTest.java  |  92 
 .../security/StartServerAuthorizationTest.java  |  73 +
 .../rules/LocatorServerConfigurationRule.java   |  79 +++---
 .../LuceneClusterConfigurationDUnitTest.java|  24 +
 6 files changed, 223 insertions(+), 254 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e15657e9/geode-core/src/test/java/org/apache/geode/security/ClusterConfigWithoutSecurityDUnitTest.java
--
diff --git 
a/geode-core/src/test/java/org/apache/geode/security/ClusterConfigWithoutSecurityDUnitTest.java
 
b/geode-core/src/test/java/org/apache/geode/security/ClusterConfigWithoutSecurityDUnitTest.java
new file mode 100644
index 000..3854bb1
--- /dev/null
+++ 
b/geode-core/src/test/java/org/apache/geode/security/ClusterConfigWithoutSecurityDUnitTest.java
@@ -0,0 +1,102 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.geode.security;
+
+import static org.apache.geode.distributed.ConfigurationProperties.*;
+import static org.assertj.core.api.Java6Assertions.*;
+import static org.junit.Assert.*;
+
+import java.util.Properties;
+
+import org.junit.After;
+import org.junit.Before;
+import org.junit.Rule;
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.GemFireConfigException;
+import org.apache.geode.cache.CacheFactory;
+import org.apache.geode.distributed.internal.InternalDistributedSystem;
+import org.apache.geode.internal.i18n.LocalizedStrings;
+import org.apache.geode.security.templates.SimpleSecurityManager;
+import org.apache.geode.test.dunit.IgnoredException;
+import org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase;
+import org.apache.geode.test.dunit.rules.LocatorServerConfigurationRule;
+import org.apache.geode.test.junit.categories.DistributedTest;
+import org.apache.geode.test.junit.categories.SecurityTest;
+
+@Category({ DistributedTest.class, SecurityTest.class })
+
+public class ClusterConfigWithoutSecurityDUnitTest extends 
JUnit4DistributedTestCase {
+
+  @Rule
+  public LocatorServerConfigurationRule lsRule = new 
LocatorServerConfigurationRule(this);
+
+  @Before
+  public void before() throws Exception {
+
IgnoredException.addIgnoredException(LocalizedStrings.GEMFIRE_CACHE_SECURITY_MISCONFIGURATION.toString());
+
IgnoredException.addIgnoredException(LocalizedStrings.GEMFIRE_CACHE_SECURITY_MISCONFIGURATION_2.toString());
+lsRule.getLocatorVM(new Properties());
+  }
+
+  @After
+  public void after() {
+IgnoredException.removeAllExpectedExceptions();
+  }
+
+  // when locator is not secured, a secured server should be allowed to start 
with its own security manager
+  // if use-cluster-config is false
+  @Test
+  public void 
serverShouldBeAllowedToStartWithSecurityIfNotUsingClusterConfig() throws 
Exception {
+Properties props = new Properties();
+props.setProperty(SECURITY_MANAGER, SimpleSecurityManager.class.getName());
+props.setProperty(SECURITY_POST_PROCESSOR, 
PDXPostProcessor.class.getName());
+
+props.setProperty("use-cluster-configuration", "false

[incubator-geode] Git Push Summary

[kmiller]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEODE-1952-2 [created] e15657e9d

[6/6] incubator-geode git commit: GEODE-1532: Fix Pulse Clickjacking vuln.

[jinmeiliao]

GEODE-1532: Fix Pulse Clickjacking vuln.

* Removed firefox driver dependency
* This closes #256


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/a78fa753
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/a78fa753
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/a78fa753

Branch: refs/heads/develop
Commit: a78fa7537dfd656521649d57245ecd7fa05b2d31
Parents: 6054e00
Author: Jared Stewart 
Authored: Mon Oct 10 18:48:01 2016 -0700
Committer: Jinmei Liao 
Committed: Wed Oct 12 09:52:40 2016 -0700

--
 geode-pulse/build.gradle |  1 -
 geode-pulse/src/main/webapp/WEB-INF/spring-security.xml  |  5 +
 .../geode/tools/pulse/testbed/driver/PulseUITest.java| 11 +--
 3 files changed, 14 insertions(+), 3 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/a78fa753/geode-pulse/build.gradle
--
diff --git a/geode-pulse/build.gradle b/geode-pulse/build.gradle
index ef29ab3..3d19dea 100755
--- a/geode-pulse/build.gradle
+++ b/geode-pulse/build.gradle
@@ -73,7 +73,6 @@ dependencies {
   exclude module: 'selenium-java' //by artifact name
   }
 
-  testCompile 'org.seleniumhq.selenium:selenium-firefox-driver:' + 
project.'selenium.version'
   testCompile 'org.seleniumhq.selenium:selenium-api:' + 
project.'selenium.version'
   testCompile 'org.seleniumhq.selenium:selenium-remote-driver:' + 
project.'selenium.version'
   testCompile 'org.seleniumhq.selenium:selenium-support:' + 
project.'selenium.version'

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/a78fa753/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml
--
diff --git a/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml 
b/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml
index b4fccf0..2842f64 100644
--- a/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml
+++ b/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml
@@ -47,6 +47,11 @@

+   
+   
+   
+   
+   




http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/a78fa753/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
--
diff --git 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
index ced298b..5a02edc 100644
--- 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
+++ 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
@@ -31,7 +31,8 @@ import org.junit.experimental.categories.Category;
 import org.openqa.selenium.By;
 import org.openqa.selenium.WebDriver;
 import org.openqa.selenium.WebElement;
-import org.openqa.selenium.firefox.FirefoxDriver;
+import org.openqa.selenium.phantomjs.PhantomJSDriver;
+import org.openqa.selenium.remote.DesiredCapabilities;
 import org.openqa.selenium.support.ui.ExpectedCondition;
 import org.openqa.selenium.support.ui.WebDriverWait;
 
@@ -77,7 +78,13 @@ public class PulseUITest {
 
 pulseURL = "http://"; + host + ":" + port + context;
 Thread.sleep(1000); //wait till tomcat settles down
-driver = new FirefoxDriver();
+
+DesiredCapabilities capabilities = new DesiredCapabilities();
+capabilities.setJavascriptEnabled(true);
+capabilities.setCapability("takesScreenshot", true);
+capabilities.setCapability("phantomjs.page.settings.userAgent", 
"Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:16.0) Gecko/20121026 
Firefox/16.0");
+
+driver = new PhantomJSDriver(capabilities);
 driver.manage().window().maximize();//required to make all elements visible
 
 Thread.sleep(5000); //wait till pulse starts polling threads...

[3/6] incubator-geode git commit: GEODE-999: Converted from Firefox driver to PhantomJS driver to run UITests in headless mode

[jinmeiliao]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/dfb87a59/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/PulseAutomatedTest.java
--
diff --git 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/PulseAutomatedTest.java
 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/PulseAutomatedTest.java
deleted file mode 100644
index 778acf9..000
--- 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/PulseAutomatedTest.java
+++ /dev/null
@@ -1,784 +0,0 @@
-/*
- *
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements.  See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License.  You may obtain a copy of the License at
- *
- *  http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- *
- */
-/**
-* This test class contains automated tests for Pulse application related to
-* 1. Different grid data validations for example - Topology, Server Group, 
Redundancy Zone
-* 2. Data Browser
-* 3. 
-* 
-*
-* @version 1.0
-* @since GemFire   2014-04-02
-*/
-package org.apache.geode.tools.pulse.tests;
-
-import static org.junit.Assert.*;
-
-import java.text.DateFormat;
-import java.text.SimpleDateFormat;
-import java.util.List;
-
-import org.junit.BeforeClass;
-import org.junit.Ignore;
-import org.junit.Test;
-import org.junit.experimental.categories.Category;
-import org.openqa.selenium.By;
-import org.openqa.selenium.WebElement;
-
-import org.apache.geode.test.junit.categories.UITest;
-
-@Category(UITest.class)
-public class PulseAutomatedTest extends PulseAbstractTest {
-
-   @BeforeClass
-   public static void beforeClassSetup() throws Exception {
-   setUpServer("pulseUser", "12345", "pulse-auth.json");
-   }
-
-   @Test
-   public void serverGroupGridDataValidation() {
-   navigateToServerGroupGridView();
-   validateServerGroupGridData();
-   }
-
-   @Test
-   public void redundancyZonesGridDataValidation() {
-   navigateToRedundancyZonesGridView();
-   validateRedundancyZonesGridData();
-   }
-
-   @Test
-   public void topologyGridDataValidation() {
-   navigateToTopologyGridView();
-   validateTopologyGridData();
-   }
-
-   @Test
-   public void dataViewGridDataValidation() {
-   navigateToDataPrespectiveGridView();
-   validateDataPrespectiveGridData();
-   }
-
-   @Test
-   public void regionDetailsGridDataValidation() {
-   navigateToRegionDetailsGridView();
-   validateRegionDetailsGridData();
-
-   }
-
-   @Test
-   public void regionDetailsNavigationTest() {
-   navigateToRegionDetailsView();
-   assertEquals("/R2", 
getTextUsingId(PulseTestLocators.RegionDetailsView.regionNameDivId));
-   }
-
-   @Test
-   public void regionName() {
-   navigateToRegionDetailsView();
-   assertEquals(getPropertyValue("region.R2.name"), 
getTextUsingId(PulseTestLocators.RegionDetailsView.regionNameDivId));
-   }
-
-   @Test
-   public void regionPath() {
-   navigateToRegionDetailsView();
-   assertEquals(getPropertyValue("region.R2.fullPath"),
-   
getTextUsingId(PulseTestLocators.RegionDetailsView.regionPathId));
-   }
-
-   @Test
-   public void regionType() {
-   navigateToRegionDetailsView();
-   assertEquals(getPropertyValue("region.R2.regionType"),
-   
getTextUsingId(PulseTestLocators.RegionDetailsView.regionTypeId));
-   }
-
-   @Test
-   public void regionMembers() {
-   navigateToRegionDetailsView();
-   assertEquals(getPropertyValue("region.R2.memberCount"),
-   
getTextUsingId(PulseTestLocators.RegionDetailsView.regionMembersTextId));
-   }
-
-   @Test
-   public void regionEmptyNodes() {
-   navigateToRegionDetailsView();
-   assertEquals(getPropertyValue("region.R2.emptyNodes"),
-   
getTextUsingId(PulseTestLocators.RegionDetailsView.regionEmptyNodesId));
-   }
-
-   @Test
-   public void regionEntryCount() {
-   navigateToRegionDetailsView();
-   
asse

[5/6] incubator-geode git commit: GEODE-1966: Unauthorized users cannot access pulseVersion details

[jinmeiliao]

GEODE-1966: Unauthorized users cannot access pulseVersion details


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/6054e004
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/6054e004
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/6054e004

Branch: refs/heads/develop
Commit: 6054e00431b1e3a0826b1e6937c867da3fb6e6ce
Parents: dfb87a5
Author: Jared Stewart 
Authored: Mon Oct 10 16:59:07 2016 -0700
Committer: Jinmei Liao 
Committed: Wed Oct 12 09:47:10 2016 -0700

--
 .../src/main/webapp/WEB-INF/spring-security.xml |   1 -
 .../tools/pulse/tests/ui/PulseAbstractTest.java |  11 +-
 .../pulse/tests/ui/PulseAnonymousUserTest.java  | 149 +++
 3 files changed, 158 insertions(+), 3 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6054e004/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml
--
diff --git a/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml 
b/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml
index 7efc356..b4fccf0 100644
--- a/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml
+++ b/geode-pulse/src/main/webapp/WEB-INF/spring-security.xml
@@ -28,7 +28,6 @@



-   




http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6054e004/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
--
diff --git 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
index 709a831..ad8f67b 100644
--- 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
+++ 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
@@ -198,7 +198,7 @@ public abstract class PulseAbstractTest extends 
PulseBaseTest {
 passwordElement.sendKeys(password);
 passwordElement.submit();
 
-Thread.sleep(3000);
+driver.get(pulseURL + "/clusterDetail.html");
 WebElement userNameOnPulsePage = (new WebDriverWait(driver, 10)).until(new 
ExpectedCondition() {
   @Override
   public WebElement apply(WebDriver d) {
@@ -207,7 +207,6 @@ public abstract class PulseAbstractTest extends 
PulseBaseTest {
 });
 assertNotNull(userNameOnPulsePage);
 driver.navigate().refresh();
-Thread.sleep(7000);
   }
 
   private static void setUpWebDriver() {
@@ -229,6 +228,7 @@ public abstract class PulseAbstractTest extends 
PulseBaseTest {
 
   @Before
   public void setup() throws Exception {
+driver.get(pulseURL + "/clusterDetail.html");
 // Make sure we go to the home page first
 
searchByXPathAndClick(PulseTestLocators.TopNavigation.clusterViewLinkXpath);
   }
@@ -975,4 +975,11 @@ public abstract class PulseAbstractTest extends 
PulseBaseTest {
 // Assert data regions are displayed
 assertTrue(driver.findElement(By.id("treeDemo_1")).isDisplayed());
   }
+
+  @Test
+  public void userCannotGetToPulseDetails() {
+driver.get(pulseURL + "/pulse/pulseVersion");
+
+assertTrue(driver.getPageSource().contains("sourceRevision"));
+  }
 }

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6054e004/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAnonymousUserTest.java
--
diff --git 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAnonymousUserTest.java
 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAnonymousUserTest.java
new file mode 100644
index 000..1cf4ad4
--- /dev/null
+++ 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAnonymousUserTest.java
@@ -0,0 +1,149 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations un

[2/6] incubator-geode git commit: GEODE-999: Converted from Firefox driver to PhantomJS driver to run UITests in headless mode

[jinmeiliao]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/dfb87a59/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
--
diff --git 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
new file mode 100644
index 000..709a831
--- /dev/null
+++ 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseAbstractTest.java
@@ -0,0 +1,978 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+package org.apache.geode.tools.pulse.tests.ui;
+
+import static org.junit.Assert.*;
+
+import java.io.BufferedReader;
+import java.io.File;
+import java.io.FileReader;
+import java.io.IOException;
+import java.io.InputStream;
+import java.text.DecimalFormat;
+import java.util.List;
+import java.util.Properties;
+import java.util.concurrent.TimeUnit;
+
+import com.jayway.awaitility.Awaitility;
+import org.apache.commons.io.FileUtils;
+import org.junit.AfterClass;
+import org.junit.Before;
+import org.junit.Ignore;
+import org.junit.Rule;
+import org.junit.Test;
+import org.junit.rules.TestRule;
+import org.junit.rules.TestWatcher;
+import org.junit.runner.Description;
+import org.openqa.selenium.By;
+import org.openqa.selenium.JavascriptExecutor;
+import org.openqa.selenium.OutputType;
+import org.openqa.selenium.TakesScreenshot;
+import org.openqa.selenium.WebDriver;
+import org.openqa.selenium.WebElement;
+import org.openqa.selenium.interactions.Actions;
+import org.openqa.selenium.phantomjs.PhantomJSDriver;
+import org.openqa.selenium.remote.DesiredCapabilities;
+import org.openqa.selenium.support.ui.ExpectedCondition;
+import org.openqa.selenium.support.ui.ExpectedConditions;
+import org.openqa.selenium.support.ui.WebDriverWait;
+
+import org.apache.geode.internal.admin.SSLConfig;
+import org.apache.geode.management.internal.JettyHelper;
+import org.apache.geode.test.junit.rules.RetryRule;
+import org.apache.geode.tools.pulse.internal.data.PulseConstants;
+import org.apache.geode.tools.pulse.tests.JMXProperties;
+import org.apache.geode.tools.pulse.tests.PulseTestLocators;
+import org.apache.geode.tools.pulse.tests.Server;
+
+@SuppressWarnings("deprecated")
+public abstract class PulseAbstractTest extends PulseBaseTest {
+
+  private static String jmxPropertiesFile;
+  private static String path;
+
+  private static org.eclipse.jetty.server.Server jetty = null;
+  private static Server server = null;
+  private static String pulseURL = null;
+  public static WebDriver driver;
+
+  /* Constants for executing Data Browser queries */
+  public static final String QUERY_TYPE_ONE = "query1";
+  public static final String QUERY_TYPE_TWO = "query2";
+  public static final String QUERY_TYPE_THREE = "query3";
+  public static final String QUERY_TYPE_FOUR = "query4";
+  public static final String QUERY_TYPE_FIVE = "query5";
+  public static final String QUERY_TYPE_SIX = "query6";
+  public static final String QUERY_TYPE_SEVENE = "query7";
+
+  private static final String DATA_VIEW_LABEL = "Data View";
+  private static final String CLUSTER_VIEW_MEMBERS_ID = 
"clusterTotalMembersText";
+  private static final String CLUSTER_VIEW_SERVERS_ID = "clusterServersText";
+  private static final String CLUSTER_VIEW_LOCATORS_ID = "clusterLocatorsText";
+  private static final String CLUSTER_VIEW_REGIONS_ID = 
"clusterTotalRegionsText";
+  private static final String CLUSTER_CLIENTS_ID = "clusterClientsText";
+  private static final String CLUSTER_FUNCTIONS_ID = "clusterFunctions";
+  private static final String CLUSTER_UNIQUECQS_ID = "clusterUniqueCQs";
+  private static final String CLUSTER_SUBSCRIPTION_ID = 
"clusterSubscriptionsText";
+  private static final String CLUSTER_MEMORY_USAGE_ID = "currentMemoryUsage";
+  private static final String CLUSTER_THROUGHPUT_WRITES_ID = 
"currentThroughputWrites";
+  private static final String CLUSTER_GCPAUSES_ID = "currentGCPauses";
+  private static final String CLUSTER_WRITEPERSEC_ID = "writePerSec";
+  private static final String CLUSTER_READPERSEC_ID = "readPerSec";
+  private static final Str

[4/6] incubator-geode git commit: GEODE-999: Converted from Firefox driver to PhantomJS driver to run UITests in headless mode

[jinmeiliao]

GEODE-999: Converted from Firefox driver to PhantomJS driver to run UITests in 
headless mode

* Moved pulse ui tests into their own package.


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/dfb87a59
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/dfb87a59
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/dfb87a59

Branch: refs/heads/develop
Commit: dfb87a591ef33e1a0f4e4b5299c21685cef2f25e
Parents: e15657e
Author: Jared Stewart 
Authored: Mon Oct 3 14:15:59 2016 -0700
Committer: Jinmei Liao 
Committed: Wed Oct 12 09:46:53 2016 -0700

--
 .gitignore  |3 +
 .../test/gemfire-jstewartgeode999-files.tgz |  Bin 0 -> 877528 bytes
 geode-pulse/build.gradle|5 +
 .../tools/pulse/testbed/driver/PulseUITest.java |2 +-
 .../pulse/tests/DataBrowserResultLoader.java|2 +
 .../tools/pulse/tests/PulseAbstractTest.java| 1048 --
 .../geode/tools/pulse/tests/PulseAuthTest.java  |   33 -
 .../tools/pulse/tests/PulseAutomatedTest.java   |  784 -
 .../geode/tools/pulse/tests/PulseBaseTest.java  |  693 
 .../tools/pulse/tests/PulseNoAuthTest.java  |   33 -
 .../tools/pulse/tests/ui/PulseAbstractTest.java |  978 
 .../tools/pulse/tests/ui/PulseAuthTest.java |   34 +
 .../pulse/tests/ui/PulseAutomatedTest.java  |  768 +
 .../tools/pulse/tests/ui/PulseBaseTest.java |  697 
 .../tools/pulse/tests/ui/PulseNoAuthTest.java   |   34 +
 gradle/dependency-versions.properties   |1 +
 16 files changed, 2523 insertions(+), 2592 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/dfb87a59/.gitignore
--
diff --git a/.gitignore b/.gitignore
index 825e379..38c8131 100644
--- a/.gitignore
+++ b/.gitignore
@@ -13,6 +13,8 @@ build/
 build-eclipse/
 /tags
 
+
+
 *.iml
 *.ipr
 *.iws
@@ -25,3 +27,4 @@ build-eclipse/
 *.orig
 geode-spark-connector/**/target/
 geode-spark-connector/project/project/
+geode-pulse/screenshots/
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/dfb87a59/artifacts-jstewartgeode999/test/gemfire-jstewartgeode999-files.tgz
--
diff --git a/artifacts-jstewartgeode999/test/gemfire-jstewartgeode999-files.tgz 
b/artifacts-jstewartgeode999/test/gemfire-jstewartgeode999-files.tgz
new file mode 100644
index 000..a15d245
Binary files /dev/null and 
b/artifacts-jstewartgeode999/test/gemfire-jstewartgeode999-files.tgz differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/dfb87a59/geode-pulse/build.gradle
--
diff --git a/geode-pulse/build.gradle b/geode-pulse/build.gradle
index c58da78..ef29ab3 100755
--- a/geode-pulse/build.gradle
+++ b/geode-pulse/build.gradle
@@ -68,6 +68,11 @@ dependencies {
   testCompile project(':geode-core')
   testCompile files(project(':geode-core').sourceSets.test.output)
 
+  testCompile(group: 'com.codeborne', name: 'phantomjsdriver', version: 
project.'phantomjsdriver.version') {
+  exclude module: 'selenium-remote-driver' //by artifact name
+  exclude module: 'selenium-java' //by artifact name
+  }
+
   testCompile 'org.seleniumhq.selenium:selenium-firefox-driver:' + 
project.'selenium.version'
   testCompile 'org.seleniumhq.selenium:selenium-api:' + 
project.'selenium.version'
   testCompile 'org.seleniumhq.selenium:selenium-remote-driver:' + 
project.'selenium.version'

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/dfb87a59/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
--
diff --git 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
index a4062e5..ced298b 100644
--- 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
+++ 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/testbed/driver/PulseUITest.java
@@ -16,7 +16,7 @@
  */
 package org.apache.geode.tools.pulse.testbed.driver;
 
-import static org.apache.geode.tools.pulse.tests.PulseAbstractTest.*;
+import static org.apache.geode.tools.pulse.tests.ui.PulseAbstractTest.*;
 import static org.junit.Assert.*;
 
 import java.net.InetAddress;

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/dfb87a59/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/DataBrowserResultLoader.java
--

[1/6] incubator-geode git commit: GEODE-999: Converted from Firefox driver to PhantomJS driver to run UITests in headless mode

[jinmeiliao]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop e15657e9d -> a78fa7537


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/dfb87a59/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseBaseTest.java
--
diff --git 
a/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseBaseTest.java
 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseBaseTest.java
new file mode 100644
index 000..8cfac53
--- /dev/null
+++ 
b/geode-pulse/src/test/java/org/apache/geode/tools/pulse/tests/ui/PulseBaseTest.java
@@ -0,0 +1,697 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+package org.apache.geode.tools.pulse.tests.ui;
+
+import static org.junit.Assert.*;
+
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.TreeMap;
+import java.util.concurrent.TimeUnit;
+
+import org.openqa.selenium.By;
+import org.openqa.selenium.WebElement;
+import org.openqa.selenium.interactions.Actions;
+import org.openqa.selenium.support.ui.ExpectedConditions;
+import org.openqa.selenium.support.ui.WebDriverWait;
+
+import org.apache.geode.tools.pulse.tests.JMXProperties;
+import org.apache.geode.tools.pulse.tests.Member;
+import org.apache.geode.tools.pulse.tests.PulseTestData;
+import org.apache.geode.tools.pulse.tests.PulseTestLocators;
+import org.apache.geode.tools.pulse.tests.Region;
+
+public class PulseBaseTest {
+
+  public static int maxWaitTime = 20;
+
+  WebElement element = null;
+
+   public WebElement findElementUsingId(String id) {
+   return PulseAbstractTest.driver.findElement(By.id(id));
+   }
+   public WebElement findElementUsingXpath(String xpath) {
+   return PulseAbstractTest.driver.findElement(By.xpath(xpath));
+   }
+
+   public void clickElementUsingId(String id) {
+   findElementUsingId(id).click();
+   }
+
+   public void clickElementUsingXpath(String xpath) {
+   findElementUsingXpath(xpath).click();
+   }
+
+   public void enterTextUsingId(String id, String textToEnter) {
+   findElementUsingId(id).sendKeys(textToEnter);
+
+   }
+
+   public void enterTextUsingXpath(String xpath, String textToEnter) {
+   findElementUsingXpath(xpath).sendKeys(textToEnter);
+   }
+
+   public String getValueFromPropertiesFile(String key) {
+   return JMXProperties.getInstance().getProperty(key);
+   }
+
+   public void sendKeysUsingId(String Id, String textToEnter){
+   findElementById(Id).sendKeys(textToEnter);
+   }
+
+   public void waitForElement(WebElement element) {
+   PulseAbstractTest.driver.manage().timeouts().implicitlyWait(0, 
TimeUnit.SECONDS);
+   WebDriverWait wait = new 
WebDriverWait(PulseAbstractTest.driver, 20);
+   wait.until(ExpectedConditions.visibilityOf(element));
+   }
+
+   public WebElement findElementById(String id) {
+   return PulseAbstractTest.driver.findElement(By.id(id));
+   }
+
+   public WebElement findElementByXpath(String xpath) {
+   return PulseAbstractTest.driver.findElement(By.xpath(xpath));
+   }
+
+   public String getTextUsingXpath(String xpath) {
+   return findElementByXpath(xpath).getText();
+   }
+
+   public String getTextUsingId(String id) {
+   return findElementById(id).getText();
+   }
+
+   public String getPersistanceEnabled(Region r) {
+   String persitance = null;
+
+   if (r.getPersistentEnabled()) {
+   persitance = "ON";
+   } else if (!r.getPersistentEnabled()) {
+   persitance = "OFF";
+   }
+   return persitance;
+   }
+
+   public String getPersistanceEnabled(String trueOrFalse) {
+   String persitance = null;
+
+   if (trueOrFalse.contains("true")) {
+   persitance = "ON";
+   } else if (trueOrFalse.contains("false")) {
+   persit

[12/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_2.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_2.svg 
b/geode-docs/images_svg/transactions_replicate_2.svg
new file mode 100644
index 000..dbf8732
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="54 149 589 337" 
width="589pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:55Zreplicate-2Layer 1Member (M1)CacheReplicate Region 
AWMember 
(M2)Replicate Region 
BXRegion AW1Region 
BX1Transaction T1CacheReplicate Region AWMember 
(M3)CacheReplicate Region 
BXJava ApplicationReplicate Region 
BX2Transaction T2Java ApplicationT1

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_3.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_3.svg 
b/geode-docs/images_svg/transactions_replicate_3.svg
new file mode 100644
index 000..ba6432f
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_3.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="56 151 581 328" 
width="581pt" height="328pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.4.1 2016-01-05 23:10:13 +replicate-3Layer 1Member (M1)CacheReplicate Region 
AJava ApplicationWMember 
(M2)Replicate Region BXRegion AW1Region BX1Transaction T1CacheReplicate Region 
AWMember 
(M3)CacheReplicate Region 
BXJava Applicati
 onW1X1

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_4.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_4.svg 
b/geode-docs/images_svg/transactions_replicate_4.svg
new file mode 100644
index 000..a8c9488
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_4.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="145 175 594 337" 
width="594pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:58Zreplicate-4Layer 1Member (M1)CacheReplicate Region AJava ApplicationW1Member (M2)Replicate Region 
BX1CacheReplicate Region 
AW1Member (M3)CacheReplicate Region 
BX1Java Application

[01/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEODE-1952-2 e15657e9d -> 40c1ed590


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/nativeclient/client-cache/region-attributes-desc.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/client-cache/region-attributes-desc.html.md.erb 
b/geode-docs/nativeclient/client-cache/region-attributes-desc.html.md.erb
new file mode 100644
index 000..f667d30
--- /dev/null
+++ b/geode-docs/nativeclient/client-cache/region-attributes-desc.html.md.erb
@@ -0,0 +1,39 @@
+---
+title:  Mutable and Immutable Region Attributes
+---
+
+Attributes that are immutable (fixed) after region creation govern storage 
location, data distribution, statistics, application plug-ins, and the 
configuration and management of the region's data hashmap.
+
+This table lists the immutable attributes and their default settings.
+
+
+
+| Immutable Region Attribute   
 | Default Setting |
+|---|-|
+| See [CachingEnabled](caching-enabled.html#caching-enabled)   
 | true|
+| See [InitialCapacity](initial-capacity.html#initial-capacity)
 | 16 (entries)|
+| See [LoadFactor](load-factor.html#load-factor)   
 | 0.75|
+| See [ConcurrencyLevel](concurrency-level.html#concurrency-level) 
 | 16  |
+| See [DiskPolicy](disk-policy.html#disk-policy)   
 | |
+| See [PersistenceManager](persistence-manager.html#persistence-manager)   
 | NULL|
+| PartitionResolver. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins). | |
+
+
+Mutable region attributes identify expiration and cache listener, cache writer 
and cache loader actions that are run from the defining client. The next table 
lists the mutable attributes that generally can be modified after region 
creation by using the `AttributesMutator` for the region.
+
+
+
+| Mutable Region Attribute 
| Default Setting |
+|--|-|
+| Expiration attributes. See [Specifying Expiration 
Attributes](expiration-attributes.html#expiration-attributes). | no expiration  
 |
+| See 
[LruEntriesLimit](lru-entries-limit.html#concept_75D723D60E044FF9AE97C939699AB10A).
  | 0 (no limit)|
+| CacheLoader. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins).  |   
  |
+| CacheWriter. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins).  |   
  |
+| CacheListener. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins).| 
|
+
+
+See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins) for information about 
using `AttributesMutator` with cache listeners, cache loaders, and cache 
writers.
+
+The remainder of this section examines these attributes in detail. Throughout 
the descriptions, `cache.xml` file snippets show how each attribute can be set 
declaratively.
+
+

[05/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/monitor_tune/udp_communication.html.md.erb
--
diff --git a/geode-docs/managing/monitor_tune/udp_communication.html.md.erb 
b/geode-docs/managing/monitor_tune/udp_communication.html.md.erb
new file mode 100644
index 000..2f85709
--- /dev/null
+++ b/geode-docs/managing/monitor_tune/udp_communication.html.md.erb
@@ -0,0 +1,33 @@
+---
+title:  UDP Communication
+---
+
+You can make configuration adjustments to improve multicast and unicast UDP 
performance of peer-to-peer communication.
+
+You can tune your Geode UDP messaging to maximize throughput. There are two 
main tuning goals: to use the largest reasonable datagram packet sizes and to 
reduce retransmission rates. These actions reduce messaging overhead and 
overall traffic on your network while still getting your data where it needs to 
go. Geode also provides statistics to help you decide when to change your UDP 
messaging settings.
+
+Before you begin, you should understand Geode [Basic Configuration and 
Programming](../../basic_config/book_intro.html). See also the general 
communication tuning and multicast-specific tuning covered in [Socket 
Communication](socket_communication.html) and [Multicast 
Communication](multicast_communication.html#multicast).
+
+## UDP Datagram Size
+
+You can change the UDP datagram size with the Geode property 
udp-fragment-size. This is the maximum packet size for transmission over UDP 
unicast or multicast sockets. When possible, smaller messages are combined into 
batches up to the size of this setting.
+
+Most operating systems set a maximum transmission size of 64k for UDP 
datagrams, so this setting should be kept under 60k to allow for communication 
headers. Setting the fragment size too high can result in extra network traffic 
if your network is subject to packet loss, as more data must be resent for each 
retransmission. If many UDP retransmissions appear in DistributionStats, you 
maybe achieve better throughput by lowering the fragment size.
+
+## UDP Flow Control
+
+UDP protocols typically have a flow control protocol built into them to keep 
processes from being overrun by incoming no-ack messages. The Geode UDP flow 
control protocol is a credit based system in which the sender has a maximum 
number of bytes it can send before getting its byte credit count replenished, 
or recharged, by its receivers. While its byte credits are too low, the sender 
waits. The receivers do their best to anticipate the sender’s recharge 
requirements and provide recharges before they are needed. If the senders 
credits run too low, it explicitly requests a recharge from its receivers.
+
+This flow control protocol, which is used for all multicast and unicast no-ack 
messaging, is configured using a three-part Geode property mcast-flow-control. 
This property is composed of:
+
+-   byteAllowance—Determines how many bytes (also referred to as credits) 
can be sent before receiving a recharge from the receiving processes.
+-   rechargeThreshold—Sets a lower limit on the ratio of the sender’s 
remaining credit to its byteAllowance. When the ratio goes below this limit, 
the receiver automatically sends a recharge. This reduces recharge request 
messaging from the sender and helps keep the sender from blocking while waiting 
for recharges.
+-   rechargeBlockMs—Tells the sender how long to wait while needing a 
recharge before explicitly requesting one.
+
+In a well-tuned system, where consumers of cache events are keeping up with 
producers, the byteAllowance can be set high to limit flow-of-control messaging 
and pauses. JVM bloat or frequent message retransmissions are an indication 
that cache events from producers are overrunning consumers.
+
+## UDP Retransmission Statistics
+
+Geode stores retransmission statistics for its senders and receivers. You can 
use these statistics to help determine whether your flow control and fragment 
size settings are appropriate for your system.
+
+The retransmission rates are stored in the DistributionStats ucastRetransmits 
and mcastRetransmits. For multicast, there is also a receiver-side statistic 
mcastRetransmitRequests that can be used to see which processes aren't keeping 
up and are requesting retransmissions. There is no comparable way to tell which 
receivers are having trouble receiving unicast UDP messages.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb
--
diff --git 
a/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb 
b/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb
new file mode 100644
index 000..62a10bf
--- /dev/null
+++ b/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb
@@ -0,

[18/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/how_partitioning_works_2.svg
--
diff --git a/geode-docs/images_svg/how_partitioning_works_2.svg 
b/geode-docs/images_svg/how_partitioning_works_2.svg
new file mode 100644
index 000..6351a28
--- /dev/null
+++ b/geode-docs/images_svg/how_partitioning_works_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="68 212 385 412" 
width="385pt" height="412pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:43Zhow_it_works_2Layer 
1Partitioned Region ALogical ViewXYZPartitioned Region APh
 ysical ViewNo local 
dataMachine 1Partitioned Region 
AXMachine 
2Partitioned Region AYMachine 3Z

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/http_module_cs_with_locator.svg
--
diff --git a/geode-docs/images_svg/http_module_cs_with_locator.svg 
b/geode-docs/images_svg/http_module_cs_with_locator.svg
new file mode 100644
index 000..3b8e6a3
--- /dev/null
+++ b/geode-docs/images_svg/http_module_cs_with_locator.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="77 333 373 279" 
width="373pt" height="279pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 08:40Zcs with 
locatorLayer 1Partitioned <
 /tspan>Session 
DataPartitioned Session DataServerServerPartitioned Session Data
 Application Server 
InstanceClientapp server requestsLocal Cacheconnection 
poolLocatorprovides discovery and load balancing 
servicesPartitioned 
Session 
Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/http_module_p2p_with_locator.svg
--
diff --git a/geode-docs/images_svg/http_module_p2p_with_locator.svg 
b/geode-docs/images_svg/http_module_p2p_with_locator.svg
new file mode 100644
index 000..3c7c0b4
--- /dev/null
+++ b/geode-docs/images_svg/http_module_p2p_with_locator.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="59 348 499 191" 
width="499pt" height="191pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 08:39Zp2p with 
locatorLayer 1Application Server InstanceCacheApplication Server InstanceCacheApplication Server InstanceCacheapp server 
requestsapp server 
requestsapp server 
requestsReplicated 
Session 
DataReplicated Session DataReplicated Session DataLocatorprovides discovery and load 
balancing services

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/locator_discovery.svg
--
diff --git a/geode-docs/images_svg/locator_discovery.svg 
b/geode-docs/images_svg/locator_discovery.svg
new file mode 100644
index 000..53e9f3b
--- /dev/null
+++ b/geode-docs/images_svg/locator_discovery.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="81 317 450 160" 
width="450pt" height="160pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:26ZlocatorsLayer 1PeerPeerPeer Discovery Using 
Locators LocatorPeerLocatorCache DataCache DataCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/member_severe_alert.svg
--
diff --git a/geode-docs/images_svg/member_severe_alert.svg 
b/geode-docs/images_svg/member_severe_alert.svg
new file mode 100644
index 000..8614503
--- /dev/null
+++ b/geode-docs/images_svg/member_severe_alert.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="94 248 368 267" 
width="368pt" height="267pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 08:59Zmember severe 
alertLayer 11. CACHE_OPERATIONCache ServerReplicated RegionCache 
ServerReplicated 
RegionLocatorClientx="12.466797" y="10" textLength="25.566406">Clientx1="346.5" y1="461.25" x2="346.5" y2="421.948" 
 >marker-end="url(#FilledArrow_Marker)" stroke="#252525" stroke-linecap="round" 
 >stroke-linejoin="round" stroke-width=".7203"/>d="M 323.91 461.25 L 369.09 461.25 C 372.76822 461.25 375.75 464.23178 375.75 
 >467.91 L 375.75 490.59 C 375.75 494.26822 372.76822 497.25 36

[11/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_local_1.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_local_1.svg 
b/geode-docs/images_svg/transactions_replicate_local_1.svg
new file mode 100644
index 000..47bb4e7
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_local_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="41 158 319 301" 
width="319pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 11:04Zreplicate-localLayer 
1MemberCacheReplicate Region AJava ApplicationXT1YZRegion AX1Y1Region AY2Z2T2Transaction T1Transaction T2

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_no_ack_1.svg 
b/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
new file mode 100644
index 000..1d94d72
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="133 203 584 337" 
width="584pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 11:00Zreplicate-no-ack-1Layer 
1W1X1X2Member (M1)CacheReplicate Region AJava ApplicationWMember 
(M2)Replicate Region 
BXRegion AW1Region 
BX1Transaction T1CacheReplicate Region 
AWMember (M3)CacheReplicate Region 
BX2Replicate Region 
BXTransaction T2Java Application

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_no_ack_2.svg 
b/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
new file mode 100644
index 000..8b4d41a
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="19 148 584 337" 
width="584pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 11:02Zreplicate-no-ack-2Layer 
1Member (M1)CacheReplicate Region AJava ApplicationW1Member (M2)Replicate Region 
B
 X2CacheReplicate Region AW1Member 
(M3)CacheReplicate Region 
BX1Java Application

[03/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
--
diff --git 
a/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
 
b/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
new file mode 100644
index 000..50f97b6
--- /dev/null
+++ 
b/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
@@ -0,0 +1,75 @@
+---
+title:  Producing Artifacts for Troubleshooting
+---
+
+There are several types of files that are critical for troubleshooting.
+
+Geode logs and statistics are the two most important artifacts used in 
troubleshooting. In addition, they are required for Geode system health 
verification and performance analysis. For these reasons, logging and 
statistics should always be enabled, especially in production. Save the 
following files for troubleshooting purposes:
+
+-   Log files. Even at the default logging level, the log contains data that 
may be important. Save the whole log, not just the stack. For comparison, save 
log files from before, during, and after the problem occurred.
+-   Statistics archive files.
+-   Core files or stack traces.
+-   For Linux, you can use gdb to extract a stack from a core file.
+-   Crash dumps.
+-   For Windows, save the user mode dump files. Some locations to check for 
these files:
+-   C:\\ProgramData\\Microsoft\\Windows\\WER\\ReportArchive
+-   C:\\ProgramData\\Microsoft\\Windows\\WER\\ReportQueue
+-   
C:\\Users\\*UserProfileName*\\AppData\\Local\\Microsoft\\Windows\\WER\\ReportArchive
+-   
C:\\Users\\*UserProfileName*\\AppData\\Local\\Microsoft\\Windows\\WER\\ReportQueue
+
+When a problem arises that involves more than one process, a network problem 
is the most likely cause. When you diagnose a problem, create a log file for 
each member of all the distributed systems involved. If you are running a 
client/server architecture, create log files for the clients.
+
+**Note:**
+You must run a time synchronization service on all hosts for troubleshooting. 
Synchronized time stamps ensure that log messages on different hosts can be 
merged to accurately reproduce a chronological history of a distributed run.
+
+For each process, complete these steps:
+
+1.  Make sure the host’s clock is synchronized with the other hosts. Use a 
time synchronization tool such as Network Time Protocol (NTP).
+2.  Enable logging to a file instead of standard output by editing 
`gemfire.properties` to include this line:
+
+``` pre
+log-file=filename
+```
+
+3.  Keep the log level at `config` to avoid filling up the disk while 
including configuration information. Add this line to `gemfire.properties`:
+
+``` pre
+log-level=config
+```
+
+**Note:**
+Running with the log level at `fine` can impact system performance and 
fill up your disk.
+
+4.  Enable statistics gathering for the distributed system either by modifying 
`gemfire.properties`:
+
+``` pre
+statistic-sampling-enabled=true
+statistic-archive-file=StatisticsArchiveFile.gfs
+```
+
+or by using the `gfsh alter rutime` command:
+
+``` pre
+alter runtime --group=myMemberGroup --enable-statistics=true 
--statistic-archive-file=StatisticsArchiveFile.gfs
+```
+
+**Note:**
+Collecting statistics at the default sample rate frequency of 1000 
milliseconds does not incur performance overhead.
+
+5.  Run the application again.
+6.  Examine the log files. To get the clearest picture, merge the files. To 
find all the errors in the log file, search for lines that begin with these 
strings:
+
+``` pre
+[error
+[severe
+```
+
+For details on merging log files, see the `--merge-log` argument for the 
[export 
logs](../../tools_modules/gfsh/command-pages/export.html#topic_B80978CC659244AE91E2B8CE56EBDFE3)command.
+
+7.  Export and analyze the stack traces on the member or member group where 
the application is running. Use the `gfsh export stack-traces   
  command`. For example:
+
+``` pre
+gfsh> export stack-traces --file=ApplicationStackTrace.txt --member=member1
+```
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
--
diff --git 
a/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
 
b/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
new file mode 100644
index 000..6c65227
--- /dev/null
+++ 
b/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
@@ -0,0 +1,58 @@
+---
+title:  Recovering from ConfictingPersistentDataExceptions
+---
+
+A `Conflicting

[04/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/security/implementing_security.html.md.erb
--
diff --git a/geode-docs/managing/security/implementing_security.html.md.erb 
b/geode-docs/managing/security/implementing_security.html.md.erb
new file mode 100644
index 000..a38dd03
--- /dev/null
+++ b/geode-docs/managing/security/implementing_security.html.md.erb
@@ -0,0 +1,63 @@
+---
+title:  Security Implementation Introduction and Overview
+---
+
+## Security Features
+
+Encryption, SSL secure communication, authentication, and authorization 
+features help to secure the distributed system.
+
+Security features include:
+
+-   **A single security interface for all components**. The single
+authentication and authorization mechanism simplifies the security
+implementation.
+It views and interacts with all components in a consistent manner. 
+-   **System-wide role-based access control**.
+Roles regiment authorized operations requested by the various components.
+-   **SSL communication**. Allows configuration of connections to be 
+SSL-based, rather than plain socket connections.
+You can enable SSL separately for peer-to-peer, client, JMX, gateway senders 
and receivers, and HTTP connections.
+-   **Post processing of region data**. Return values for operations that
+return region values may be altered, permitting the filtering of returned data.
+
+## Overview
+
+An authentication and authorization mechanism forms the core of
+the internal security of the distributed system.
+Communications may be further protected by enabling SSL for
+data in transit.
+
+Authentication verifies the identity of communicating components,
+leading to control over participation.
+The variety of participants include peer members, servers,
+clients, originators of JMX operations, Pulse,
+gateway senders and receivers representing WAN members of the system,
+and commands arriving from `gfsh` on behalf of system users
+or administrators.
+
+Connection requests trigger the invocation of an authentication
+callback.
+This special-purpose callback is written as part of the application,
+and it attempts to authenticate the requester by whatever
+algorithm it chooses. 
+The result is either a returned principal representing the requester's
+authenticated identity or an exception indicating that the requester
+has not been authenticated.
+The principal becomes part of any request for operations,
+which go through the authorization process.
+
+
+Given authentication,
+isolation and access to cache data and system state can be further
+protected by implementing the authorization mechanism,
+also implemented as a special-purpose callback as part of the application.
+For example, the protection may be to permit only certain system administrators
+to start and stop servers. 
+The authority to do this needs to be limited to specific
+verified accounts, preventing those without the authorization. 
+An implementation of the authorization callback will require
+that an authenticate identity accompanies all requests to the system,
+and that the system maintains a representation of which identities
+are permitted to complete which actions or cache commands.
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/security/implementing_ssl.html.md.erb
--
diff --git a/geode-docs/managing/security/implementing_ssl.html.md.erb 
b/geode-docs/managing/security/implementing_ssl.html.md.erb
new file mode 100644
index 000..73bbf49
--- /dev/null
+++ b/geode-docs/managing/security/implementing_ssl.html.md.erb
@@ -0,0 +1,209 @@
+---
+title:  Configuring SSL
+---
+
+You can configure SSL for authentication between members and to protect your 
data during
+distribution. You can use SSL alone or in conjunction with the other Geode 
security options.
+Geode SSL connections use the Java Secure Sockets Extension (JSSE) package.
+
+## SSL-Configurable Components
+
+You can specify that SSL be used system-wide, or you can independently 
configure SSL for specific
+system components.  The following list shows the system components that can be 
separately configured
+to communicate using SSL, and the kind of communications to which each 
component name refers:
+
+**cluster**
+Peer-to-peer communications among members of a distributed system
+
+**gateway**
+Communication across WAN gateways from one site to another
+
+**web**
+All web-based services hosted on the configured server, which can include 
the Developer REST API
+service, the Management REST API service (used for remote cluster management) 
and the Pulse
+monitoring tool's web-based user interface.
+
+**jmx**
+Java management extension communications, including communications with 
the `gfsh` utility. 
+The Pulse monitoring tool uses JMX for server-side communication with a 
locator, but SSL
+app

[17/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/network_partition_scenario.svg
--
diff --git a/geode-docs/images_svg/network_partition_scenario.svg 
b/geode-docs/images_svg/network_partition_scenario.svg
new file mode 100644
index 000..89f7f48
--- /dev/null
+++ b/geode-docs/images_svg/network_partition_scenario.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="58 313 508 353" 
width="508pt" height="353pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:13Zscenario 1Layer 1Network Partition Scenario  – Total weight of 111XSurviving SideM1 (weight=3)Locator & Membership 
CoordinatorM2(weight=15)Cache Server & Lead MemberM3 (weight=10)M4 (weight=10)M6 (weight=10)Cache ServerCache ServerCache ServerM5 
(weight=10)Cache Server- Detects membership weight loss of 47%- This 
distributed system stays upM7(weight=3)LocatorLosing SideM9 (weight=10)Cache Server
 M11 (weight=10)Cache ServerM10 (weight=10)Cache ServerM12 (weight=10)Cache ServerM8 (weight=10)Cache 
Server- Detects 
membership weight loss of 52%- 
Locator assumes coordinator role and shuts system down

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/p2p_topology.svg
--
diff --git a/geode-docs/images_svg/p2p_topology.svg 
b/geode-docs/images_svg/p2p_topology.svg
new file mode 100644
index 000..208fad3
--- /dev/null
+++ b/geode-docs/images_svg/p2p_topology.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="59 293 499 121" 
width="499pt" height="121pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:03Zp2pLayer 1Application 
ProcessPeerApplication ProcessPeerApplication 
ProcessPeerCache DataCache DataCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/partitioned_data_HA.svg
--
diff --git a/geode-docs/images_svg/partitioned_data_HA.svg 
b/geode-docs/images_svg/partitioned_data_HA.svg
new file mode 100644
index 000..cbb8b5b
--- /dev/null
+++ b/geode-docs/images_svg/partitioned_data_HA.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="95 216 463 423" 
width="463pt" height="423pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 08:44ZHALayer 1stroke="#252525" stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="105.993164" y="14" textLength="84.006836">Member 
 >(M1)Partition Region 
Asecondary 
dataWXLogical 
ViewWXZYMember (M2)Partition Region Aprimary dataWXsecondary dataZYLogical ViewWXZYMember (M3)Partition Region 
Aprimary dataZYLogical ViewWXZYApplicationreadreadread

[08/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/heap_use/off_heap_management.html.md.erb
--
diff --git a/geode-docs/managing/heap_use/off_heap_management.html.md.erb 
b/geode-docs/managing/heap_use/off_heap_management.html.md.erb
new file mode 100644
index 000..0c8bf7c
--- /dev/null
+++ b/geode-docs/managing/heap_use/off_heap_management.html.md.erb
@@ -0,0 +1,192 @@
+---
+title: Managing Off-Heap Memory
+---
+
+
+
+Geode can be configured to store region values in off-heap memory, which is 
memory within the JVM that is not subject to Java garbage collection.
+
+Garbage collection (GC) within a JVM can prove to be a performance impediment. 
A server cannot exert control over when garbage collection within the JVM heap 
memory takes place, and the server has little control over the triggers for 
invocation. Off-heap memory offloads values to a storage area that is not 
subject to Java GC. By taking advantage of off-heap storage, an application can 
reduce the amount of heap storage that is subject to GC overhead.
+
+Off-heap memory works in conjunction with the heap, it does not replace it. 
The keys are stored in heap memory space. Geode's own memory manager handles 
the off-heap memory with better performance than the Java garbage collector 
would for certain sets of region data.
+
+The resource manager monitors the contents of off-heap memory and invokes 
memory management operations in accordance with two thresholds similar to those 
used for monitoring the JVM heap: `eviction-off-heap-percentage` and 
`critical-off-heap-percentage`.
+
+## On-heap and Off-heap Objects
+
+The following objects are always stored in the JVM heap:
+
+-   Region metadata
+-   Entry metadata
+-   Keys
+-   Indexes
+-   Subscription queue elements
+
+The following objects can be stored in off-heap memory:
+
+-   Values - maximum value size is 2GB
+-   Reference counts
+-   List of free memory blocks
+-   WAN queue elements
+
+**Note:**
+Do not use functional range indexes with off-heap data, as they are not 
supported. An attempt to do so generates an exception.
+
+## Off-heap Recommendations
+
+Off-heap storage is best suited to data patterns where:
+
+-   Stored values are relatively uniform in size
+-   Stored values are mostly less than 128K in size
+-   The usage patterns involve cycles of many creates followed by destroys or 
clear
+-   The values do not need to be frequently deserialized
+-   Many of the values are long-lived reference data
+
+Be aware that Geode has to perform extra work to access the data stored in 
off-heap memory since it is stored in serialized form. This extra work may 
cause some use cases to run slower in an off-heap configuration, even though 
they use less memory and avoid garbage collection overhead. However, even with 
the extra deserialization, off-heap storage may give you the best performance. 
Features that may increase overhead include
+
+-   frequent updates
+-   stored values of widely varying sizes
+-   deltas
+-   queries
+
+## Implementation Details
+
+The off-heap memory manager is efficient at handling region data values that 
are all the same size or are of fixed sizes. With fixed and same-sized data 
values allocated within the off-heap memory, freed chunks can often be re-used, 
and there is little or no need to devote cycles to defragmentation.
+
+Region values that are less than or equal to eight bytes in size will not 
reside in off-heap memory, even if the region is configured to use off-heap 
memory. These very small size region values reside in the JVM heap in place of 
a reference to an off-heap location. This performance enhancement saves space 
and load time.
+
+## Controlling Off-heap Use with the Resource Manager
+
+The Geode resource manager controls off-heap memory by means of two 
thresholds, in much the same way as it does JVM heap memory. See [Using the 
Geode Resource Manager](heap_management.html#how_the_resource_manager_works). 
The resource manager prevents the cache from consuming too much off-heap memory 
by evicting old data. If the off-heap memory manager is unable to keep up, the 
resource manager refuses additions to the cache until the off-heap memory 
manager has freed an adequate amount of memory.
+
+The resource manager has two threshold settings, each expressed as a 
percentage of the total off-heap memory. Both are disabled by default.
+
+1.  **Eviction Threshold**. The percentage of off-heap memory at which 
eviction should begin. Evictions continue until the resource manager determines 
that off-heap memory use is again below the eviction threshold. Set the 
eviction threshold with the `eviction-off-heap-percentage` region attribute. 
The resource manager enforces an eviction threshold only on regions with the 
HEAP\_LRU characteristic. If critical threshold is non-zero, the default 
eviction threshold is 5% below the critical thres

[06/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
--
diff --git 
a/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
 
b/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
new file mode 100644
index 000..b8445f2
--- /dev/null
+++ 
b/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
@@ -0,0 +1,30 @@
+---
+title:  Run-time Considerations for Multicast
+---
+
+When you use multicast for messaging and data distribution, you need to 
understand how the health monitoring setting works and how to control memory 
use.
+
+**Multicast Health Monitor**
+
+The Geode management and monitoring system is supplemented by a 
maxRetransmissionRatio health monitoring setting for distributed system 
members. This ratio is the number of retransmission requests received divided 
by the number of multicast datagrams written. If the ratio is at 1.0, the 
member is retransmitting as many packets as it originally sent. Retransmissions 
are point-to-point, and many processes may request retransmission, so this 
number can get quite high if problems occur. The default value for 
maxRetransmissionRatio is 0.2.
+
+For example, consider a distributed system with one producer and two consumers 
of cache events using multicast to transmit cache updates. The new member is 
added, which is running on a machine without multicast enabled. As a result, 
there is a retransmission request for every cache update, and the 
maxRetransmissionRatio changes to 1.0.
+
+**Controlling Memory Use on Geode Hosts with Multicast**
+
+Running out of memory can impede a member’s performance and eventually lead 
to severe errors.
+
+When data is distributed over multicast, Geode incurs a fixed overhead of 
memory reserved for transmission buffers. A specified amount of memory is 
reserved for each distributed region. These producer-side buffers are used only 
when a receiver is not getting enough CPU to read from its own receiving buffer 
as quickly as the producer is sending. In this case, the receiver complains of 
lost data. The producer then retrieves the data, if it still exists in its 
buffer, and resends to the receiver.
+
+Tuning the transmission buffers requires a careful balance. Larger buffers 
mean that more data remains available for retransmission, providing more 
protection in case of a problem. On the other hand, a larger amount of reserved 
memory means that less memory is available for caching.
+
+You can adjust the transmission buffer size by resetting the 
mcast-send-buffer-size parameter in the `gemfire.properties` file:
+
+``` pre
+mcast-send-buffer-size=45000
+```
+
+**Note:**
+The maximum buffer size is constrained only by the limits of your system. If 
you are not seeing problems that could be related to lack of memory then do not 
change the default, since it provides greater protection in case of network 
problems.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb
--
diff --git 
a/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb
 
b/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb
new file mode 100644
index 000..d339a55
--- /dev/null
+++ 
b/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb
@@ -0,0 +1,128 @@
+---
+title:  Testing Multicast Speed Limits
+---
+
+TCP automatically adjusts its speed to the capability of the processes using 
it and enforces bandwidth sharing so that every process gets a turn. With 
multicast, you must determine and explicitly set those limits.
+
+
+Without the proper configuration, multicast delivers its traffic as fast as 
possible, overrunning the ability of consumers to process the data and locking 
out other processes that are waiting for the bandwidth. You can tune your 
multicast and unicast behavior using mcast-flow-control in `gemfire.properties`.
+
+**Using Iperf**
+
+Iperf is an open-source TCP/UDP performance tool that you can use to find your 
site’s maximum rate for data distribution over multicast. Iperf can be 
downloaded from web sites such as the National Laboratory for Applied Network 
Research (NLANR).
+
+Iperf measures maximum bandwidth, allowing you to tune parameters and UDP 
characteristics. Iperf reports statistics on bandwidth, delay jitter, and 
datagram loss. On Linux, you can redirect this output to a file; on Windows, 
use the -o filename parameter.
+
+Run each test for ten minutes to make sure any potential problems have a 
chance

[20/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/distributed_how_3.svg
--
diff --git a/geode-docs/images_svg/distributed_how_3.svg 
b/geode-docs/images_svg/distributed_how_3.svg
new file mode 100644
index 000..a466636
--- /dev/null
+++ b/geode-docs/images_svg/distributed_how_3.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="130 293 355 193" 
width="355pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 11:15Zhow_it_works-3Layer 
1Member (M1)Member 
(M2)ApplicationDistributed Region AX1Distributed Region 
AX1

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/distributed_preload.svg
--
diff --git a/geode-docs/images_svg/distributed_preload.svg 
b/geode-docs/images_svg/distributed_preload.svg
new file mode 100644
index 000..681c824
--- /dev/null
+++ b/geode-docs/images_svg/distributed_preload.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="77 311 310 85" 
width="310pt" height="85pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 23:02ZpreloadLayer 1DistributedSystemDistributed Region(Preloaded or Normal)XYOperations for existing entry 
keys

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/distributed_replica.svg
--
diff --git a/geode-docs/images_svg/distributed_replica.svg 
b/geode-docs/images_svg/distributed_replica.svg
new file mode 100644
index 000..b28d8da
--- /dev/null
+++ b/geode-docs/images_svg/distributed_replica.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="95 347 310 85" 
width="310pt" height="85pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 23:02ZreplicaLayer 1DistributedSystemDistributed Region(Replica)XYAll creationsOther entry 
operations(due 
to distribution)

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/distributed_replica_preload.svg
--
diff --git a/geode-docs/images_svg/distributed_replica_preload.svg 
b/geode-docs/images_svg/distributed_replica_preload.svg
new file mode 100644
index 000..a40b99e
--- /dev/null
+++ b/geode-docs/images_svg/distributed_replica_preload.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="86 275 409 265" 
width="409pt" height="265pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 23:02Zreplica_or_preloadLayer 1Member (M1) Member 
(M2)Distributed Region AXDistributed Region AXYZMember (M3)Distributed Region 
A(replica or 
preloaded)XYZDistributedSystem

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/expiration.svg
--
diff --git a/geode-docs/images_svg/expiration.svg 
b/geode-docs/images_svg/expiration.svg
new file mode 100644
index 000..8fc278b
--- /dev/null
+++ b/geode-docs/images_svg/expiration.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="104 275 421 301" 
width="421pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:58ZexpirationLayer 1Distributed SystemConsumer Member #1Producer Member 
#1Distributed Region 
AXDistributed Region AXYYdatabaseEntry TTL1 hour: destroyConsumer Member 
#2Distributed Region AXYEntry Idle Tx="68.512695" y="9" textLength="14.501953">imefont-family="Helvetica" font-size="9" font-weight="500" fill="black" 
 >x="11.730957" y="20" textLength="82.538086">15 min: local 
 >destroyfill="url(#Obj_Gradient_11)"/>stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">Entry Idle Time15 
min: local destroy

[13/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_partitioned_2.svg
--
diff --git a/geode-docs/images_svg/transactions_partitioned_2.svg 
b/geode-docs/images_svg/transactions_partitioned_2.svg
new file mode 100644
index 000..a9445e1
--- /dev/null
+++ b/geode-docs/images_svg/transactions_partitioned_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="36 167 580 274" 
width="580pt" height="274pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:52Zpartition-2Layer 1Member 
(M1)CachePartition Region 
AJava Applicationsecondary dataWMember (M2)
 CacheT3XPartition Region Bdata accessor 
onlyReplicate Region RFGPartition Region 
Aprimary 
dataWXPartition Region 
Bprimary 
dataZReplicate Region RFGYRegion AWXRegion BZRegion 
RFG
 YTransaction T3

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_1.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_1.svg 
b/geode-docs/images_svg/transactions_replicate_1.svg
new file mode 100644
index 000..094bc58
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="36 149 585 337" 
width="585pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:54Zreplicate-1Layer 1Member (M1)CacheReplicate Region A
 Java ApplicationWMember 
(M2)T1Replicate Region BXRegion AW1Region BX1Transaction T1CacheReplicate Region AWMember 
(M3)CacheReplicate Region BX2Replicate Region BXTransaction T2Java ApplicationT2

[10/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/tune_cs_event_messaging.svg
--
diff --git a/geode-docs/images_svg/tune_cs_event_messaging.svg 
b/geode-docs/images_svg/tune_cs_event_messaging.svg
new file mode 100644
index 000..5af9f53
--- /dev/null
+++ b/geode-docs/images_svg/tune_cs_event_messaging.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="114 214 391 346" 
width="391pt" height="346pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:33Ztune-cs-messagingLayer 
1ServerBClient3A12A11B2A10A9B1send message A-10subscription queuethreadop #
 ServerBClient3A
 12A11Bfont-family="Helvetica" font-size="10" font-weight="500" fill="black" 
 >x="9.719238" y="10" textLength="5.5615234">2y="468" width="27" height="18" fill="url(#Obj_Gradient_1b)"/>x="424.125" y="468" width="27" height="18" stroke="#252525" 
 >stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="9.165039" y="10" textLength="6.669922">Ax="451.125" y="468" width="27" height="18" 
 >fill="url(#Obj_Gradient_1c)"/>height="18" stroke="#252525" stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="6.9384766" y="10" textLength="11.123047">10B1subscription 
queuethreadop #Stage 1Stage 2

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/unbalanced_network_capacity_probs.svg
--
diff --git a/geode-docs/images_svg/unbalanced_network_capacity_probs.svg 
b/geode-docs/images_svg/unbalanced_network_capacity_probs.svg
new file mode 100644
index 000..c24c082
--- /dev/null
+++ b/geode-docs/images_svg/unbalanced_network_capacity_probs.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="113 275 283 271" 
width="283pt" height="271pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:58Zunbalanced networkLayer 
1app1(producer)app2app3app4networkswitch10 Mbps10 
Mbps10 Mbps5 Mbps

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
--
diff --git a/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb 
b/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
new file mode 100644
index 000..7303800
--- /dev/null
+++ b/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
@@ -0,0 +1,42 @@
+---
+title:  Handling Forced Cache Disconnection Using Autoreconnect
+---
+
+A Geode member may be forcibly disconnected from a Geode distributed system if 
the member is unresponsive for a period of time, or if a network partition 
separates one or more members into a group that is too small to act as the 
distributed system.
+
+## How the Autoreconnection Process Works
+
+After being disconnected from a distributed system a Geode member shuts down 
and then automatically restarts into a "reconnecting" state, while periodically 
attempting to rejoin the distributed system by contacting a list of known 
locators. If the member succeeds in reconnecting to a known locator, the member 
rebuilds its view of the distributed system from existing members and receives 
a new distributed system ID.
+
+If the member cannot connect to a known locator, the member will then check to 
see if it itself is a locator (or hosting an embedded locator process). If the 
member is a locator, then the member does a quorum-based reconnect; it will 
attempt to contact a quorum of the members that were in the membership view 
just before it became disconnected. If a quorum of members can be contacted, 
then startup of the distributed system is allowed to begin. Since the 
reconnecting member does not know which members survived the network partition 
event, all members that are in a reconnecting state will keep their UDP unicast 
ports open and respond to ping requests.
+
+Membership quorum is determined using the same member weighting system used in 
network partition detection. See [Membership Coordinators, Lead Members and 
Member 
Weighting](../network_partitioning/membership_coordinators_lead_members_and_weighting.html#concept_23C2606D59754106AFBFE17515DF4330).
+
+Note that when a locator is in the reconnecting state, it provides no 
discovery services for the distributed system.
+
+After the cache has reconnected, applications must fetch a reference to the 
new Cache, Regions, DistributedSystem and other artifacts. Old references will 
continue to throw cancellation exceptions like 

[15/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/region_entry_versions_2.svg
--
diff --git a/geode-docs/images_svg/region_entry_versions_2.svg 
b/geode-docs/images_svg/region_entry_versions_2.svg
new file mode 100644
index 000..0efcc23
--- /dev/null
+++ b/geode-docs/images_svg/region_entry_versions_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="17 33 535 193" 
width="535pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-03 01:12ZCanvas 9Layer 1Member C
 Replicated 
RegionMember 
AMember 
BApplicationReplicated 
RegionX 
(A3)Replicated RegionApplicationApplicationX 
(A3)X 
(C3)X (A3)X 
(A3)(ignored)

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/region_entry_versions_3.svg
--
diff --git a/geode-docs/images_svg/region_entry_versions_3.svg 
b/geode-docs/images_svg/region_entry_versions_3.svg
new file mode 100644
index 000..105db57
--- /dev/null
+++ b/geode-docs/images_svg/region_entry_versions_3.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="26 101 535 193" 
width="535pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-03 01:12ZCanvas 8Layer 1Member CReplicated RegionMember A 
Member BApplicationReplicated RegionX (C3)Replicated 
RegionApplicationApplicationX (C3)X (C3)X 
(C3)X 
(C3)

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/server_client_event_dist.svg
--
diff --git a/geode-docs/images_svg/server_client_event_dist.svg 
b/geode-docs/images_svg/server_client_event_dist.svg
new file mode 100644
index 000..2d726cd
--- /dev/null
+++ b/geode-docs/images_svg/server_client_event_dist.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="27 275 293 301" 
width="293pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:51Z
 cs-event-distributionLayer 
1Client 
1Region Apool-name = ServerPoolinterest in XreceiveValues = trueServerRegion AXCache 
ServerClient 2XUpdate/CreateRegion Apool-name = ServerPoolinterest in XreceiveValues = 
falsepool 
“ServerPool”(with 
subscriptions enabled)pool 
“ServerPool”(with 
subscriptions enabled)Update/CreateInvalidateXX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/server_discovery.svg
--
diff --git a/geode-docs/images_svg/server_discovery.svg 
b/geode-docs/images_svg/server_discovery.svg
new file mode 100644
index 000..661b66f
--- /dev/null
+++ b/geode-docs/images_svg/server_discovery.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="176 248 373 341" 
width="373pt" height="341pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:31Zhow_server_discovery_worksLayer 
1Server #1ClientLocal Cacheconnection poolLocatorsend address and load inforequest serverconnectionServer 
#2Cache DataCache Datalistening on 10.80.100.1 :  
40404listening on 10.80.100.2 :  40404listening on lucy : 4locator atlucy : 41use 
10.80.100.2 : 404042client/server communication3

[02/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/nativeclient/client-cache/application-plugins.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/client-cache/application-plugins.html.md.erb 
b/geode-docs/nativeclient/client-cache/application-plugins.html.md.erb
new file mode 100644
index 000..8d23295
--- /dev/null
+++ b/geode-docs/nativeclient/client-cache/application-plugins.html.md.erb
@@ -0,0 +1,262 @@
+---
+title:  Specifying Application Plug-In Attributes
+---
+
+
+The plug-in attributes allow you to customize client region behavior for 
loading, updating, deleting, and overflowing region data and for accessing data 
in server partitioned regions. All client plug-ins are available through the 
C++ and .NET API.
+
+Application plug-ins for cache regions in clients can be declared either 
programmatically or in the `cache.xml` file.
+
+
+
+Figure: Where Application Plug-Ins Run
+
+
+
+## Overview of Application Plug-ins
+
+The API provides the framework for application plug-ins with callback 
functions for the appropriate events. Your classes and functions can customize 
these for your application's needs. When creating a region, specify these as 
part of the region's attributes settings. For regions already in the cache, you 
can specify new `CacheLoader`, `CacheWriter`, and `CacheListener` using the 
region's `AttributesMutator`. The `PartitionResolver` is not mutable.
+
+-   `CacheLoader`: A data loader called when an entry get operation fails to 
find a value for a given key. A cache loader is generally used to retrieve data 
from an outside source such as a database, but it may perform any operation 
defined by the user. Loaders are invoked as part of the distributed loading 
activities for entry retrieval, described in [Entry 
Retrieval](accessing-entries.html#accessing-entries__section_AD6AFD842C144C128FA1C7F0B9283372).
+-   `CacheWriter`: A synchronous event listener that receives callbacks before 
region events occur and has the ability to abort the operations. Writers are 
generally used to keep a back-end data source synchronized with the cache.
+-   `CacheListener`: An asynchronous event listener for region events in the 
local cache.
+-   `PartitionResolver`: Used for single-hop access to partitioned region 
entries on the server side. This resolver implementation must match that of the 
`PartitionResolver` on the server side.
+
+The following XML declaration specifies a cache loader for a region when the 
region is created.
+
+``` pre
+
+
+
+
+```
+
+The rest of this section gives more detailed descriptions of these application 
plug-ins, followed by special considerations for plug-ins in distributed 
regions and some guidelines for writing callbacks.
+
+## CacheLoader
+
+A cache loader is an application plug-in used to load data into the region. 
When an entry is requested that is unavailable in the region, a cache loader 
may be called upon to load it. Generally, you use a cache loader to retrieve 
the data from a database or another source outside the distributed system, but 
it may perform any operation defined by the user.
+
+The `CacheLoader` interface provides one function, `load`, for customizing 
region entry loading. A distributed region may have cache loaders defined in 
any or all caches where the region is defined. When loading an entry value, a 
locally defined cache loader is always used before a remote loader. In 
distributed regions, loaders are available for remote entry retrieval.
+
+## CacheWriter
+
+A cache writer is an application plug-in that synchronously handles changes to 
a region's contents. It is generally used to keep back-end data sources 
synchronized with a cache region. A cache writer has callback functions to 
handle region destruction and entry creation, update, and destruction. These 
functions are all called before the modification has taken place and can abort 
the operation.
+
+You can also use cache writers to store data that you want to make persistent.
+
+## CacheListener
+
+A cache listener is an application plug-in that asynchronously handles changes 
to a region's contents. A cache listener has callback functions to handle 
region destruction and invalidation, along with entry creation, update, 
invalidation, and destruction. These functions are called asynchronously after 
the modification has taken place.
+
+This declarative XML example establishes a cache listener when a region is 
created:
+
+``` pre
+
+
+
+
+
+```
+
+Unlike cache loaders and cache writers, cache listeners only receive events 
for entries to which the client has performed operations or registered interest.
+
+When the listener is attached to a region with caching disabled, the old value 
is always `NULL`.
+
+**Note:**
+Do not perform region operations inside the cache listener. Once you have 
configured a cache listener, the event supplies the ne

[66/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/implementing_security.html.md.erb
--
diff --git a/geode-docs/managing/security/implementing_security.html.md.erb 
b/geode-docs/managing/security/implementing_security.html.md.erb
index a38dd03..c0afc5c 100644
--- a/geode-docs/managing/security/implementing_security.html.md.erb
+++ b/geode-docs/managing/security/implementing_security.html.md.erb
@@ -2,6 +2,23 @@
 title:  Security Implementation Introduction and Overview
 ---
 
+
+
 ## Security Features
 
 Encryption, SSL secure communication, authentication, and authorization 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/implementing_ssl.html.md.erb
--
diff --git a/geode-docs/managing/security/implementing_ssl.html.md.erb 
b/geode-docs/managing/security/implementing_ssl.html.md.erb
index 73bbf49..c19b6d9 100644
--- a/geode-docs/managing/security/implementing_ssl.html.md.erb
+++ b/geode-docs/managing/security/implementing_ssl.html.md.erb
@@ -2,6 +2,23 @@
 title:  Configuring SSL
 ---
 
+
+
 You can configure SSL for authentication between members and to protect your 
data during
 distribution. You can use SSL alone or in conjunction with the other Geode 
security options.
 Geode SSL connections use the Java Secure Sockets Extension (JSSE) package.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/post_processing.html.md.erb
--
diff --git a/geode-docs/managing/security/post_processing.html.md.erb 
b/geode-docs/managing/security/post_processing.html.md.erb
index 2a6dc50..f0ce32e 100644
--- a/geode-docs/managing/security/post_processing.html.md.erb
+++ b/geode-docs/managing/security/post_processing.html.md.erb
@@ -2,6 +2,23 @@
 title:  Post Processing of Region Data
 ---
 
+
+
 The  `PostProcessor` interface allows the definition of a callback
 that is invoked after any and all client and `gfsh` operations that get data,
 but before the data is returned.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/properties_file.html.md.erb
--
diff --git a/geode-docs/managing/security/properties_file.html.md.erb 
b/geode-docs/managing/security/properties_file.html.md.erb
index d4758c1..e9ba1d6 100644
--- a/geode-docs/managing/security/properties_file.html.md.erb
+++ b/geode-docs/managing/security/properties_file.html.md.erb
@@ -1,6 +1,23 @@
 ---
 title: Where to Place Security Configuration Settings 
 ---
+
+
 
 
 Any security-related (properties that begin with `security-*`) configuration 
properties that are normally configured in `gemfire.properties` can be moved to 
a separate `gfsecurity.properties` file. Placing these configuration settings 
in a separate file allows you to restrict access to security configuration 
data. This way, you can still allow read or write access for your 
`gemfire.properties` file.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/security-audit.html.md.erb
--
diff --git a/geode-docs/managing/security/security-audit.html.md.erb 
b/geode-docs/managing/security/security-audit.html.md.erb
index f35a29a..0a6c410 100644
--- a/geode-docs/managing/security/security-audit.html.md.erb
+++ b/geode-docs/managing/security/security-audit.html.md.erb
@@ -1,6 +1,23 @@
 ---
 title: External Interfaces, Ports, and Services
 ---
+
+
 
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/security_audit_overview.html.md.erb
--
diff --git a/geode-docs/managing/security/security_audit_overview.html.md.erb 
b/geode-docs/managing/security/security_audit_overview.html.md.erb
index 307dc2c..7f1c374 100644
--- a/geode-docs/managing/security/security_audit_overview.html.md.erb
+++ b/geode-docs/managing/security/security_audit_overview.html.md.erb
@@ -1,6 +1,23 @@
 ---
 title: Security Detail Considerations
 ---
+
+
 
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/security/security_intro.html.md.erb
--
diff --git a/geode-docs/managing/security/security_intro.html.md.erb 
b/geode-docs/managing/security/security_intro.html.md.erb
index 1ebf105..7b70a7f 100644
--- a/geode-docs/managing/security/security_intro.html.md.erb
+++ b/geode-docs/managing/security/security_intro.html.md.erb
@@ -2,6 +2,23 @@
 title:  Security Features
 ---
 
+
+
 Encryption, SSL secure communication, authentication, and authorization 
 featu

[16/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/partitioned_data_buckets_1.svg
--
diff --git a/geode-docs/images_svg/partitioned_data_buckets_1.svg 
b/geode-docs/images_svg/partitioned_data_buckets_1.svg
new file mode 100644
index 000..a8cf406
--- /dev/null
+++ b/geode-docs/images_svg/partitioned_data_buckets_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="95 239 409 337" 
width="409pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:47Zbuckets-1Layer 1Member (M1)Partition Region 
A<
 /g>Member 
(M2)Partition Region AMember (M3)Partition Region A

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/partitioned_data_buckets_2.svg
--
diff --git a/geode-docs/images_svg/partitioned_data_buckets_2.svg 
b/geode-docs/images_svg/partitioned_data_buckets_2.svg
new file mode 100644
index 000..a996ca7
--- /dev/null
+++ b/geode-docs/images_svg/partitioned_data_buckets_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="95 239 409 337" 
width="409pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:47Zbuckets-2Layer 1Member (M1)Partition Region 
AMember (M2)Partition 
Region AMember (M3)Partition Region 
A

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/region_entry_versions_1.svg
--
diff --git a/geode-docs/images_svg/region_entry_versions_1.svg 
b/geode-docs/images_svg/region_entry_versions_1.svg
new file mode 100644
index 000..ef3f074
--- /dev/null
+++ b/geode-docs/images_svg/region_entry_versions_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="50 182 535 193" 
width="535pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-03 18:54Ztemp_content
 Layer 1GemFire Member CReplicated 
Region<
 /g>GemFire Member AGemFire Member BApplicationReplicated RegionX (A3)Replicated RegionApplicationApplicationX (C2)X (C3)XX

[28/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/region_options/region_types.html.md.erb
--
diff --git a/geode-docs/developing/region_options/region_types.html.md.erb 
b/geode-docs/developing/region_options/region_types.html.md.erb
new file mode 100644
index 000..45908dd
--- /dev/null
+++ b/geode-docs/developing/region_options/region_types.html.md.erb
@@ -0,0 +1,129 @@
+---
+title:  Region Types
+---
+
+Region types define region behavior within a single distributed system. You 
have various options for region data storage and distribution.
+
+
+Within a Geode distributed system, you can define distributed regions and 
non-distributed regions, and you can define regions whose data is spread across 
the distributed system, and regions whose data is entirely contained in a 
single member.
+
+Your choice of region type is governed in part by the type of application you 
are running. In particular, you need to use specific region types for your 
servers and clients for effective communication between the two tiers:
+
+-   Server regions are created inside a `Cache` by servers and are accessed by 
clients that connect to the servers from outside the server's distributed 
system. Server regions must have region type partitioned or replicated. Server 
region configuration uses the `RegionShortcut` enum settings.
+-   Client regions are created inside a `ClientCache` by clients and are 
configured to distribute data and events between the client and the server 
tier. Client regions must have region type `local`. Client region configuration 
uses the `ClientRegionShortcut` enum settings.
+-   Peer regions are created inside a `Cache`. Peer regions may be server 
regions, or they may be regions that are not accessed by clients. Peer regions 
can have any region type. Peer region configuration uses the `RegionShortcut` 
enum settings.
+
+When you configure a server or peer region using `gfsh` or with the 
`cache.xml` file, you can use *region shortcuts* to define the basic 
configuration of your region. A region shortcut provides a set of default 
configuration attributes that are designed for various types of caching 
architectures. You can then add additional configuration attributes as needed 
to customize your application. For more information and a complete reference of 
these region shortcuts, see [Region Shortcuts 
Reference](../../reference/topics/region_shortcuts_reference.html#reference_lt4_54c_lk).
+
+
+
+These are the primary configuration choices for each data region.
+
+
+
+
+
+
+
+
+
+Region Type
+Description
+Best suited for...
+
+
+
+
+Partitioned
+System-wide setting for the data set. Data is divided into buckets across 
the members that define the region. For high availability, configure redundant 
copies so each bucket is stored in multiple members with one member holding the 
primary.
+Server regions and peer regions
+
+Very large data sets
+High availability
+Write performance
+Partitioned event listeners and data loaders
+
+
+
+Replicated (distributed)
+Holds all data from the distributed region. The data from the distributed 
region is copied into the member replica region. Can be mixed with 
non-replication, with some members holding replicas and some holding 
non-replicas.
+Server regions and peer regions
+
+Read heavy, small datasets
+Asynchronous distribution
+Query performance
+
+
+
+Distributed non-replicated
+Data is spread across the members that define the region. Each member 
holds only the data it has expressed interest in. Can be mixed with 
replication, with some members holding replicas and some holding 
non-replicas.
+Peer regions, but not server regions and not client regions
+
+Asynchronous distribution
+Query performance
+
+
+
+Non-distributed (local)
+The region is visible only to the defining member.
+Client regions and peer regions
+
+Data that is not shared between applications
+
+
+
+
+
+## Partitioned Regions
+
+Partitioning is a good choice for very large server regions. Partitioned 
regions are ideal for data sets in the hundreds of gigabytes and beyond.
+
+**Note:**
+Partitioned regions generally require more JDBC connections than other region 
types because each member that hosts data must have a connection.
+
+Partitioned regions group your data into buckets, each of which is stored on a 
subset of all of the system members. Data location in the buckets does not 
affect the logical view - all members see the same logical data set.
+
+Use partitioning for:
+
+-   **Large data sets**. Store data sets that are too large to fit into a 
single member, and all members will see the same logical data set. Partitioned 
regions divide the data into units of storage called buckets that are split 
across the members hosting the partitioned region data, so no member needs to 
host all of the region’s data. Geode provides dynamic redundancy recovery and 
rebalancin

[09/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
--
diff --git 
a/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb 
b/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
new file mode 100644
index 000..89e7178
--- /dev/null
+++ b/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
@@ -0,0 +1,79 @@
+---
+title:  Disk Store File Names and Extensions
+---
+
+Disk store files include store management files, access control files, and the 
operation log, or oplog, files, consisting of one file for deletions and 
another for all other operations.
+
+
+The next tables describe file names and extensions; they are followed by 
example disk store files.
+
+## File Names
+
+File names have three parts:
+
+**First Part of File Name: Usage Identifier**
+
+| Values   | Used for  
 | Examples   |
+|--|||
+| OVERFLOW | Oplog data from overflow regions and queues only. 
 | OVERFLOWoverflowDS1\_1.crf |
+| BACKUP   | Oplog data from persistent and persistent+overflow regions and 
queues. | BACKUPoverflowDS1.if, BACKUPDEFAULT.if |
+| DRLK\_IF | Access control - locking the disk store.  
 | DRLK\_IFoverflowDS1.lk, DRLK\_IFDEFAULT.lk |
+
+**Second Part of File Name: Disk Store Name**
+
+| Values  | Used for   
   | 
Examples
 |
+|-|---|--|
+|  | Non-default disk stores.   
   | 
name="overflowDS1" DRLK\_IFoverflowDS1.lk, name="persistDS1" 
BACKUPpersistDS1\_1.crf |
+| DEFAULT | Default disk store name, used when persistence or 
overflow are specified on a region or queue but no disk store is named. | 
DRLK\_IFDEFAULT.lk, BACKUPDEFAULT\_1.crf
 |
+
+**Third Part of File Name: oplog Sequence Number**
+
+| Values| Used for 
   | Examples   
  |
+|---|-|--|
+| Sequence number in the format \_n | Oplog data files only. Numbering starts 
with 1. | OVERFLOWoverflowDS1\_1.crf, BACKUPpersistDS1\_2.crf, 
BACKUPpersistDS1\_3.crf |
+
+## File Extensions
+
+| File extension | Used for | Notes

|
+||--|--|
+| if | Disk store metadata  | Stored 
in the first disk-dir listed for the store. Negligible size - not considered in 
size control. |
+| lk | Disk store access control| Stored 
in the first disk-dir listed for the store. Negligible size - not considered in 
size control. |
+| crf| Oplog: create, update, and invalidate operations | 
Pre-allocated 90% of the total max-oplog-size at creation.  
 |
+| drf| Oplog: delete operations | 
Pre-allocated 10% of the total max-oplog-size at creation.  
 |
+| krf| Oplog: key and crf offset information| Created 
after the oplog has reached the max-oplog-size. Used to improve performance at 
startup.  |
+
+Example files for disk stores persistDS1 and overflowDS1:
+
+``` pre
+bash-2.05$ ls -tlra persistData1/
+total 8
+-rw-rw-r--   1 person users188 Mar  4 06:17 BACKUPpersistDS1.if
+drwxrwxr-x   2 person users512 Mar  4 06:17 .
+-rw-rw-r--   1 person users  0 Mar  4 06:18 BACKUPpersistDS1_1.drf
+-rw-rw-r--   1 person users 38 Mar  4 06:18 BACKUPpersistDS1_1.crf
+drwxrwxr-x   8 person users512 Mar  4 06:20 ..
+bash-2.05$
+ 
+bash-2.05$ ls -ltra overflowData1/
+total 1028
+drwxrwxr-x   

[47/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/data_serialization/auto_serialization.html.md.erb
--
diff --git a/developing/data_serialization/auto_serialization.html.md.erb 
b/developing/data_serialization/auto_serialization.html.md.erb
deleted file mode 100644
index 7e3dfa2..000
--- a/developing/data_serialization/auto_serialization.html.md.erb
+++ /dev/null
@@ -1,124 +0,0 @@

-title:  Using Automatic Reflection-Based PDX Serialization

-
-You can configure your cache to automatically serialize and deserialize domain 
objects without having to add any extra code to them.
-
-
-You can automatically serialize and deserialize domain objects without coding 
a `PdxSerializer` class. You do this by registering your domain objects with a 
custom `PdxSerializer` called `ReflectionBasedAutoSerializer` that uses Java 
reflection to infer which fields to serialize.
-
-You can also extend the ReflectionBasedAutoSerializer to customize its 
behavior. For example, you could add optimized serialization support for 
BigInteger and BigDecimal types. See [Extending the 
ReflectionBasedAutoSerializer](extending_the_autoserializer.html#concept_9E020566EE794A81A48A90BA798EC279)
 for details.
-
-**Note:**
-Your custom PDX autoserializable classes cannot use the `com.gemstone` 
package. If they do, the classes will be ignored by the PDX auto serializer.
-
-
-
-**Prerequisites**
-
--   Understand generally how to configure the Geode cache.
--   Understand how PDX serialization works and how to configure your 
application to use `PdxSerializer`.
-
-Procedure
-
-In your application where you manage data from the cache, provide the 
following configuration and code as appropriate:
-
-1.  In the domain classes that you wish to autoserialize, make sure each class 
has a zero-arg constructor. For example:
-
-``` pre
-public PortfolioPdx(){}
-```
-
-2.  Using one of the following methods, set the PDX serializer to 
`ReflectionBasedAutoSerializer`.
-1.  In gfsh, execute the following command prior to starting up any 
members that host data:
-
-``` pre
-gfsh>configure pdx --auto-serializable-classes=com\.company\.domain\..*
-```
-
-By using gfsh, this configuration can propagated across the cluster 
through the [Cluster Configuration 
Service](../../configuring/cluster_config/gfsh_persist.html).
-
-2.  Alternately, in `cache.xml`:
-
-``` pre
-
-
-  
-
-  
-   org.apache.geode.pdx.ReflectionBasedAutoSerializer
-  
-  
-  com.company.domain.DomainObject
- 
-  
- 
-  ...
-
-```
-
-The parameter, `classes`, takes a comma-separated list of class 
patterns to define the domain classes to serialize. If your domain object is an 
aggregation of other domain classes, you need to register the domain object and 
each of those domain classes explicitly for the domain object to be serialized 
completely.
-
-3.  Using the Java API:
-
-``` pre
-Cache c = new CacheFactory()
-  .setPdxSerializer(new 
ReflectionBasedAutoSerializer("com.company.domain.DomainObject"))
-  .create();
-```
-
-3.  Customize the behavior of the `ReflectionBasedAutoSerializer` using one of 
the following mechanisms:
--   By using a class pattern string to specify the classes to 
auto-serialize and customize how the classes are serialized. Class pattern 
strings can be specified in the API by passing strings to the 
`ReflectionBasedAutoSerializer` constructor or by specifying them in cache.xml. 
See [Customizing Serialization with Class Pattern 
Strings](autoserialization_with_class_pattern_strings.html#concept_9B67BBE94B414B7EA63BD7E8D61D0312)
 for details.
--   By creating a subclass of `ReflectionBasedAutoSerializer` and 
overriding specific methods. See [Extending the 
ReflectionBasedAutoSerializer](extending_the_autoserializer.html#concept_9E020566EE794A81A48A90BA798EC279)
 for details.
-
-4.  If desired, configure the `ReflectionBasedAutoSerializer` to check the 
portability of the objects it is passed before it tries to autoserialize them. 
When this flag is set to true, the `ReflectionBasedAutoSerializer` will throw a 
`NonPortableClassException` error when trying to autoserialize a non-portable 
object. To set this, use the following configuration:
--   In gfsh, use the following command:
-
-``` pre
-gfsh>configure pdx 
--portable-auto-serializable-classes=com\.company\.domain\..*
-```
-
-By using gfsh, this configuration can propagated across the cluster 
through the [Cluster Configuration 
Service](../../configuring/cluster_config/gfsh_persist.html).
--   In cache.xml:
-
-``` pre
-
-
-  
-
-  
-   

[71/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/distributed_regions/chapter_overview.html.md.erb
--
diff --git 
a/geode-docs/developing/distributed_regions/chapter_overview.html.md.erb 
b/geode-docs/developing/distributed_regions/chapter_overview.html.md.erb
index ce33ee2..d24de37 100644
--- a/geode-docs/developing/distributed_regions/chapter_overview.html.md.erb
+++ b/geode-docs/developing/distributed_regions/chapter_overview.html.md.erb
@@ -2,6 +2,23 @@
 title:  Distributed and Replicated Regions
 ---
 
+
+
 In addition to basic region management, distributed and replicated regions 
include options for things like push and pull distribution models, global 
locking, and region entry versions to ensure consistency across Geode members.
 
 -   **[How Distribution 
Works](../../developing/distributed_regions/how_distribution_works.html)**

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/distributed_regions/choosing_level_of_dist.html.md.erb
--
diff --git 
a/geode-docs/developing/distributed_regions/choosing_level_of_dist.html.md.erb 
b/geode-docs/developing/distributed_regions/choosing_level_of_dist.html.md.erb
index f48aaeb..3d48ab4 100644
--- 
a/geode-docs/developing/distributed_regions/choosing_level_of_dist.html.md.erb
+++ 
b/geode-docs/developing/distributed_regions/choosing_level_of_dist.html.md.erb
@@ -2,6 +2,23 @@
 title:  Options for Region Distribution
 ---
 
+
+
 You can use distribution with and without acknowledgment, or global locking 
for your region distribution. Regions that are configured for distribution with 
acknowledgment can also be configured to resolve concurrent updates 
consistently across all Geode members that host the region.
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/distributed_regions/how_distribution_works.html.md.erb
--
diff --git 
a/geode-docs/developing/distributed_regions/how_distribution_works.html.md.erb 
b/geode-docs/developing/distributed_regions/how_distribution_works.html.md.erb
index bbc7522..857a194 100644
--- 
a/geode-docs/developing/distributed_regions/how_distribution_works.html.md.erb
+++ 
b/geode-docs/developing/distributed_regions/how_distribution_works.html.md.erb
@@ -2,6 +2,23 @@
 title:  How Distribution Works
 ---
 
+
+
 To use distributed and replicated regions, you should understand how they work 
and your options for managing them.
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
--
diff --git 
a/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
 
b/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
index 7e4c551..c8b98f7 100644
--- 
a/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
+++ 
b/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
@@ -2,6 +2,23 @@
 title: Consistency Checking by Region Type
 ---
 
+
+
 
 
 Geode performs different consistency checks depending on the type of region 
you have configured.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/distributed_regions/how_region_versioning_works_wan.html.md.erb
--
diff --git 
a/geode-docs/developing/distributed_regions/how_region_versioning_works_wan.html.md.erb
 
b/geode-docs/developing/distributed_regions/how_region_versioning_works_wan.html.md.erb
index 0ce2f04..275d496 100644
--- 
a/geode-docs/developing/distributed_regions/how_region_versioning_works_wan.html.md.erb
+++ 
b/geode-docs/developing/distributed_regions/how_region_versioning_works_wan.html.md.erb
@@ -2,6 +2,23 @@
 title:  How Consistency Is Achieved in WAN Deployments
 ---
 
+
+
 When two or more Geode systems are configured to distribute events over a WAN, 
each system performs local consistency checking before it distributes an event 
to a configured gateway sender. Discarded events are not distributed across the 
WAN.
 
 Regions can also be configured to distribute updates to other Geode clusters 
over a WAN. With a distributed WAN configuration, multiple gateway senders 
asynchronously queue and send region updates to another Geode cluster. It is 
possible for multiple sites to send updates to the same region entry at the 
same time. It is also possible that, due to a slow WAN connection, a cluster 
might receive region updates after a considerable delay, and after it has 
applied more recent updates to a region. To ensure that WAN-replicated regions 
eventually reach a consist

[70/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/partitioned_regions/configure_pr_single_hop.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/configure_pr_single_hop.html.md.erb 
b/geode-docs/developing/partitioned_regions/configure_pr_single_hop.html.md.erb
index 5518905..a7eeeb2 100644
--- 
a/geode-docs/developing/partitioned_regions/configure_pr_single_hop.html.md.erb
+++ 
b/geode-docs/developing/partitioned_regions/configure_pr_single_hop.html.md.erb
@@ -2,6 +2,23 @@
 title:  Configure Client Single-Hop Access to Server-Partitioned Regions
 ---
 
+
+
 Configure your client/server system for direct, single-hop access to 
partitioned region data in the servers.
 
 This requires a client/server installation that uses one or more partitioned 
regions on the server.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb
 
b/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb
index 7ee7133..ccb7e71 100644
--- 
a/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb
+++ 
b/geode-docs/developing/partitioned_regions/configuring_bucket_for_pr.html.md.erb
@@ -2,6 +2,23 @@
 title:  Configuring the Number of Buckets for a Partitioned Region
 ---
 
+
+
 Decide how many buckets to assign to your partitioned region and set the 
configuration accordingly.
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/partitioned_regions/configuring_ha_for_pr.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/configuring_ha_for_pr.html.md.erb 
b/geode-docs/developing/partitioned_regions/configuring_ha_for_pr.html.md.erb
index a9a98fb..c084f4a 100644
--- 
a/geode-docs/developing/partitioned_regions/configuring_ha_for_pr.html.md.erb
+++ 
b/geode-docs/developing/partitioned_regions/configuring_ha_for_pr.html.md.erb
@@ -2,6 +2,23 @@
 title:  Configure High Availability for a Partitioned Region
 ---
 
+
+
 Configure in-memory high availability for your partitioned region. Set other 
high-availability options, like redundancy zones and redundancy recovery 
strategies.
 
 Here are the main steps for configuring high availability for a partitioned 
region. See later sections for details.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/partitioned_regions/custom_partitioning_and_data_colocation.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/custom_partitioning_and_data_colocation.html.md.erb
 
b/geode-docs/developing/partitioned_regions/custom_partitioning_and_data_colocation.html.md.erb
index 0cd5f63..3e4f185 100644
--- 
a/geode-docs/developing/partitioned_regions/custom_partitioning_and_data_colocation.html.md.erb
+++ 
b/geode-docs/developing/partitioned_regions/custom_partitioning_and_data_colocation.html.md.erb
@@ -2,6 +2,23 @@
 title:  Understanding Custom Partitioning and Data Colocation
 ---
 
+
+
 Custom partitioning and data colocation can be used separately or in 
conjunction with one another.
 
 ## Custom Partitioning

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/partitioned_regions/how_partitioning_works.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/how_partitioning_works.html.md.erb 
b/geode-docs/developing/partitioned_regions/how_partitioning_works.html.md.erb
index 68e8dd2..c846995 100644
--- 
a/geode-docs/developing/partitioned_regions/how_partitioning_works.html.md.erb
+++ 
b/geode-docs/developing/partitioned_regions/how_partitioning_works.html.md.erb
@@ -2,6 +2,23 @@
 title:  Understanding Partitioning
 ---
 
+
+
 To use partitioned regions, you should understand how they work and your 
options for managing them.
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb 
b/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb
index 5082cc4..ba83732 100644
--- a/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb
+++ b/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb
@@ -2,6 +2,23 @@
 title:  Understanding High Availability for Partitioned Regions
 ---
 
+
+
 With high availability, each member t

[48/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/configuring/running/deploying_config_jar_files.html.md.erb
--
diff --git a/configuring/running/deploying_config_jar_files.html.md.erb 
b/configuring/running/deploying_config_jar_files.html.md.erb
deleted file mode 100644
index bf855c6..000
--- a/configuring/running/deploying_config_jar_files.html.md.erb
+++ /dev/null
@@ -1,35 +0,0 @@

-title:  Deploying Configuration Files in JAR Files

-
-This section provides a procedure and an example for deploying configuration 
files in JAR files.
-
-**Procedure**
-
-1.  Jar the files.
-2.  Set the Apache Geode system properties to point to the files as they 
reside in the jar file.
-3.  Include the jar file in your `CLASSPATH.`
-4.  Verify the jar file copies are the only ones visible to the application at 
runtime. Geode searches the `CLASSPATH` after searching other locations, so the 
files cannot be available in the other search areas.
-5.  Start your application. The configuration file is loaded from the jar file.
-
-**Example of Deploying a Configuration JAR**
-
-The following example deploys the cache configuration file, `myCache.xml`, in 
`my.jar`. The following displays the contents of `my.jar`:
-
-``` pre
-% jar -tf my.jar 
-META-INF 
-META-INF/MANIFEST.MF 
-myConfig/ 
-myConfig/myCache.xml
-```
-
-In this example, you would perform the following steps to deploy the 
configuration jar file:
-
-1.  Set the system property, `gemfire.cache-xml-file`, to 
`myConfig/myCache.xml`
-2.  Set your `CLASSPATH` to include `my.jar`.
-3.  Verify there is no file named `myCache.xml` in `./myConfig/myCache.xml`, 
the current directory location of the file
-
-When you start your application, the configuration file is loaded from the jar 
file.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/configuring/running/firewall_ports_config.html.md.erb
--
diff --git a/configuring/running/firewall_ports_config.html.md.erb 
b/configuring/running/firewall_ports_config.html.md.erb
deleted file mode 100644
index 4f90602..000
--- a/configuring/running/firewall_ports_config.html.md.erb
+++ /dev/null
@@ -1,15 +0,0 @@

-title:  Firewall Considerations

-
-You can configure and limit port usage for situations that involve firewalls, 
for example, between client-server or server-server connections.
-
--   **[Firewalls and 
Connections](../../configuring/running/firewalls_connections.html)**
-
-Be aware of possible connection problems that can result from running a 
firewall on your machine.
-
--   **[Firewalls and Ports](../../configuring/running/firewalls_ports.html)**
-
-Make sure your port settings are configured correctly for firewalls.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/configuring/running/firewalls_connections.html.md.erb
--
diff --git a/configuring/running/firewalls_connections.html.md.erb 
b/configuring/running/firewalls_connections.html.md.erb
deleted file mode 100644
index 3ae6bb1..000
--- a/configuring/running/firewalls_connections.html.md.erb
+++ /dev/null
@@ -1,18 +0,0 @@

-title:  Firewalls and Connections

-
-Be aware of possible connection problems that can result from running a 
firewall on your machine.
-
-Apache Geode is a network-centric distributed system, so if you have a 
firewall running on your machine it could cause connection problems. For 
example, your connections may fail if your firewall places restrictions on 
inbound or outbound permissions for Java-based sockets. You may need to modify 
your firewall configuration to permit traffic to Java applications running on 
your machine. The specific configuration depends on the firewall you are using.
-
-As one example, firewalls may close connections to Geode due to timeout 
settings. If a firewall senses no activity in a certain time period, it may 
close a connection and open a new connection when activity resumes, which can 
cause some confusion about which connections you have.
-
-For more information on how Geode client and servers connect, see the 
following topics:
-
--   [How Client/Server Connections 
Work](../../topologies_and_comm/topology_concepts/how_the_pool_manages_connections.html#how_the_pool_manages_connections)
--   [Socket 
Communication](../../managing/monitor_tune/socket_communication.html)
--   [Controlling Socket 
Use](../../managing/monitor_tune/performance_controls_controlling_socket_use.html#perf)
--   [Setting Socket Buffer 
Sizes](../../managing/monitor_tune/socket_communication_setting_socket_buffer_sizes.html)
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/configuring/running/firewalls_multisite.html.md.erb
--
diff --git

[19/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/hibernate_cs.svg
--
diff --git a/geode-docs/images_svg/hibernate_cs.svg 
b/geode-docs/images_svg/hibernate_cs.svg
new file mode 100644
index 000..ce9c3a8
--- /dev/null
+++ b/geode-docs/images_svg/hibernate_cs.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="59 233 493 205" 
width="493pt" height="205pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:24ZcsLayer 
1Partitioned Session DataPartitioned Session DataPartitioned 
Session 
DataServerServerServerPartitioned DataHibernate 
SessionClientaccess to Hibernate entitiesconnection poolIf data not found in cache, Hibernate accesses database...RelationalDatabasePartitioned DataPartitioned Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/hibernate_overview.svg
--
diff --git a/geode-docs/images_svg/hibernate_overview.svg 
b/geode-docs/images_svg/hibernate_overview.svg
new file mode 100644
index 000..0fd8669
--- /dev/null
+++ b/geode-docs/images_svg/hibernate_overview.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="146 287 389 228" 
width="389pt" height="19pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:06ZoverviewLayer 1Cached DataCached DataMemberHibernate 
SessionMemberCached Dataaccess to Hibernate entitiesIf data not found in cache, Hibernate accesses 
database...RelationalDatabaseCached Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/hibernate_p2p.svg
--
diff --git a/geode-docs/images_svg/hibernate_p2p.svg 
b/geode-docs/images_svg/hibernate_p2p.svg
new file mode 100644
index 000..bc536dc
--- /dev/null
+++ b/geode-docs/images_svg/hibernate_p2p.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="59 269 499 228" 
width="499pt" height="19pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:09Zp2pLayer 1stroke="#252525" stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="27.143066" y="10" textLength="81.713867">Hibernate 
 >SessionPeer CacheHibernate 
SessionPeer CacheHibernate SessionPeer CacheReplicated DataReplicated DataReplicated
  Dataaccess 
to Hibernate entitiesaccess to Hibernate entitiesaccess to Hibernate entitiesIf data not found in cache, Hibernate accesses 
database...RelationalDatabase

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/how_partitioning_works_1.svg
--
diff --git a/geode-docs/images_svg/how_partitioning_works_1.svg 
b/geode-docs/images_svg/how_partitioning_works_1.svg
new file mode 100644
index 000..b7cd2a2
--- /dev/null
+++ b/geode-docs/images_svg/how_partitioning_works_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="181 308 386 413" 
width="386pt" height="413pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:44Zhow_it_works_1Layer 
1Partitioned Region ALogical ViewXYZPartitioned Region APhysical ViewXMachine 1P
 artitioned Region AYMachine 2Partitioned Region AZMachine 3

[75/76] [abbrv] incubator-geode git commit: GEODE-1968 - set aside Hibernate Cache docs until feature is mainstreamed.

[kmiller]

GEODE-1968 - set aside Hibernate Cache docs until feature is mainstreamed.


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/fd8927cb
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/fd8927cb
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/fd8927cb

Branch: refs/heads/feature/GEODE-1952-2
Commit: fd8927cb1d74b46125589daf032d4eab43789d85
Parents: 6bea820
Author: Dave Barnes 
Authored: Thu Oct 6 13:08:23 2016 -0700
Committer: Dave Barnes 
Committed: Thu Oct 6 13:08:23 2016 -0700

--
 geode-docs/images/HibernateFlowchart.png| Bin 138228 -> 0 bytes
 geode-docs/images_svg/hibernate_cs.svg  |   3 -
 geode-docs/images_svg/hibernate_overview.svg|   3 -
 geode-docs/images_svg/hibernate_p2p.svg |   3 -
 geode-docs/tools_modules/book_intro.html.md.erb |   4 -
 .../hibernate_cache/advanced_config.html.md.erb |  51 --
 .../changing_gemfire_default_cfg.html.md.erb| 155 ---
 .../chapter_overview.html.md.erb|  54 ---
 .../chapter_overview_how_works.html.md.erb  |  25 ---
 .../hibernate_why_use_gemfire.html.md.erb   |  44 --
 .../installing_gemfire_and_module.html.md.erb   |  28 
 .../setting_up_the_module.html.md.erb   | 110 -
 ...sing_hibernate_with_http_session.html.md.erb |  39 -
 13 files changed, 519 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/fd8927cb/geode-docs/images/HibernateFlowchart.png
--
diff --git a/geode-docs/images/HibernateFlowchart.png 
b/geode-docs/images/HibernateFlowchart.png
deleted file mode 100644
index 55c500c..000
Binary files a/geode-docs/images/HibernateFlowchart.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/fd8927cb/geode-docs/images_svg/hibernate_cs.svg
--
diff --git a/geode-docs/images_svg/hibernate_cs.svg 
b/geode-docs/images_svg/hibernate_cs.svg
deleted file mode 100644
index ce9c3a8..000
--- a/geode-docs/images_svg/hibernate_cs.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
-http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="59 233 493 205" 
width="493pt" height="205pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:24ZcsLayer 
1Partitioned Session DataPartitioned Session DataPartitioned 
Session 
DataServerServerServerPartitioned DataHibernate 
SessionClientaccess to Hibernate entitiesconnection poolIf data not found in cache, Hibernate accesses database...RelationalDatabasePartitioned DataPartitioned Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/fd8927cb/geode-docs/images_svg/hibernate_overview.svg
--
diff --git a/geode-docs/images_svg/hibernate_overview.svg 
b/geode-docs/images_svg/hibernate_overview.svg
deleted file mode 100644
index 0fd8669..000
--- a/geode-docs/images_svg/hibernate_overview.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
-http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="146 287 389 228" 
width="389pt" height="19pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:06ZoverviewLayer 1Cached DataCached DataMemberHibernate 
SessionMemberCached Dataaccess to Hibernate entitiesIf data not found in cache, Hibernate accesses 
database...RelationalDatabaseCached Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/fd8927cb/geode-docs/images_svg/hibernate_p2p.svg
--
diff --git a/geode-docs/images_svg/hibernate_p2p.svg 
b/geode-docs/images_svg/hibernate_p2p.svg
deleted file mode 100644
index bc536dc..000
--- a/geode-docs/images_svg/hibernate_p2p.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
-http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="59 269 499 228" 
width="499pt" height="19pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:09Zp2pLayer 1stroke="#252525" stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="27.143066" y="10" textLength="81.713867">Hibernate 
 >SessionPeer CacheHibernate 
SessionPeer CacheHibernate SessionPeer CacheReplicated DataReplicated DataReplicated
  Dataaccess 
to Hibernate entitiesaccess to Hibernate entitiesaccess to Hibernate entitiesIf data not found in cac

[14/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/server_grouping.svg
--
diff --git a/geode-docs/images_svg/server_grouping.svg 
b/geode-docs/images_svg/server_grouping.svg
new file mode 100644
index 000..15eab1f
--- /dev/null
+++ b/geode-docs/images_svg/server_grouping.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="122 212 373 301" 
width="373pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:30Zserver_groupingLayer 
1Server #1
 Client #1Region: Portfoliosconnection 
poolServer #2Region: ProductsRegion: Portfolioslistening on 
10.80.100.1 :  40404group: 
Portfolioslistening on 10.80.100.2 :  40404group: 
Productslocator at lucy : 
4server-group: PortfoliosClient 
#2Region: Productsconnection 
poollocator 
at
  lucy : 4server-group: ProductsLocatorlistening on lucy : 
4Portfolios: 
10.80.100.1 : 40404Products: 10.80.100.2 : 
40404

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_partitioned_1.svg
--
diff --git a/geode-docs/images_svg/transactions_partitioned_1.svg 
b/geode-docs/images_svg/transactions_partitioned_1.svg
new file mode 100644
index 000..c101378
--- /dev/null
+++ b/geode-docs/images_svg/transactions_partitioned_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="5 95 562 274" 
width="562pt" height="274pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:50Zpartition-1Layer 1Member 
(M1)CacheXYRegion AZJava ApplicationTransaction T1primary datasecondary dataWWT1 local 
eventsMember (M2)CacheXYRegion AZTransaction T2secondary dataprimary 
dataWT2 local 
eventsYZT1T2

[76/76] [abbrv] incubator-geode git commit: Merge branch 'feature/GEODE-1952' into feature/GEODE-1952-2

[kmiller]

Merge branch 'feature/GEODE-1952' into feature/GEODE-1952-2


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/40c1ed59
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/40c1ed59
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/40c1ed59

Branch: refs/heads/feature/GEODE-1952-2
Commit: 40c1ed590fcc5d22a9b82cbb87fa89cc99aa49e3
Parents: e15657e fd8927c
Author: Karen Miller 
Authored: Wed Oct 12 10:10:10 2016 -0700
Committer: Karen Miller 
Committed: Wed Oct 12 10:10:10 2016 -0700

--
 geode-docs/.gitignore   |6 +
 geode-docs/CONTRIBUTE.md|   63 +
 geode-docs/README.md|   93 +
 geode-docs/about_geode.html.md.erb  |   26 +
 geode-docs/basic_config/book_intro.html.md.erb  |   40 +
 .../chapter_overview.html.md.erb|   40 +
 ...uted_system_member_configuration.html.md.erb |   51 +
 .../config_concepts/local_vs_remote.html.md.erb |   29 +
 .../chapter_overview.html.md.erb|   32 +
 .../managing_data_entries.html.md.erb   |  146 +
 .../using_custom_classes.html.md.erb|   51 +
 .../data_regions/chapter_overview.html.md.erb   |   65 +
 .../create_a_region_with_API.html.md.erb|   80 +
 .../create_a_region_with_cacheXML.html.md.erb   |   85 +
 .../create_a_region_with_gfsh.html.md.erb   |   55 +
 .../creating_custom_attributes.html.md.erb  |   64 +
 .../managing_data_regions.html.md.erb   |  222 ++
 .../managing_region_attributes.html.md.erb  |  113 +
 .../new_region_existing_data.html.md.erb|   28 +
 .../data_regions/region_naming.html.md.erb  |   31 +
 .../data_regions/region_shortcuts.html.md.erb   |  115 +
 .../store_retrieve_region_shortcuts.html.md.erb |   77 +
 .../setting_distributed_properties.html.md.erb  |   81 +
 .../the_cache/chapter_overview.html.md.erb  |   48 +
 .../intro_cache_management.html.md.erb  |   96 +
 .../managing_a_client_cache.html.md.erb |   84 +
 .../managing_a_multiuser_cache.html.md.erb  |   66 +
 .../managing_a_peer_server_cache.html.md.erb|   81 +
 .../managing_a_secure_cache.html.md.erb |   67 +
 .../setting_cache_initializer.html.md.erb   |   76 +
 .../setting_cache_properties.html.md.erb|   39 +
 .../configuring/chapter_overview.html.md.erb|   84 +
 .../deploying_application_jars.html.md.erb  |  131 +
 .../cluster_config/export-import.html.md.erb|   56 +
 .../gfsh_config_troubleshooting.html.md.erb |   75 +
 .../gfsh_load_from_shared_dir.html.md.erb   |   44 +
 .../cluster_config/gfsh_persist.html.md.erb |  125 +
 .../cluster_config/gfsh_remote.html.md.erb  |   78 +
 .../persisting_configurations.html.md.erb   |  337 ++
 .../using_member_groups.html.md.erb |   44 +
 .../running/change_file_spec.html.md.erb|   57 +
 .../running/default_file_specs.html.md.erb  |   76 +
 .../deploy_config_files_intro.html.md.erb   |   34 +
 .../running/deploying_config_files.html.md.erb  |   45 +
 .../deploying_config_jar_files.html.md.erb  |   52 +
 .../running/firewall_ports_config.html.md.erb   |   32 +
 .../running/firewalls_connections.html.md.erb   |   35 +
 .../running/firewalls_multisite.html.md.erb |   87 +
 .../running/firewalls_ports.html.md.erb |  246 ++
 .../running/managing_output_files.html.md.erb   |   33 +
 .../running/running_the_cacheserver.html.md.erb |  199 +
 .../running/running_the_locator.html.md.erb |  257 ++
 .../starting_up_shutting_down.html.md.erb   |  146 +
 geode-docs/developing/book_intro.html.md.erb|   74 +
 .../chapter_overview.html.md.erb|   38 +
 .../continuous_querying_whats_next.html.md.erb  |   88 +
 .../how_continuous_querying_works.html.md.erb   |   98 +
 ...implementing_continuous_querying.html.md.erb |  202 ++
 .../PDX_Serialization_Features.html.md.erb  |   40 +
 .../auto_serialization.html.md.erb  |  141 +
 ...ation_with_class_pattern_strings.html.md.erb |   85 +
 .../chapter_overview.html.md.erb|   40 +
 .../data_serialization_options.html.md.erb  |   68 +
 .../extending_the_autoserializer.html.md.erb|  123 +
 .../gemfire_data_serialization.html.md.erb  |   52 +
 .../gemfire_pdx_serialization.html.md.erb   |   64 +
 .../java_serialization.html.md.erb  |   29 +
 .../jsonformatter_pdxinstances.html.md.erb  |   46 +
 .../persist_pdx_metadata_to_disk.html.md.erb|   53 +
 .../program_application_for_pdx.html.md.erb |  107 +
 .../use_pdx_high_level_steps.html.md.erb|   49 +
 .../use_pdx_serializable.html.md.erb|  115 +
 .../use_pdx_serializer.html.md.erb  |  145 +
 .../using_PdxInstanceFactory.html.md.erb|   51 +
 .../using_pdx_region_ent

[24/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cache_data_loader.svg
--
diff --git a/geode-docs/images_svg/cache_data_loader.svg 
b/geode-docs/images_svg/cache_data_loader.svg
new file mode 100644
index 000..0493df6
--- /dev/null
+++ b/geode-docs/images_svg/cache_data_loader.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="113 230 427 229" 
width="427pt" height="229pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:40Zdata-loadersLayer 1databaseMember (M2)Partitioned Region AYCache LoaderMember (M1)Partitioned Region AXCache 
LoaderMember (M3)Partitioned Region AZCache Loader

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cache_data_loader_2.svg
--
diff --git a/geode-docs/images_svg/cache_data_loader_2.svg 
b/geode-docs/images_svg/cache_data_loader_2.svg
new file mode 100644
index 000..7334890
--- /dev/null
+++ b/geode-docs/images_svg/cache_data_loader_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="95 275 427 229" 
width="427pt" height="229pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:41Zdata-loaders-2Layer 
1databaseMember (M2)Distributed Region AXMember (M1)Distributed Region AXCache 
LoaderMember (M3)Distributed Region AX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/client_server_deployment.svg
--
diff --git a/geode-docs/images_svg/client_server_deployment.svg 
b/geode-docs/images_svg/client_server_deployment.svg
new file mode 100644
index 000..dbaff91
--- /dev/null
+++ b/geode-docs/images_svg/client_server_deployment.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="99 332 374 297" 
width="374pt" height="297pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:01ZcsLayer 1filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>ServerClientLocal Cacheconnection 
poolServer 
FarmLocatorsend address 
and load information to locatorCache Clientsrequest server information from 
locator,locator responds with least loaded serversend, receive cache datareceive server eventsCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/client_server_event_dist.svg
--
diff --git a/geode-docs/images_svg/client_server_event_dist.svg 
b/geode-docs/images_svg/client_server_event_dist.svg
new file mode 100644
index 000..e19e46a
--- /dev/null
+++ b/geode-docs/images_svg/client_server_event_dist.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="66 203 487 337" 
width="487pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:51Zcs-event-distribution-2Layer 
1Distributed SystemClie
 nt 1Region Apool-name = ServerPoolServerRegion AXClient 2XRegion Apool-name = ServerPoolpool “ServerPool”(with or without subscriptions 
enabled)pool 
“ServerPool”(with 
subscriptions enabled,interest register in X,receiveValues = 
true)Update/CreateXXsubscription12334

[21/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/custom_partitioned.svg
--
diff --git a/geode-docs/images_svg/custom_partitioned.svg 
b/geode-docs/images_svg/custom_partitioned.svg
new file mode 100644
index 000..e952a5c
--- /dev/null
+++ b/geode-docs/images_svg/custom_partitioned.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="102 228 392 186" 
width="392pt" height="186pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:07Zcustom_partitioningLayer 
1Member (M1)Partition Region AMember (M2)Partition Region 
Acustomer X 
datacustomer Y datacustomer 
P 
datacustomer Q 
data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/developing_overflow.svg
--
diff --git a/geode-docs/images_svg/developing_overflow.svg 
b/geode-docs/images_svg/developing_overflow.svg
new file mode 100644
index 000..f5cf3bb
--- /dev/null
+++ b/geode-docs/images_svg/developing_overflow.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="77 330 414 138" 
width="414pt" height="138pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:42ZoverflowLayer 1MemberXYZXRegion BDisk 
Filesvalues for 
overflow 
entriesoffload overflowupdate/invalidate/destroysatisfy get<
 /svg>

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/developing_persistence.svg
--
diff --git a/geode-docs/images_svg/developing_persistence.svg 
b/geode-docs/images_svg/developing_persistence.svg
new file mode 100644
index 000..e5f3174
--- /dev/null
+++ b/geode-docs/images_svg/developing_persistence.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="113 479 415 133" 
width="415pt" height="133pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:40ZpersistenceLayer 1MemberXYZXYZRegion Apersist values from createDisk Fileskeys and 
values for all entriesupdate/invalidate/destroy

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/developing_persistence_and_overflow.svg
--
diff --git a/geode-docs/images_svg/developing_persistence_and_overflow.svg 
b/geode-docs/images_svg/developing_persistence_and_overflow.svg
new file mode 100644
index 000..c09ce8e
--- /dev/null
+++ b/geode-docs/images_svg/developing_persistence_and_overflow.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="95 330 416 139" 
width="416pt" height="139pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:47Zpersist+overflowLayer 
1GemFire MemberXYZXYZRegion 
CDisk Fileskeys and values for all 
entriespersist values from createupdate/invalidate/destroysatisfy get

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/distributed_how_1.svg
--
diff --git a/geode-docs/images_svg/distributed_how_1.svg 
b/geode-docs/images_svg/distributed_how_1.svg
new file mode 100644
index 000..4c4026a
--- /dev/null
+++ b/geode-docs/images_svg/distributed_how_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="95 293 355 193" 
width="355pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 11:12Zhow_it_works-1Layer 
1 Member (M1)Member (M2)X1ApplicationDistributed Region AXDistributed Region 
AX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/distributed_how_2.svg
--
diff --git a/geode-docs/images_svg/distributed_how_2.svg 
b/geode-docs/images_svg/distributed_how_2.svg
new file mode 100644
index 000..ccc6874
--- /dev/null
+++ b/geode-docs/images_svg/distributed_how_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="131 293 355 193" 
width="355pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-0

[60/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb
--
diff --git a/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb 
b/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb
deleted file mode 100644
index d862004..000
--- a/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb
+++ /dev/null
@@ -1,34 +0,0 @@

-title:  DiskPolicy

-
-
-If the `lru-entries-limit` attribute is greater than zero, the optional 
`disk-policy` attribute determines how over-limit LRU entries are handled. LRU 
entries over the limit are either destroyed by default (`disk-policy` is none ) 
or written to disk (`overflows`).
-
-**Note:**
-If `LruEntriesLimit` is `0`, or `CachingEnabled` is `false`, do not set the 
`disk-policy` attribute. An `IllegalStateException` is thrown if the attribute 
is set.
-
-This declaration causes LRU to overflow to disk:
-
-``` pre
-
-  
-
-```
-
-Overflow requires a persistence manager for cache-to-disk and disk-to-cache 
operations. See 
[PersistenceManager](persistence-manager.html#persistence-manager).
-
-## Overflowing Data to Disk
-
-Region data can be stored to disk using the overflow process to satisfy region 
capacity restrictions without completely destroying the local cache data. The 
storage mechanism uses disk files to hold region entry data. When an entry is 
overflowed, its value is written to disk but its key and entry object remain in 
the cache. This also uses the region attribute 
[DiskPolicy](disk-policy.html#disk-policy).
-
-Overflow allows you to keep the region within a user-specified size in memory 
by relegating the values of least recently used (LRU) entries to disk. Overflow 
essentially uses disk as a swap space for entry values. When the region size 
reaches the specified threshold, entry values are moved from memory to disk, as 
shown in the following figure. If an entry is requested whose value is only on 
disk, the value is copied back into memory, possibly causing the value of a 
different LRU entry to be overflowed to disk.
-
-
-
-Figure: Data Flow Between Overflow Region 
and Disk Files
-
-
-
-In this figure the value of the LRU entry X has been moved to disk to recover 
space in memory. The key for the entry remains in memory. From the distributed 
system perspective, the value on disk is as much a part of the region as the 
data in memory. A `get` performed on region B looks first in memory and then on 
disk as part of the local cache search.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/entries.html.md.erb
--
diff --git a/geode-docs/nativeclient/client-cache/entries.html.md.erb 
b/geode-docs/nativeclient/client-cache/entries.html.md.erb
deleted file mode 100644
index b5799f5..000
--- a/geode-docs/nativeclient/client-cache/entries.html.md.erb
+++ /dev/null
@@ -1,20 +0,0 @@

-title:  Region Entries

-
-Region entries hold cached application data. Entries are automatically managed 
according to region attribute settings.
-
-You can create, update, invalidate, and destroy entries through explicit API 
calls or through operations distributed from other caches.
-
-When the number of entries is very large, a partitioned region can provide the 
required data management capacity if the total size of the data is greater than 
the heap in any single JVM.
-
-When an entry is created, a new object is instantiated in the region 
containing:
-
--   The entry key.
--   The entry value. This is the application data object. The entry value may 
be set to `NULL`, which is the equivalent of an invalid value.
-
-Entry operations invoke callbacks to user-defined application plug-ins. In 
this chapter, the calls that may affect the entry operation itself (by 
providing a value or aborting the operation, for example) are highlighted, but 
all possible interactions are not listed. For details, see [Application 
Plug-Ins](application-plugins.html#application-plugins).
-
-`DateTime` objects must be stored in the cache in UTC, so that times 
correspond between client and server. If you use a date with a different time 
zone, convert it when storing into and retrieving from the cache.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb 
b/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb
deleted file mode 100644
index d154d62..000
--- a/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb
+++ /dev/null
@@ -1,65 +0,0 @@

-title:  Specifying Expiration Attributes

-
-
-Expiration attr

[26/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/getting_started/book_intro.html.md.erb
--
diff --git a/geode-docs/getting_started/book_intro.html.md.erb 
b/geode-docs/getting_started/book_intro.html.md.erb
new file mode 100644
index 000..05c946c
--- /dev/null
+++ b/geode-docs/getting_started/book_intro.html.md.erb
@@ -0,0 +1,23 @@
+---
+title:  Getting Started with Apache Geode
+---
+
+A tutorial demonstrates features, and a main features section describes key 
functionality.
+
+-   **[About Apache Geode](geode_overview.html)**
+
+Apache Geode is a data management platform that provides real-time, 
consistent access to data-intensive applications throughout widely distributed 
cloud architectures.
+
+-   **[Main Features of Apache Geode](product_intro.html)**
+
+This section summarizes the main features and key functionality of Apache 
Geode.
+
+-   **[Prerequisites and Installation 
Instructions](../prereq_and_install.html)**
+
+Each host of Apache Geode 1.0.0-incubating that meets a small set of 
prerequisites may follow the provided installation instructions.
+
+-   **[Apache Geode in 15 Minutes or Less](15_minute_quickstart_gfsh.html)**
+
+Need a quick introduction to Apache Geode? Take this brief tour to try out 
basic features and functionality.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/getting_started/geode_overview.html.md.erb
--
diff --git a/geode-docs/getting_started/geode_overview.html.md.erb 
b/geode-docs/getting_started/geode_overview.html.md.erb
new file mode 100644
index 000..dca502c
--- /dev/null
+++ b/geode-docs/getting_started/geode_overview.html.md.erb
@@ -0,0 +1,20 @@
+---
+title:  About Apache Geode
+---
+
+Apache Geode is a data management platform that provides real-time, consistent 
access to data-intensive applications throughout widely distributed cloud 
architectures.
+
+
+Geode pools memory, CPU, network resources, and optionally local disk across 
multiple processes to manage application objects and behavior. It uses dynamic 
replication and data partitioning techniques to implement high availability, 
improved performance, scalability, and fault tolerance. In addition to being a 
distributed data container, Geode is an in-memory data management system that 
provides reliable asynchronous event notifications and guaranteed message 
delivery.
+
+## Main Concepts and Components
+
+*Caches* are an abstraction that describe a node in a Geode distributed 
system. Application architects can arrange these nodes in peer-to-peer or 
client/server topologies.
+
+Within each cache, you define data *regions*. Data regions are analogous to 
tables in a relational database and manage data in a distributed fashion as 
name/value pairs. A *replicated* region stores identical copies of the data on 
each cache member of a distributed system. A *partitioned* region spreads the 
data among cache members. After the system is configured, client applications 
can access the distributed data in regions without knowledge of the underlying 
system architecture. You can define listeners to create notifications about 
when data has changed, and you can define expiration criteria to delete 
obsolete data in a region.
+
+For large production systems, Geode provides *locators*. Locators provide both 
discovery and load balancing services. You configure clients with a list of 
locator services and the locators maintain a dynamic list of member servers. By 
default, Geode clients and servers use port 40404 to discover each other.
+
+
+
+For more information on product features, see [Main Features of Apache 
Geode](product_intro.html).

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/getting_started/installation/install_standalone.html.md.erb
--
diff --git 
a/geode-docs/getting_started/installation/install_standalone.html.md.erb 
b/geode-docs/getting_started/installation/install_standalone.html.md.erb
new file mode 100644
index 000..22936c7
--- /dev/null
+++ b/geode-docs/getting_started/installation/install_standalone.html.md.erb
@@ -0,0 +1,121 @@
+---
+title:  How to Install
+---
+
+Build from source or use the ZIP or TAR distribution to install Apache Geode 
on every physical and virtual machine that will run Apache Geode.
+
+## Build from Source on Unix
+
+1.  Set the JAVA\_HOME environment variable.
+
+``` pre
+JAVA_HOME=/usr/java/jdk1.8.0_60
+export JAVA_HOME
+```
+
+2.  Download the project source from the Releases page found at 
[http://geode.incubator.apache.org](http://geode.incubator.apache.org/), and 
unpack the source code.
+3.  Within the directory containing the unpacked source code, build without 
tests:
+
+``` pre
+$ ./gradlew build -Dskip

[74/76] [abbrv] incubator-geode git commit: GEODE-1968 - set aside Hibernate Cache docs until feature is mainstreamed.

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/fd8927cb/geode-docs/tools_modules/hibernate_cache/installing_gemfire_and_module.html.md.erb
--
diff --git 
a/geode-docs/tools_modules/hibernate_cache/installing_gemfire_and_module.html.md.erb
 
b/geode-docs/tools_modules/hibernate_cache/installing_gemfire_and_module.html.md.erb
deleted file mode 100644
index a3bc6b9..000
--- 
a/geode-docs/tools_modules/hibernate_cache/installing_gemfire_and_module.html.md.erb
+++ /dev/null
@@ -1,28 +0,0 @@

-title:  Installing the Hibernate Cache Module

-
-
-
-The Hibernate module is included in the Apache Geode installation package.
-
-1.  If you have not done so, download and install 
[Hibernate](http://www.hibernate.org/). Apache Geode supports Hibernate 3.3 and 
later (up to version 3.6.10) for use with the Hibernate Cache module. Apache 
Geode does not currently support Hibernate 4.x for use with the Hibernate Cache 
module.
-2.  The Hibernate module is included in the Apache Geode installation package. 
You can find the module in the `/tools/Modules` directory, in a 
zip file that includes the version and the string `Hibernate`. `` 
is the location where you installed Geode.
-3.  Make sure that `/lib/geode-dependencies.jar` is part of the 
CLASSPATH when you run Hibernate. Alternatively, you can place the 
`geode-dependencies.jar` in a location that is accessible to your Hibernate 
application.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/fd8927cb/geode-docs/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb
--
diff --git 
a/geode-docs/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb 
b/geode-docs/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb
deleted file mode 100644
index 8d00c34..000
--- a/geode-docs/tools_modules/hibernate_cache/setting_up_the_module.html.md.erb
+++ /dev/null
@@ -1,110 +0,0 @@

-title:  Setting Up the Geode Hibernate Cache Module

-
-
-
-Edit the `hibernate.cfg.xml` file to use the Hibernate Cache module.
-
-1.  **Turn on L2 Cache**
-
-In the `hibernate.cfg.xml` file, turn on the L2 cache and identify the 
Geode locator(s):
-
-``` pre
-true
-host1[port1],host2[port2]
-```
-
-Change `host1` and `host2 ` to the hostnames (or IP addresses) for each of 
the locators; `port1` and `port2 `are the ports for each of 
the locators.
-
-2.  **Set Region Factory or Cache Provider**
-
-Associate the region factory class with GemFireRegionFactory:
-
-``` pre
-
-  org.apache.geode.modules.hibernate.GemFireRegionFactory
- 
-```
-
-3.  **Determine Cache Usage Mode**
-
-Determine the cache usage mode for the entities in each region. There are 
four types of usage modes:
-
-| Mode   | Description 

|
-
||-|
-| `read-only`| This mode is used when you do not plan on 
modifying the data already stored in your persistent storage.   
  |
-| `read-write`   | This mode is used when you plan to both read 
from and write to your data.
   |
-| `nonstrict-read-write` | This mode is a special read/write mode that has 
faster write performance; however, only use this mode if no more than one 
client will update content at a time. |
-| `transactional`| This mode allows for transaction-based data 
access. 
|
-
-4.  **Set Cache Usage Mode**
-
-The usage mode can either be set using the hibernate-mapping file or 
through Java annotations.
--   To set the mode with the hibernate-mapping file, refer to this example:
-
-``` pre
-
-
-  
-
-...
-  
-
- 
-```
-
-In this example, `PACKAGE` is the name of the entity package, 
`ENTITY_NAME` is the name of your entity, and `USAGE_MODE` is the chosen usage 
mode from the table given above. Refer to the [Hibernate 
documentation](http://hibernate.org/docs) for further information.
--   To set the mode using annotations, your class definition should look 
something like this example which specifies the `read-only` usage mode:
-
-``` pre
-import org.hibernate.annotations.Cache; 
-import org.hibernate.annot

[72/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
--
diff --git 
a/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb 
b/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
index 76d5066..c56eaa7 100644
--- a/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
+++ b/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
@@ -2,6 +2,23 @@
 title:  Options for Configuring the Cache and Data Regions
 ---
 
+
+
 To populate your Apache Geode cache and fine-tune its storage and distribution 
behavior, you need to define cached data regions and provide custom 
configuration for the cache and regions.
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/configuring/chapter_overview.html.md.erb
--
diff --git a/geode-docs/configuring/chapter_overview.html.md.erb 
b/geode-docs/configuring/chapter_overview.html.md.erb
index 8026e72..295444c 100644
--- a/geode-docs/configuring/chapter_overview.html.md.erb
+++ b/geode-docs/configuring/chapter_overview.html.md.erb
@@ -2,6 +2,23 @@
 title:  Configuring and Running a Cluster
 ---
 
+
+
 You use the `gfsh` command-line utility to configure your Apache Geode cluster 
(also called a "distributed system"). The cluster configuration service 
persists the cluster configurations and distributes the configurations to 
members of the cluster. There are also several additional ways to configure a 
cluster.
 
 You use `gfsh` to configure regions, disk stores, members, and other Geode 
objects. You also use `gfsh` to start and stop locators, servers, and Geode 
monitoring tools. As you execute these commands, the cluster configuration 
service persists the configuration. When new members join the cluster, the 
service distributes the configuration to the new members.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/configuring/cluster_config/deploying_application_jars.html.md.erb
--
diff --git 
a/geode-docs/configuring/cluster_config/deploying_application_jars.html.md.erb 
b/geode-docs/configuring/cluster_config/deploying_application_jars.html.md.erb
index 08eb1d5..1e43753 100644
--- 
a/geode-docs/configuring/cluster_config/deploying_application_jars.html.md.erb
+++ 
b/geode-docs/configuring/cluster_config/deploying_application_jars.html.md.erb
@@ -2,6 +2,23 @@
 title:  Deploying Application JARs to Apache Geode Members
 ---
 
+
+
 You can dynamically deploy your application JAR files to specific members or 
to all members in your distributed system. Geode automatically keeps track of 
JAR file versions; autoloads the deployed JAR files to the CLASSPATH; and 
auto-registers any functions that the JAR contains.
 
 To deploy and undeploy application JAR files in Apache Geode, use the `gfsh` 
`deploy` or `undeploy` command. You can deploy a single JAR or multiple JARs 
(by either specifying the JAR filenames or by specifying a directory that 
contains the JAR files), and you can also target the deployment to a member 
group or multiple member group. For example, after connecting to the 
distributed system where you want to deploy the JARs, you could type at the 
`gfsh` prompt:

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/configuring/cluster_config/export-import.html.md.erb
--
diff --git a/geode-docs/configuring/cluster_config/export-import.html.md.erb 
b/geode-docs/configuring/cluster_config/export-import.html.md.erb
index e730c5b..5a89f51 100644
--- a/geode-docs/configuring/cluster_config/export-import.html.md.erb
+++ b/geode-docs/configuring/cluster_config/export-import.html.md.erb
@@ -2,6 +2,23 @@
 title:  Exporting and Importing Cluster Configurations
 ---
 
+
+
 The cluster configuration service exports and imports configurations created 
using `gfsh` for an entire Apache Geode cluster.
 
 The cluster configuration service saves the cluster configuration as you 
create a regions, disk-stores and other objects using `gfsh` commands. You can 
export this configuration as well as any jar files that contain application 
files to a zip file and then import this configuration to create a new cluster.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
--
diff --git 
a/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb 
b/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
index 51f89b0..638ff1d 100644
--- 
a/geode-docs/configuring/cluster_config/gfsh

[39/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/transactions/jca_adapter_example.html.md.erb
--
diff --git a/developing/transactions/jca_adapter_example.html.md.erb 
b/developing/transactions/jca_adapter_example.html.md.erb
deleted file mode 100644
index 1e562cd..000
--- a/developing/transactions/jca_adapter_example.html.md.erb
+++ /dev/null
@@ -1,34 +0,0 @@

-title:  JCA Resource Adapter Example

-
-This example shows how to use the JCA Resource Adapter in Geode .
-
-``` pre
-Hashtable env = new Hashtable();
-env.put(Context.INITIAL_CONTEXT_FACTORY, 
“weblogic.jndi.WLInitialContextFactory”);
-env.put(Context.PROVIDER_URL, “t3://localhost:7001”);
-Context ctx = new InitialContext(env);
-UserTransaction utx = (UserTransaction) 
ctx.lookup(“javax.transaction.UserTransaction”);
-utx.begin();
-  // the XA Resource
-javax.sql.DataSource ds = (DataSource) ctx.lookup(“derby”);
-javax.sql.Connection derbyConn = ds.getConnection();
-Statement stmt = conn.createStatement();
-stmt.executeUpdate(“insert into test values(2,4) “);
- // do ConnectionFactory lookup
-GFConnectionFactory cf = (GFConnectionFactory) ctx.lookup(“gfe/jca”);
-
- // Obtaining the connection begins the LocalTransaction.
- // If this is absent, operations will not be part of any transaction.
-GFConnection conn = cf.getConnection();
-
-testRegion.put(“foo”, “bar-”);
-utx.commit();
-
- // the connection can also be closed within the transaction
-derbyConn.close();
-conn.close();
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/transactions/monitor_troubleshoot_transactions.html.md.erb
--
diff --git 
a/developing/transactions/monitor_troubleshoot_transactions.html.md.erb 
b/developing/transactions/monitor_troubleshoot_transactions.html.md.erb
deleted file mode 100644
index 6cb1b6c..000
--- a/developing/transactions/monitor_troubleshoot_transactions.html.md.erb
+++ /dev/null
@@ -1,39 +0,0 @@

-title:  Monitoring and Troubleshooting Transactions

-
-This topic covers errors that may occur when running transactions in Geode.
-
-
-Unlike database transactions, Geode does not write a transaction log to disk. 
To get the full details about committed operations, use a transaction listener 
to monitor the transaction events and their contained cache events for each of 
your transactions.
-
-## Statistics on Cache Transactions
-
-During the operation of Geode cache transactions, if statistics are enabled, 
transaction-related statistics are calculated and accessible from the 
CachePerfStats statistic resource. Because the transaction’s data scope is 
the cache, these statistics are collected on a per-cache basis.
-
-## Commit
-
-In a failed commit, the exception lists the first conflict that caused the 
failure. Other conflicts can exist, but are not reported.
-
-## Capacity Limits
-
-A transaction can create data beyond the capacity limit set in the region’s 
eviction attributes. The capacity limit does not take effect until commit time. 
Then, any required eviction action takes place as part of the commit.
-
-## Interaction with the Resource Manager
-
-The Geode resource manager, which controls overall heap use, either allows all 
transactional operations or blocks the entire transaction. If a cache reaches 
the critical threshold in the middle of a commit, the commit is allowed to 
finish before the manager starts blocking operations.
-
-## Transaction Exceptions
-
-The following sections list possible transaction exceptions.
-
-**Exceptions Indicating Transaction Failure**
-
--   **`TransactionDataNodeHasDepartedException`**. This exception means the 
transaction host has departed unexpectedly. Clients and members that run 
transactions but are not a transaction host can get this exception. You can 
avoid this by working to ensure your transaction hosts are stable and remain 
running when transactions are in progress.
--   **`TransactionDataNotColocatedException`**. You will get this error if you 
try to run a transaction on data that is not all located in the same member. 
Partition your data so that a single member contains all data that will be 
accessed as part of a single transaction. See [Transactions and Partitioned 
Regions](cache_transactions_by_region_type.html#concept_ysk_xj1_wk) and 
[Understanding Custom Partitioning and Data 
Colocation](../partitioned_regions/custom_partitioning_and_data_colocation.html#custom_partitioning_and_data_colocation).
--   **`TransactionDataRebalancedException`**. You get this error if your 
transactional data is moved to another member for rebalancing during the 
transaction. Manage your partitioned region data to avoid rebalancing during a 
transaction. See [Rebalancing Partitioned Region 
Data](../partitioned_regions/rebalancing

[25/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/JMX_Architecture.svg
--
diff --git a/geode-docs/images_svg/JMX_Architecture.svg 
b/geode-docs/images_svg/JMX_Architecture.svg
new file mode 100644
index 000..f60c097
--- /dev/null
+++ b/geode-docs/images_svg/JMX_Architecture.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="106 331 380 360" 
width="380pt" height="30pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 00:09Zjmx 
architectureLayer 1Management and 
Monitoring ToolsJMX Manager Node Distributed SystemOther JMX Clients (JConsole, jvisualvm)
 Managed NodeManaged NodeCMBean ServerDAMBean ServerBMBean ServerY+XAManagerMBeanx="1.9985352" y="9" textLength="6.0029297">Btransform="translate(139 442.875)" fill="black">font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x=".75927734" y="6" textLength="45.023438">Proxied Mbeans font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x="3.0942383" y="13" textLength="40.353516">from Managed font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x="13.765625" y="20" textLength="17.34375">Nodesmarker-end="url(#FilledArrow_Marker_2)" stroke="black" stroke-linecap="round" 
 >stroke-linejoin="round" stroke-width=".23998"/>d="M 159.66 546.75 L 245.34 546.75 C 249.01822 546.75 252 549.73178 252 
 >553.41 L 252 558.09 C 252 5
 61.7682 249.01822 564.75 245.34 564.75 L 159.66 564.75 C 155.98178 564.75 153 
561.7682 153 558.09 L 153 553.41 C 153 549.73178 155.98178 546.75 159.66 546.75 
Z" fill="url(#Obj_Gradient_c)"/>Management ServiceManagement 
ServiceRMI 
ConnectorManagement ServiceCDgfshMemberMBeanMemberMBeanLocal 
MBeansLocal 
MBeansLocal MBeansZYAggregate MBeanMemberMBeanPulseOther JMX Clients (JConsole, jvisualvm)Local view of 
managed node 
onlyRMI 
ConnectorView of 
remote managed node

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/MBeans.svg
--
diff --git a/geode-docs/images_svg/MBeans.svg b/geode-docs/images_svg/MBeans.svg
new file mode 100644
index 000..cdfcf6e
--- /dev/null
+++ b/geode-docs/images_svg/MBeans.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="54 72 504 450" 
width="42pc" height="450pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 23:57ZmbeanLayer 1DistributedLockServiceMXBeanLocatorMXBeanMemberMXBeanManagerMXBeanDistributedRegionMXBeanDistributedSystemMXBeanJMX Manager NodeRegionMXBeanLockServiceMXBeanManaged NodeDiskStoreMXBean110..N0..10..N10..N0..N0..NAsyncEventQueueMXBeanCacheServerMXBean10..N

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/async_system_queue_conflation.svg
--
diff --git a/geode-docs/images_svg/async_system_queue_conflation.svg 
b/geode-docs/images_svg/async_system_queue_conflation.svg
new file mode 100644
index 000..fcc8635
--- /dev/null
+++ b/geode-docs/images_svg/async_system_queue_conflation.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="61 349 454 346" 
width="454pt" height="346pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 08:59ZconflationLayer 1Initial producer queue 
w
 ith conflationentry createKey Bentry updateKey AValue QV1to consumerentry updateKey AValue V2Add entry update to 
queue...entry 
createKey 
Bentry updateKey AValue 
V1to consumerQueue after conflationentry updateKey AValue 
V2entry 
createKey 
Bto consumer

[23/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/client_server_message_tracking.svg
--
diff --git a/geode-docs/images_svg/client_server_message_tracking.svg 
b/geode-docs/images_svg/client_server_message_tracking.svg
new file mode 100644
index 000..69b0a55
--- /dev/null
+++ b/geode-docs/images_svg/client_server_message_tracking.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="114 214 391 346" 
width="391pt" height="346pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:54Ztune-cs-messagingLayer 
1ServerBClient3A12A11B2A10A9B1send message A-10subscription queuethreadop #ServerBClient3A12A11B2A10B1subscription queuethreadop #Stage 1Stage 
2

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cluster-group-config.svg
--
diff --git a/geode-docs/images_svg/cluster-group-config.svg 
b/geode-docs/images_svg/cluster-group-config.svg
new file mode 100644
index 000..7977987
--- /dev/null
+++ b/geode-docs/images_svg/cluster-group-config.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="86 108 489 320" 
width="489pt" height="320pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 08:52Z12 ColumnsLayer 1ClusterConfigurationfor 
entire clustercluster.xmlcluster.propertiesjarjarCluster 
Configurationfor group1group1.xmlgroup1.propertiesjarjarCluster Configurationfor group2group2.xmlgroup2.propertiesjarjar

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cluster_config_overview.svg
--
diff --git a/geode-docs/images_svg/cluster_config_overview.svg 
b/geode-docs/images_svg/cluster_config_overview.svg
new file mode 100644
index 000..93470e6
--- /dev/null
+++ b/geode-docs/images_svg/cluster_config_overview.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="23 15 430 469" 
width="430pt" height="469pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-03-24 21:39Z12 ColumnsLayer 1Locator(s)ser
 ver34. New members request 
 the configuration from a 
locator.5. Locator 
distributes the configuration (including regions, disk-stores, jar 
files) to new servers joining the cluster.server2start 
locatorstart server1create disk-storecreate indexcreate 
regiondeploy...1. Developer/Administrator executes gfsh commands to 
configure the cluster.
 start 
server --name=server2start server 
--name=server3start server 
--name=server43. Developer/Administrator executes gfsh commands to add new members to the cluster.server4Layer 
2server12. gfsh saves the cluster configuration 
on the locator(s). Existing 
server(s) using cluster 
configuration service are 
configured.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/colocated_partitioned_regions.svg
--
diff --git a/geode-docs/images_svg/colocated_partitioned_regions.svg 
b/geode-docs/images_svg/colocated_partitioned_regions.svg
new file mode 100644
index 000..1cb609e
--- /dev/null
+++ b/geode-docs/images_svg/colocated_partitioned_regions.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="90 285 383 221" 
width="383pt" height="221pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:09Zregion_data_colocationLayer 
1Member (M1)Partition Region AMember (M2)Partition Region 
Acustomer X datacustomer P dataPartition Region 
BPartition Region 
Bcustomer X 
datacustomer 
P 
data

[27/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/transactions/how_cache_transactions_work.html.md.erb
--
diff --git 
a/geode-docs/developing/transactions/how_cache_transactions_work.html.md.erb 
b/geode-docs/developing/transactions/how_cache_transactions_work.html.md.erb
new file mode 100644
index 000..fb914be
--- /dev/null
+++ b/geode-docs/developing/transactions/how_cache_transactions_work.html.md.erb
@@ -0,0 +1,56 @@
+---
+title: How Geode Cache Transactions Work
+---
+
+
+
+This section provides an explanation of how transactions work on Geode caches.
+
+All the regions in a Geode member cache can participate in a transaction. A 
Java application can operate on the cache using multiple transactions. A 
transaction is associated with only one thread, and a thread can operate on 
only one transaction at a time. Child threads do not inherit existing 
transactions.
+
+-   **[Transaction 
View](../../developing/transactions/how_cache_transactions_work.html#concept_hls_1j1_wk)**
+
+-   **[Committing 
Transactions](../../developing/transactions/how_cache_transactions_work.html#concept_sbj_lj1_wk)**
+
+-   **[Transactions by Region 
Type](../../developing/transactions/cache_transactions_by_region_type.html#topic_nlq_sk1_wk)**
+
+-   **[Client 
Transactions](../../developing/transactions/client_server_transactions.html)**
+
+-   **[Comparing Transactional and Non-Transactional 
Operations](../../developing/transactions/transactional_and_nontransactional_ops.html#transactional_and_nontransactional_ops)**
+
+-   **[Geode Cache Transaction 
Semantics](../../developing/transactions/transaction_semantics.html)**
+
+## Transaction View
+
+A transaction is isolated from changes made concurrently to the cache. Each 
transaction has its own private view of the cache, including the entries it has 
read and the changes it has made. The first time the transaction touches an 
entry in the cache, either to read or write, it produces a snapshot of that 
entry’s state in the transaction’s view. The transaction maintains its 
current view of the entry, which reflects only the changes made within the 
transaction. The transaction remembers the entry’s original state and uses it 
at commit time to discover write conflicts.
+
+
+
+## Committing Transactions
+
+When a commit succeeds, the changes recorded in the transaction view are 
merged into the cache. If the commit fails or the transaction is rolled back, 
all of its changes are dropped.
+
+When a transaction is committed, the transaction management system uses a 
two-phase commit protocol:
+
+1.  Reserves all the entries involved in the transaction from changes by any 
other transactional thread. For distributed regions, it reserves the entries in 
the entire distributed system. For partitioned regions, it reserves them on the 
data store, where the transaction is running.
+2.  Checks the cache for conflicts on affected keys, to make sure all entries 
are still in the same state they were in when this transaction first accessed 
them.
+3.  If any conflict is detected, the manager rolls back the transaction.
+4.  If no conflict is detected, the manager:
+1.  Calls the `TransactionWriter` in the member where the transaction is 
running. This allows the system to write through transactional updates to an 
external data source.
+2.  Updates the local cache and distributes the updates to the other 
members holding the data. Cache listeners are called for these updates, in each 
cache where the changes are made, the same as for non-transactional operations.
+3.  Calls the `TransactionListener`s in the member where the transaction 
is running.
+
+5.  Releases the transaction reservations on the entries.
+
+The manager updates the local cache and distributes the updates to other 
members in a non-atomic way.
+
+-   If other threads read the keys the transaction is modifying, they may see 
some in their pre-transaction state and some in their post-transaction state.
+-   If other, non-transactional sources update the keys the transaction is 
modifying, the changes may intermingle with this transaction’s changes. The 
other sources can include distributions from remote members, loading 
activities, and other direct cache modification calls from the same member. 
When this happens, after your commit finishes, the cache state may not be what 
you expected.
+
+If the transaction fails to complete any of the steps, a 
CommitConflictException is thrown to the calling application.
+
+Once the members involved in the transaction have been asked to commit, the 
transaction completes even if one of the participating members were to leave 
the system during the commit. The transaction completes successfully so long as 
all remaining members are in agreement.
+
+Each member participating in the transaction maintains a membership listener 
on the transaction coordin

[73/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

GEODE-1952: Add Apache license to all geode-docs erb files


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/6bea8204
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/6bea8204
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/6bea8204

Branch: refs/heads/feature/GEODE-1952-2
Commit: 6bea8204c24c0f0b6424e97f491d787e016ab8fc
Parents: e0f5203
Author: Karen Miller 
Authored: Wed Oct 5 15:49:58 2016 -0700
Committer: Karen Miller 
Committed: Wed Oct 5 15:49:58 2016 -0700

--
 geode-docs/about_geode.html.md.erb | 17 +
 geode-docs/basic_config/book_intro.html.md.erb | 17 +
 .../config_concepts/chapter_overview.html.md.erb   | 17 +
 ...ributed_system_member_configuration.html.md.erb | 17 +
 .../config_concepts/local_vs_remote.html.md.erb| 17 +
 .../chapter_overview.html.md.erb   | 17 +
 .../managing_data_entries.html.md.erb  | 17 +
 .../using_custom_classes.html.md.erb   | 17 +
 .../data_regions/chapter_overview.html.md.erb  | 17 +
 .../create_a_region_with_API.html.md.erb   | 17 +
 .../create_a_region_with_cacheXML.html.md.erb  | 17 +
 .../create_a_region_with_gfsh.html.md.erb  | 17 +
 .../creating_custom_attributes.html.md.erb | 17 +
 .../data_regions/managing_data_regions.html.md.erb | 17 +
 .../managing_region_attributes.html.md.erb | 17 +
 .../new_region_existing_data.html.md.erb   | 17 +
 .../data_regions/region_naming.html.md.erb | 17 +
 .../data_regions/region_shortcuts.html.md.erb  | 17 +
 .../store_retrieve_region_shortcuts.html.md.erb| 17 +
 .../setting_distributed_properties.html.md.erb | 17 +
 .../the_cache/chapter_overview.html.md.erb | 17 +
 .../the_cache/intro_cache_management.html.md.erb   | 17 +
 .../the_cache/managing_a_client_cache.html.md.erb  | 17 +
 .../managing_a_multiuser_cache.html.md.erb | 17 +
 .../managing_a_peer_server_cache.html.md.erb   | 17 +
 .../the_cache/managing_a_secure_cache.html.md.erb  | 17 +
 .../setting_cache_initializer.html.md.erb  | 17 +
 .../the_cache/setting_cache_properties.html.md.erb | 17 +
 .../configuring/chapter_overview.html.md.erb   | 17 +
 .../deploying_application_jars.html.md.erb | 17 +
 .../cluster_config/export-import.html.md.erb   | 17 +
 .../gfsh_config_troubleshooting.html.md.erb| 17 +
 .../gfsh_load_from_shared_dir.html.md.erb  | 17 +
 .../cluster_config/gfsh_persist.html.md.erb| 17 +
 .../cluster_config/gfsh_remote.html.md.erb | 17 +
 .../persisting_configurations.html.md.erb  | 17 +
 .../cluster_config/using_member_groups.html.md.erb | 17 +
 .../running/change_file_spec.html.md.erb   | 17 +
 .../running/default_file_specs.html.md.erb | 17 +
 .../running/deploy_config_files_intro.html.md.erb  | 17 +
 .../running/deploying_config_files.html.md.erb | 17 +
 .../running/deploying_config_jar_files.html.md.erb | 17 +
 .../running/firewall_ports_config.html.md.erb  | 17 +
 .../running/firewalls_connections.html.md.erb  | 17 +
 .../running/firewalls_multisite.html.md.erb| 17 +
 .../running/firewalls_ports.html.md.erb| 17 +
 .../running/managing_output_files.html.md.erb  | 17 +
 .../running/running_the_cacheserver.html.md.erb| 17 +
 .../running/running_the_locator.html.md.erb| 17 +
 .../running/starting_up_shutting_down.html.md.erb  | 17 +
 geode-docs/developing/book_intro.html.md.erb   | 17 +
 .../chapter_overview.html.md.erb   | 17 +
 .../continuous_querying_whats_next.html.md.erb | 17 +
 .../how_continuous_querying_works.html.md.erb  | 17 +
 .../implementing_continuous_querying.html.md.erb   | 17 +
 .../PDX_Serialization_Features.html.md.erb | 17 +
 .../auto_serialization.html.md.erb | 17 +
 ...lization_with_class_pattern_strings.html.md.erb | 17 +

[34/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
--
diff --git 
a/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
 
b/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
new file mode 100644
index 000..7e4c551
--- /dev/null
+++ 
b/geode-docs/developing/distributed_regions/how_region_versioning_works.html.md.erb
@@ -0,0 +1,110 @@
+---
+title: Consistency Checking by Region Type
+---
+
+
+
+Geode performs different consistency checks depending on the type of region 
you have configured.
+
+## Partitioned Region Consistency
+
+For a partitioned region, Geode maintains consistency by routing all updates 
on a given key to the Geode member that holds the primary copy of that key. 
That member holds a lock on the key while distributing updates to other members 
that host a copy of the key. Because all updates to a partitioned region are 
serialized on the primary Geode member, all members apply the updates in the 
same order and consistency is maintained at all times. See [Understanding 
Partitioning](../partitioned_regions/how_partitioning_works.html).
+
+## Replicated Region Consistency
+
+For a replicated region, any member that hosts the region can update a key and 
distribute that update to other members without locking the key. It is possible 
that two members can update the same key at the same time (a concurrent 
update). It is also possible that, due to network latency, an update in one 
member is distributed to other members at a later time, after those members 
have already applied more recent updates to the key (an out-of-order update). 
By default, Geode members perform conflict checking before applying region 
updates in order to detect and consistently resolve concurrent and out-of-order 
updates. Conflict checking ensures that region data eventually becomes 
consistent on all members that host the region. The conflict checking behavior 
for replicated regions is summarized as follows:
+
+-   If two members update the same key at the same time, conflict checking 
ensures that all members eventually apply the same value, which is the value of 
one of the two concurrent updates.
+-   If a member receives an out-of-order update (an update that is received 
after one or more recent updates were applied), conflict checking ensures that 
the out-of-order update is discarded and not applied to the cache.
+
+[How Consistency Checking Works for Replicated 
Regions](#topic_C5B74CCDD909403C815639339AA03758) and [How Destroy and Clear 
Operations Are Resolved](#topic_321B05044B6641FCAEFABBF5066BD399) provide more 
details about how Geode performs conflict checking when applying an update.
+
+## Non-Replicated Regions and Client Cache Consistency
+
+When a member receives an update for an entry in a non-replicated region and 
applies an update, it performs conflict checking in the same way as for a 
replicated region. However, if the member initiates an operation on an entry 
that is not present in the region, it first passes that operation to a member 
that hosts a replicate. The member that hosts the replica generates and 
provides the version information necessary for subsequent conflict checking. 
See [How Consistency Checking Works for Replicated 
Regions](#topic_C5B74CCDD909403C815639339AA03758).
+
+Client caches also perform consistency checking in the same way when they 
receive an update for a region entry. However, all region operations that 
originate in the client cache are first passed onto an available Geode server, 
which generates the version information necessary for subsequent conflict 
checking.
+
+## Configuring Consistency Checking
+
+Geode enables consistency checking by default. You cannot disable consistency 
checking for persistent regions. For all other regions, you can explicitly 
enable or disable consistency checking by setting the 
`concurrency-checks-enabled` region attribute in `cache.xml` to "true" or 
"false."
+
+All Geode members that host a region must use the same 
`concurrency-checks-enabled` setting for that region.
+
+A client cache can disable consistency checking for a region even if server 
caches enable consistency checking for the same region. This configuration 
ensures that the client sees all events for the region, but it does not prevent 
the client cache region from becoming out-of-sync with the server cache.
+
+See 
[](../../reference/topics/cache_xml.html#region-attributes).
+
+**Note:**
+Regions that do not enable consistency checking remain subject to race 
conditions. Concurrent updates may result in one or more members having 
different values for the same key. Network latency can result in older updates 
being applied to a key after more recent updates have occurred.
+
+## Overhead for Consistency Chec

[31/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb 
b/geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb
new file mode 100644
index 000..56e65e1
--- /dev/null
+++ b/geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb
@@ -0,0 +1,43 @@
+---
+title:  Partitioned Regions
+---
+
+In addition to basic region management, partitioned regions include options 
for high availability, data location control, and data balancing across the 
distributed system.
+
+-   **[Understanding 
Partitioning](../../developing/partitioned_regions/how_partitioning_works.html)**
+
+To use partitioned regions, you should understand how they work and your 
options for managing them.
+
+-   **[Configuring Partitioned 
Regions](../../developing/partitioned_regions/managing_partitioned_regions.html)**
+
+Plan the configuration and ongoing management of your partitioned region 
for host and accessor members and configure the regions for startup.
+
+-   **[Configuring the Number of Buckets for a Partitioned 
Region](../../developing/partitioned_regions/configuring_bucket_for_pr.html)**
+
+Decide how many buckets to assign to your partitioned region and set the 
configuration accordingly.
+
+-   **[Custom-Partitioning and Colocating 
Data](../../developing/partitioned_regions/overview_custom_partitioning_and_data_colocation.html)**
+
+You can customize how Apache Geode groups your partitioned region data 
with custom partitioning and data colocation.
+
+-   **[Configuring High Availability for Partitioned 
Regions](../../developing/partitioned_regions/overview_how_pr_ha_works.html)**
+
+By default, Apache Geode stores only a single copy of your partitioned 
region data among the region's data stores. You can configure Geode to maintain 
redundant copies of your partitioned region data for high availability.
+
+-   **[Configuring Single-Hop Client Access to Server-Partitioned 
Regions](../../developing/partitioned_regions/overview_how_pr_single_hop_works.html)**
+
+Single-hop data access enables the client pool to track where a 
partitioned region’s data is hosted in the servers. To access a single entry, 
the client directly contacts the server that hosts the key, in a single hop.
+
+-   **[Rebalancing Partitioned Region 
Data](../../developing/partitioned_regions/rebalancing_pr_data.html)**
+
+In a distributed system with minimal contention to the concurrent threads 
reading or updating from the members, you can use rebalancing to dynamically 
increase or decrease your data and processing capacity.
+
+-   **[Checking Redundancy in Partitioned 
Regions](../../developing/partitioned_regions/checking_region_redundancy.html)**
+
+Under some circumstances, it can be important to verify that your 
partitioned region data is redundant and that upon member restart, redundancy 
has been recovered properly across partitioned region members.
+
+-   **[Moving Partitioned Region Data to Another 
Member](../../developing/partitioned_regions/moving_partitioned_data.html)**
+
+You can use the `PartitionRegionHelper` `moveBucketByKey` and `moveData` 
methods to explicitly move partitioned region data from one member to another.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
 
b/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
new file mode 100644
index 000..a35de98
--- /dev/null
+++ 
b/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
@@ -0,0 +1,38 @@
+---
+title:  Checking Redundancy in Partitioned Regions
+---
+
+Under some circumstances, it can be important to verify that your partitioned 
region data is redundant and that upon member restart, redundancy has been 
recovered properly across partitioned region members.
+
+You can verify partitioned region redundancy by making sure that the 
`numBucketsWithoutRedundancy` statistic is **zero** for all your partitioned 
regions. To check this statistic, use the following `gfsh` command:
+
+``` pre
+gfsh>show metrics --categories=partition --region=region_name
+```
+
+For example:
+
+``` pre
+gfsh>show metrics --categories=partition --region=posts
+
+Cluster-wide Region Metrics
+- | --- | -
+partition | putLocalRate| 0
+  | putRemoteRate   | 0
+  | putRemoteLatency| 0
+  | putRemoteAvgLatency | 0
+  | bucketCount | 1
+ 

[22/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cs_connection_pool.svg
--
diff --git a/geode-docs/images_svg/cs_connection_pool.svg 
b/geode-docs/images_svg/cs_connection_pool.svg
new file mode 100644
index 000..dcba00d
--- /dev/null
+++ b/geode-docs/images_svg/cs_connection_pool.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="103 268 246 268" 
width="246pt" height="268pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:14Zconnection_poolLayer 
1ServerClientconnection 
poolclient threads use pool connection for cache 
operationsrequests fromother clientsCache Datalistener for 
clientsclient requests,server responsesrequests toother servers

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cs_locator_discovery.svg
--
diff --git a/geode-docs/images_svg/cs_locator_discovery.svg 
b/geode-docs/images_svg/cs_locator_discovery.svg
new file mode 100644
index 000..dd55275
--- /dev/null
+++ b/geode-docs/images_svg/cs_locator_discovery.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="122 365 391 242" 
width="391pt" height="242pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-06 22:29Zp2p and cs with locatorsLayer 
1Client/Server Discovery Using LocatorsClientLocal CacheClientLocal CachePeerPeerLocatorPeerLocatorCache DataCache DataCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cs_subscriptions.svg
--
diff --git a/geode-docs/images_svg/cs_subscriptions.svg 
b/geode-docs/images_svg/cs_subscriptions.svg
new file mode 100644
index 000..9764499
--- /dev/null
+++ b/geode-docs/images_svg/cs_subscriptions.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="229 275 261 257" 
width="261pt" height="257pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 09:18ZsubscriptionsLayer 
1ServerClientstroke-width=".7203"/>fill="black">fill="black" x="48.03833" y="9" textLength="63.04834">connection 
 >poolused for updates to cache andfor sending events to 
listenersevents to 
other 
clientsCache eventssubscription queuesconnections to 
clientssubscriptionconnection

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cs_topology.svg
--
diff --git a/geode-docs/images_svg/cs_topology.svg 
b/geode-docs/images_svg/cs_topology.svg
new file mode 100644
index 000..e14dd6e
--- /dev/null
+++ b/geode-docs/images_svg/cs_topology.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd";>
+http://www.w3.org/2000/svg"; 
xmlns:xl="http://www.w3.org/1999/xlink"; version="1.1" viewBox="131 238 355 201" 
width="355pt" height="201pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/";> Produced by OmniGraffle 
6.0.5 2015-04-07 10:03ZcsLayer 1ServerServerServerApplication 
ProcessClientLocal Cacheconnection poolCache DataCache DataCache Data

[07/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/management/list_of_mbeans_full.html.md.erb
--
diff --git a/geode-docs/managing/management/list_of_mbeans_full.html.md.erb 
b/geode-docs/managing/management/list_of_mbeans_full.html.md.erb
new file mode 100644
index 000..74fb2bd
--- /dev/null
+++ b/geode-docs/managing/management/list_of_mbeans_full.html.md.erb
@@ -0,0 +1,210 @@
+---
+title: JMX Manager MBeans
+---
+
+
+
+This section describes the MBeans that are available on the JMX Manager node.
+
+The JMX Manager node includes all local beans listed under [Managed Node 
MBeans](list_of_mbeans_full.html#topic_48194A5BDF3F40F68E95A114DD702413) and 
the following beans that are available only on the JMX Manager node:
+
+-   
[ManagerMXBean](list_of_mbeans_full.html#topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_7B878B450B994514BDFE96571F0D3827)
+-   
[DistributedSystemMXBean](list_of_mbeans_full.html#topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_4D7A4C82DD974BB5A5E52B34A6D888B4)
+-   
[DistributedRegionMXBean](list_of_mbeans_full.html#topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_48384B091AB846E591F22EEA2770DD36)
+-   
[DistributedLockServiceMXBean](list_of_mbeans_full.html#topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_9E004D8AA3D24647A5C19CAA1879F0A4)
+
+## ManagerMXBean
+
+Represents the Geode Management layer for the hosting member. Controls the 
scope of management. This MBean provides `start` and `stop` methods to turn a 
managed node into a JMX Manager node or to stop a node from being a JMX 
Manager. For potential managers (`jmx-manager=true` and 
`jmx-manager-start=false`), this MBean is created when a Locator requests it.
+
+**Note:**
+You must configure the node to allow it to become a JMX Manager. See 
[Configuring a JMX 
Manager](jmx_manager_operations.html#topic_263072624B8D4CDBAD18B82E07AA44B6) 
for configuration information.
+
+**MBean Details**
+
+|| 
   |
+|||
+| Scope  | ALL 
   |
+| Proxied| No  
   |
+| Object Name| GemFire:type=Member, 
service=Manager,member= |
+| Instances Per Node | 1   
   |
+
+See the `org.apache.geode.management.ManagerMXBean` JavaDocs for information 
on available MBean methods and attributes.
+
+## DistributedSystemMXBean
+
+System-wide aggregate MBean that provides a high-level view of the entire 
distributed system including all members (cache servers, peers, locators) and 
their caches. At any given point of time, it can provide a snapshot of the 
complete distributed system and its operations.
+
+The DistributedSystemMXBean provides APIs for performing distributed 
system-wide operations such as backing up all members, shutting down all 
members or showing various distributed system metrics.
+
+You can attach a standard JMX NotificationListener to this MBean to listen for 
notifications throughout the distributed system. See [Geode JMX MBean 
Notifications](mbean_notifications.html) for more information.
+
+This MBean also provides some MBean model navigation APIS. These APIs should 
be used to navigate through all the MBeans exposed by a Geode System.
+
+**MBean Details**
+
+|| |
+||-|
+| Scope  | Aggregate   |
+| Proxied| No  |
+| Object Name| GemFire:type=Distributed,service=System |
+| Instances Per Node | 1   |
+
+See the `org.apache.geode.management.DistributedSystemMXBean` JavaDocs for 
information on available MBean methods and attributes.
+
+## DistributedRegionMXBean
+
+System-wide aggregate MBean of a named region. It provides a high-level view 
of a region for all members hosting and/or using that region. For example, you 
can obtain a list of all members that are hosting the region. Some methods are 
only available for partitioned regions.
+
+**MBean Details**
+
+|| 
|
+||-|
+| Scope  | Aggregate   
|
+| Proxied| No  
|
+| Object Name| 
GemFire:type=Distributed,service=Region,name= |
+| Instances Per Node | 0..N   

[32/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/events/list_of_event_handlers_and_events.html.md.erb
--
diff --git 
a/geode-docs/developing/events/list_of_event_handlers_and_events.html.md.erb 
b/geode-docs/developing/events/list_of_event_handlers_and_events.html.md.erb
new file mode 100644
index 000..5f63db1
--- /dev/null
+++ b/geode-docs/developing/events/list_of_event_handlers_and_events.html.md.erb
@@ -0,0 +1,164 @@
+---
+title:  List of Event Handlers and Events
+---
+
+Geode provides many types of events and event handlers to help you manage your 
different data and application needs.
+
+## Event Handlers
+
+Use either cache handlers or membership handlers in any single application. Do 
not use both. The event handlers in this table are cache handlers unless 
otherwise noted.
+
+
+
+
+
+
+
+
+
+Handler API
+Events received
+Description
+
+
+
+
+AsyncEventListener
+AsyncEvent
+Tracks changes in a region for write-behind processing. Extends th 
CacheCallback interface. You install a 
write-back cache listener to an AsyncEventQueue 
instance. You can then add the AsyncEventQueue 
instance to one or more regions for write-behind processing. See [Implementing 
an AsyncEventListener for Write-Behind Cache Event 
Handling](implementing_write_behind_event_handler.html#implementing_write_behind_cache_event_handling).
+
+
+CacheCallback
+ 
+Superinterface of all cache event listeners. Functions only to clean up 
resources that the callback allocated.
+
+
+CacheListener
+RegionEvent, EntryEvent
+Tracks changes to region and its data entries. Responds synchronously. 
Extends CacheCallback interface. Installed in 
region. Receives only local cache events. Install one in every member where you 
want the events handled by this listener. In a partitioned region, the cache 
listener only fires in the primary data store. Listeners on secondaries are not 
fired.
+
+
+CacheWriter
+RegionEvent, EntryEvent
+Receives events for pending changes to the region and its data 
entries in this member or one of its peers. Has the ability to abort the 
operations in question. Extends CacheCallback 
interface. Installed in region. Receives events from anywhere in the 
distributed region, so you can install one in one member for the entire 
distributed region. Receives events only in primary data store in partitioned 
regions, so install one in every data store.
+
+
+ClientMembershipListener
+(org.apache.geode.management .membership.ClientMembershipListener)
+ClientMembershipEvent
+One of the interfaces that replaces the deprecated Admin APIs. You can use 
the ClientMembershipListener to receive membership events only about clients. 
This listener's callback methods are invoked when this process detects 
connection changes to clients. Callback methods include memberCrashed, memberJoined, 
memberLeft (graceful exit).
+
+
+CqListener
+CqEvent
+Receives events from the server cache that satisfy a client-specified 
query. Extends CacheCallback interface. 
Installed in the client inside a CqQuery.
+
+
+GatewayConflictResolver
+TimestampedEntryEvent
+Decides whether to apply a potentially conflicting event to a region that 
is distributed over a WAN configuration. This event handler is called only when 
the distributed system ID of an update event is different from the ID that last 
updated the region entry.
+
+
+MembershipListener
+(org.apache.geode.management .membership.MembershipListener)
+MembershipEvent
+Use this interface to receive membership events only about peers. This 
listener's callback methods are invoked when peer members join or leave the 
Geode distributed system. Callback methods include memberCrashed, memberJoined, and 
memberLeft (graceful exit).
+
+
+RegionMembershipListener
+RegionEvent
+Provides after-event notification when a region with the same name has 
been created in another member and when other members hosting the region join 
or leave the distributed system. Extends CacheCallback and CacheListener. 
Installed in region as a CacheListener.
+
+
+TransactionListener
+TransactionEvent with embedded list of 
EntryEvent
+Tracks the outcome of transactions and changes to data entries in the 
transaction.
+
+**Note:**
+Multiple transactions on the same cache can cause concurrent invocation of 
TransactionListener methods, so implement 
methods that do the appropriate synchronizing of the multiple threads for 
thread-safe operation.
+
+Extends CacheCallback interface. Installed in 
cache using transaction manager. Works with region-level listeners if 
needed.
+
+
+TransactionWriter
+TransactionEvent with embedded list of 
EntryEvent
+Receives events for pending transaction commits. Has the ability 
to abort the transaction. Extends CacheCallback 
interface. Installed in cache using transaction manager. At most one writer is 
called per transaction. Install a writer in every transaction host.
+
+
+Unive

[51/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

GEODE-1952 Consolidated docs under a single geode-docs directory


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/ccc2fbda
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/ccc2fbda
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/ccc2fbda

Branch: refs/heads/feature/GEODE-1952-2
Commit: ccc2fbda4001884a0bf36ca2d76d75358cbda3eb
Parents: 2eabdb2
Author: Dave Barnes 
Authored: Tue Oct 4 10:32:02 2016 -0700
Committer: Dave Barnes 
Committed: Tue Oct 4 10:32:02 2016 -0700

--
 .gitignore  |6 -
 CONTRIBUTE.md   |   63 -
 README.md   |   93 -
 about_geode.html.md.erb |9 -
 basic_config/book_intro.html.md.erb |   23 -
 .../chapter_overview.html.md.erb|   23 -
 ...uted_system_member_configuration.html.md.erb |   34 -
 .../config_concepts/local_vs_remote.html.md.erb |   12 -
 .../chapter_overview.html.md.erb|   15 -
 .../managing_data_entries.html.md.erb   |  129 -
 .../using_custom_classes.html.md.erb|   34 -
 .../data_regions/chapter_overview.html.md.erb   |   48 -
 .../create_a_region_with_API.html.md.erb|   63 -
 .../create_a_region_with_cacheXML.html.md.erb   |   68 -
 .../create_a_region_with_gfsh.html.md.erb   |   38 -
 .../creating_custom_attributes.html.md.erb  |   47 -
 .../managing_data_regions.html.md.erb   |  205 --
 .../managing_region_attributes.html.md.erb  |   96 -
 .../new_region_existing_data.html.md.erb|   11 -
 .../data_regions/region_naming.html.md.erb  |   14 -
 .../data_regions/region_shortcuts.html.md.erb   |   98 -
 .../store_retrieve_region_shortcuts.html.md.erb |   60 -
 .../setting_distributed_properties.html.md.erb  |   64 -
 .../the_cache/chapter_overview.html.md.erb  |   31 -
 .../intro_cache_management.html.md.erb  |   79 -
 .../managing_a_client_cache.html.md.erb |   67 -
 .../managing_a_multiuser_cache.html.md.erb  |   49 -
 .../managing_a_peer_server_cache.html.md.erb|   64 -
 .../managing_a_secure_cache.html.md.erb |   50 -
 .../setting_cache_initializer.html.md.erb   |   59 -
 .../setting_cache_properties.html.md.erb|   22 -
 configuring/chapter_overview.html.md.erb|   67 -
 .../deploying_application_jars.html.md.erb  |  114 -
 .../cluster_config/export-import.html.md.erb|   39 -
 .../gfsh_config_troubleshooting.html.md.erb |   58 -
 .../gfsh_load_from_shared_dir.html.md.erb   |   27 -
 .../cluster_config/gfsh_persist.html.md.erb |  108 -
 .../cluster_config/gfsh_remote.html.md.erb  |   61 -
 .../persisting_configurations.html.md.erb   |  320 --
 .../using_member_groups.html.md.erb |   27 -
 .../running/change_file_spec.html.md.erb|   40 -
 .../running/default_file_specs.html.md.erb  |   59 -
 .../deploy_config_files_intro.html.md.erb   |   17 -
 .../running/deploying_config_files.html.md.erb  |   28 -
 .../deploying_config_jar_files.html.md.erb  |   35 -
 .../running/firewall_ports_config.html.md.erb   |   15 -
 .../running/firewalls_connections.html.md.erb   |   18 -
 .../running/firewalls_multisite.html.md.erb |   70 -
 configuring/running/firewalls_ports.html.md.erb |  229 --
 .../running/managing_output_files.html.md.erb   |   16 -
 .../running/running_the_cacheserver.html.md.erb |  182 -
 .../running/running_the_locator.html.md.erb |  240 --
 .../starting_up_shutting_down.html.md.erb   |  129 -
 developing/book_intro.html.md.erb   |   57 -
 .../chapter_overview.html.md.erb|   21 -
 .../continuous_querying_whats_next.html.md.erb  |   71 -
 .../how_continuous_querying_works.html.md.erb   |   81 -
 ...implementing_continuous_querying.html.md.erb |  185 -
 .../PDX_Serialization_Features.html.md.erb  |   23 -
 .../auto_serialization.html.md.erb  |  124 -
 ...ation_with_class_pattern_strings.html.md.erb |   68 -
 .../chapter_overview.html.md.erb|   23 -
 .../data_serialization_options.html.md.erb  |   51 -
 .../extending_the_autoserializer.html.md.erb|  106 -
 .../gemfire_data_serialization.html.md.erb  |   35 -
 .../gemfire_pdx_serialization.html.md.erb   |   47 -
 .../java_serialization.html.md.erb  |   12 -
 .../jsonformatter_pdxinstances.html.md.erb  |   29 -
 .../persist_pdx_metadata_to_disk.html.md.erb|   36 -
 .../program_application_for_pdx.html.md.erb |   90 -
 .../use_pdx_high_level_steps.html.md.erb|   32 -
 .../use_pdx_serializable.html.md.erb|   98 -
 .../use_pdx_serializer.html.md.erb  |  128 -
 .../using_PdxInstanceFactory.html.md.erb|   34 -
 .../using_pdx_region_entry_keys.

[42/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/query_additional/case_sensitivity.html.md.erb
--
diff --git a/developing/query_additional/case_sensitivity.html.md.erb 
b/developing/query_additional/case_sensitivity.html.md.erb
deleted file mode 100644
index 2d49259..000
--- a/developing/query_additional/case_sensitivity.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@

-title:  Case Sensitivity

-
-Query language keywords such as SELECT, NULL, DATE, and  are 
case-insensitive. Identifiers such as attribute names, method names, and path 
expressions are case-sensitive.
-
-In terms of query string and region entry matching, if you want to perform a 
case-insensitive search on a particular field, you can use the Java String 
class `toUpperCase` and `toLowerCase` methods in your query. For example:
-
-``` pre
-SELECT entry.value FROM /exampleRegion.entries entry WHERE 
entry.value.toUpperCase LIKE '%BAR%'
-```
-
-or
-
-``` pre
-SELECT * FROM /exampleRegion WHERE foo.toLowerCase LIKE '%bar%'
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/query_additional/literals.html.md.erb
--
diff --git a/developing/query_additional/literals.html.md.erb 
b/developing/query_additional/literals.html.md.erb
deleted file mode 100644
index 37fcc0f..000
--- a/developing/query_additional/literals.html.md.erb
+++ /dev/null
@@ -1,65 +0,0 @@

-title:  Supported Literals

-
-## Comparing Values With java.util.Date
-
-Geode supports the following literal types:
-
-**boolean**
-A `boolean` value, either TRUE or FALSE
-**int** and **long**
-An integer literal is of type `long` if has a suffix of the ASCII letter 
L. Otherwise it is of type `int`.
-**floating point**
-A floating-point literal is of type `float` if it has a suffix of an ASCII 
letter `F`. Otherwise its type is `double`. Optionally, it can have a suffix of 
an ASCII letter `D`. A double or floating point literal can optionally include 
an exponent suffix of `E` or `e`, followed by a signed or unsigned number.
-
-**string**
-String literals are delimited by single quotation marks. Embedded 
single-quotation marks are doubled. For example, the character string `'Hello'` 
evaluates to the value `Hello`, while the character string `'He said, 
''Hello'''` evaluates to `He said, 'Hello'`. Embedded newlines are kept as part 
of the string literal.
-**char**
-A literal is of type char if it is a string literal prefixed by the 
keyword `CHAR`, otherwise it is of type `string`. The `CHAR` literal for the 
single-quotation mark character is `CHAR` `` (four single quotation 
marks).
-**date**
-A `java.sql.Date` object that uses the JDBC format prefixed with the DATE 
keyword: `DATE -mm-dd`. In the `Date`, `` represents the year, `mm` 
represents the month, and `dd` represents the day. The year must be represented 
by four digits; a two-digit shorthand for the year is not allowed.
-**time**
-A `java.sql.Time` object that uses the JDBC format (based on a 24-hour 
clock) prefixed with the TIME keyword: `TIME hh:mm:ss`. In the `Time`, `hh` 
represents the hours, `mm` represents the minutes, and `ss` represents the 
seconds.
-**timestamp**
-A `java.sql.Timestamp` object that uses the JDBC format with a TIMESTAMP 
prefix: `TIMESTAMP -mm-dd hh:mm:ss.f` In the `Timestamp`, 
`-mm-dd` represents the `date`, `hh:mm:ss` represents the `time`, and 
`f` represents the fractional seconds (up to nine digits).
-**NIL**
-Equivalent alternative of `NULL`.
-**NULL**
-The same as `null` in Java.
-**UNDEFINED**
-A special literal that is a valid value for any data type. An `UNDEFINED` 
value is the result of accessing an attribute of a null-valued attribute. Note 
that if you access an attribute that has an explicit value of null, then it is 
not undefined. For example if a query accesses the attribute address.city and 
address is null, the result is undefined. If the query accesses address, then 
the result is not undefined, it is `NULL`.
-
-You can compare temporal literal values `DATE`, `TIME`, and `TIMESTAMP` with 
`java.util.Date` values. There is no literal for `java.util.Date` in the query 
language.
-
-## Type Conversion
-
-The Geode query processor performs implicit type conversions and promotions 
under certain cases in order to evaluate expressions that contain different 
types. The query processor performs binary numeric promotion, method invocation 
conversion, and temporal type conversion.
-
-## Binary Numeric Promotion
-
-The query processor performs binary numeric promotion on the operands of the 
following operators:
-
--   Comparison operators <, <=, >, and >=
--   Equality operators = and <>
--   Binary numeric promotion widens the operands in a numeric expression to 
the widest representation used by any of the operands. I

[63/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
--
diff --git 
a/geode-docs/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
 
b/geode-docs/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
index a94609e..a472ab3 100644
--- 
a/geode-docs/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
+++ 
b/geode-docs/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb
@@ -2,6 +2,23 @@
 title:  Setting Up the HTTP Module for Tomcat
 ---
 
+
+
 To use the Geode HTTP module with Tomcat application servers, you will need to 
modify Tomcat's `server.xml` and `context.xml` files.
 
 Configuration is slightly different depending on the topology you are setting 
up. Refer to [Common Topologies for HTTP Session 
Management](common_gemfire_topologies.html#common_gemfire_topologies) for more 
information.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
--
diff --git 
a/geode-docs/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
 
b/geode-docs/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
index d86dca6..50e41be 100644
--- 
a/geode-docs/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
+++ 
b/geode-docs/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb
@@ -2,6 +2,23 @@
 title:  Changing the Default Geode Configuration in the AppServers Module
 ---
 
+
+
 By default, the AppServers module will run Geode automatically with 
preconfigured settings. You can change these Geode settings.
 
 Here are the default settings:

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/http_session_mgmt/weblogic_common_configuration_changes.html.md.erb
--
diff --git 
a/geode-docs/tools_modules/http_session_mgmt/weblogic_common_configuration_changes.html.md.erb
 
b/geode-docs/tools_modules/http_session_mgmt/weblogic_common_configuration_changes.html.md.erb
index 693fc8e..7669fdd 100644
--- 
a/geode-docs/tools_modules/http_session_mgmt/weblogic_common_configuration_changes.html.md.erb
+++ 
b/geode-docs/tools_modules/http_session_mgmt/weblogic_common_configuration_changes.html.md.erb
@@ -2,6 +2,23 @@
 title:  Common Geode Configuration Changes for AppServers
 ---
 
+
+
 ## Overriding Region Attributes
 
 When using the HTTP Session Management Module, you cannot override region 
attributes directly on the cache server. You must place all region attribute 
definitions in the region attributes template that you customize within the 
application server. For example, to specify a different name for the region's 
disk store, you could add the new disk-store-name specification to the region 
attributes template and then reference the template on the cache server.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
--
diff --git 
a/geode-docs/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
 
b/geode-docs/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
index 935853f..e0eb267 100644
--- 
a/geode-docs/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
+++ 
b/geode-docs/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb
@@ -2,6 +2,23 @@
 title:  Setting Up the HTTP Module for AppServers
 ---
 
+
+
 To use the module, you need to modify your application's `web.xml` files. 
Configuration is slightly different depending on the topology you are setting 
up.
 
 Refer to [Common Topologies for HTTP Session 
Management](common_gemfire_topologies.html#common_gemfire_topologies) for more 
information. Modifying the war file can be done manually or with the 
`modify_war` script. To see the command line options for the `modify_war` 
script, invoke:

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/pulse/chapter_overview.html.md.erb
--
diff --git a/geode-docs/tools_modules/pulse/chapter_overview.html.md.erb 
b/geode-docs/tools_modules/pulse/chapter_overview.html.md.erb
index 553fa55..19de8f1 100644
--- a/geode-docs/tools_modules/pulse/chapter_overview.html.md.erb
+++ b/geode-docs/tools_modules/pulse/chapter_overview.html.md.erb
@@ -2,6 +2,23 @@
 title:  Geode Pulse
 ---
 
+
+
 Geode Pulse is a Web Application that provides a graphical dashboard 

[46/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/delta_propagation/implementing_delta_propagation.html.md.erb
--
diff --git 
a/developing/delta_propagation/implementing_delta_propagation.html.md.erb 
b/developing/delta_propagation/implementing_delta_propagation.html.md.erb
deleted file mode 100644
index 7727532..000
--- a/developing/delta_propagation/implementing_delta_propagation.html.md.erb
+++ /dev/null
@@ -1,24 +0,0 @@

-title:  Implementing Delta Propagation

-
-By default, delta propagation is enabled in your distributed system. When 
enabled, delta propagation is used for objects that implement 
`org.apache.geode.Delta`. You program the methods to store and extract delta 
information for your entries and to apply received delta information.
-
-
-Use the following procedure to implement delta propagation in your distributed 
system.
-
-1.  Study your object types and expected application behavior to determine 
which regions can benefit from using delta propagation. Delta propagation does 
not improve performance for all data and data modification scenarios. See [When 
to Avoid Delta Propagation](when_to_use_delta_prop.html#when_to_use_delta_prop).
-2.  For each region where you are using delta propagation, choose whether to 
enable cloning using the delta propagation property `cloning-enabled`. Cloning 
is disabled by default. See [Delta Propagation 
Properties](delta_propagation_properties.html#delta_propagation_properties).
-3.  If you do not enable cloning, review all associated listener code for 
dependencies on `EntryEvent.getOldValue`. Without cloning, Geode modifies the 
entry in place and so loses its reference to the old value. For delta events, 
the `EntryEvent` methods `getOldValue` and `getNewValue` both return the new 
value.
-4.  For every class where you want delta propagation, implement 
`org.apache.geode.Delta` and update your methods to support delta propagation. 
Exactly how you do this depends on your application and object needs, but these 
steps describe the basic approach:
-1.  If the class is a plain old Java object (POJO), wrap it for this 
implementation and update your code to work with the wrapper class.
-2.  Define as transient any extra object fields that you use to manage 
delta state. This can help performance when the full object is distributed. 
Whenever standard Java serialization is used, the transient keyword indicates 
to Java to not serialize the field.
-3.  Study the object contents to decide how to handle delta changes. Delta 
propagation has the same issues of distributed concurrency control as the 
distribution of full objects, but on a more detailed level. Some parts of your 
objects may be able to change independent of one another while others may 
always need to change together. Send deltas large enough to keep your data 
logically consistent. If, for example, field A and field B depend on each 
other, then your delta distributions should either update both fields or 
neither. As with regular updates, the fewer producers you have on a data 
region, the lower your likelihood of concurrency issues.
-4.  In the application code that puts entries, put the fully populated 
object into the local cache. Even though you are planning to send only deltas, 
errors on the receiving end could cause Geode to request the full object, so 
you must provide it to the originating put method. Do this even in empty 
producers, with regions configured for no local data storage. This usually 
means doing a get on the entry unless you are sure it does not already exist 
anywhere in the distributed region.
-5.  Change each field's update method to record information about the 
update. The information must be sufficient for `toDelta` to encode the delta 
and any additional required delta information when it is invoked.
-6.  Write `hasDelta` to report on whether a delta is available.
-7.  Write `toDelta` to create a byte stream with the changes to the object 
and any other information `fromDelta` will need to apply the changes. Before 
returning from `toDelta`, reset your delta state to indicate that there are no 
delta changes waiting to be sent.
-8.  Write `fromDelta` to decode the byte stream that `toDelta` creates and 
update the object.
-9.  Make sure you provide adequate synchronization to your object to 
maintain a consistent object state. If you do not use cloning, you will 
probably need to synchronize on reads and writes to avoid reading partially 
written updates from the cache.This synchronization might involve `toDelta`, 
`fromDelta`, `toData`, `fromData`, and other methods that access or update the 
object. Additionally, your implementation should take into account the 
possibility of concurrent invocations of `fromDelta` and one or more of the 
object's update methods.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-

[55/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/introduction/developing-solaris.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/introduction/developing-solaris.html.md.erb 
b/geode-docs/nativeclient/introduction/developing-solaris.html.md.erb
deleted file mode 100644
index da707bc..000
--- a/geode-docs/nativeclient/introduction/developing-solaris.html.md.erb
+++ /dev/null
@@ -1,44 +0,0 @@

-title:  Developing C++ Programs on Solaris

-
-This section describes how to build and run a native client application on 
Solaris.
-
-## Step 1. Set Environment Variables
-
-**Note:** When compiling external projects or applications that are used or 
referenced by the native client, make sure that you compile them for the same 
target architecture as your native client installation. For example, if you 
installed the 32-bit (x86) version of the native client, compile your external 
projects for 32-bit (x86) architecture.
-
-Set the native client environment variables on each Solaris host. For each 
case, ** is the path to the native client product directory.
-
-**For Bourne and Korn shells (sh, ksh, bash)**
-
-``` pre
-GFCPP=; export GFCPP
-PATH=$GFCPP/bin:$PATH;export PATH
-LD_LIBRARY_PATH=$GFCPP/lib:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH
-```
-
-## Step 2. Compile C++ Clients and Dynamically Link to 
Them to Native Client Library
-
-Version 5.9 of the *SUNpro* compiler is supported on Solaris. The linker 
switches vary according to whether you are statically linking to the native 
client library.
-
-To build and link a C++ client on Solaris, the compilation command line must 
include the appropriate arguments from this table.
-
-
-
-| Argument 
  | Explanation|
-|||
-| `-D_REENTRANT`   
  | Required to compile Solaris programs in a thread-safe way. |
-| `-xarch=v8plus`  
  | Enables 32-bit compilation.|
-| `-xarch=v9`  
  | Enables 64-bit compilation.|
-| `-ldl`; `-lpthread`; `-lc`; `-lm`; `-lsocket`; `-lrt`; `-lnsl`; 
`-ldemangle`; `-lkstat`; `-lz` | Additional libraries.  
|
-| `-library=stlport4`  
  | Solaris library compilation.   |
-| `-I$ GFCPP /include` 
  | Specifies the GemFire include directory.   |
-
-
-
-## Step 3. Make Sure the Native Client Library Can Be 
Loaded
-
-When a C++ application is not statically linked to the native client library, 
the library must be dynamically loadable.
-
-To verify that the native client library is available for loading, make sure 
you have added the path *productDir*`/lib` to the *LD\_LIBRARY\_PATH* 
environment variable, where *productDir* is the path to the Geode product 
directory.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/introduction/developing-windows.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/introduction/developing-windows.html.md.erb 
b/geode-docs/nativeclient/introduction/developing-windows.html.md.erb
deleted file mode 100644
index 7ed37c0..000
--- a/geode-docs/nativeclient/introduction/developing-windows.html.md.erb
+++ /dev/null
@@ -1,56 +0,0 @@

-title:  Developing C++ Programs on Windows

-
-Geode uses the Visual Studio 2010 Service Pack 1 compiler for C++ programs on 
Windows, which invokes Microsoft® `cl.exe` from the command line at 
compile time.
-
-The Geode native client supports .NET 4.0 and Visual Studio 2010. For 
advantages and more information on the features of .NET 4.0 and Visual Studio 
2010 SP1, see 
[http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx](http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx)
 and 
[http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx](http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx).
-
-Visual Studio 2010 SP1 is the recommended compiler. If you are using any other 
compiler, contact technical support for assistance.
-
-**Note:** When compiling external projects or applications that are used or 
referenced by the native client, make sure that you compile them for the same

[68/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/getting_started/uninstall_gemfire.html.md.erb
--
diff --git a/geode-docs/getting_started/uninstall_gemfire.html.md.erb 
b/geode-docs/getting_started/uninstall_gemfire.html.md.erb
index baf19eb..e5cac8a 100644
--- a/geode-docs/getting_started/uninstall_gemfire.html.md.erb
+++ b/geode-docs/getting_started/uninstall_gemfire.html.md.erb
@@ -2,6 +2,23 @@
 title:  How to Uninstall
 ---
 
+
+
 This section describes how to remove Geode.
 
 Shut down any running Geode processes and then remove the entire directory 
tree. No additional system modifications or modification of Windows registry 
entries are needed.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
--
diff --git a/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb 
b/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
index 7303800..916d301 100644
--- a/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
+++ b/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
@@ -2,6 +2,23 @@
 title:  Handling Forced Cache Disconnection Using Autoreconnect
 ---
 
+
+
 A Geode member may be forcibly disconnected from a Geode distributed system if 
the member is unresponsive for a period of time, or if a network partition 
separates one or more members into a group that is too small to act as the 
distributed system.
 
 ## How the Autoreconnection Process Works

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/book_intro.html.md.erb
--
diff --git a/geode-docs/managing/book_intro.html.md.erb 
b/geode-docs/managing/book_intro.html.md.erb
index 568203a..d7929f2 100644
--- a/geode-docs/managing/book_intro.html.md.erb
+++ b/geode-docs/managing/book_intro.html.md.erb
@@ -2,6 +2,23 @@
 title:  Managing Apache Geode
 ---
 
+
+
 *Managing Apache Geode* describes how to plan and implement tasks associated 
with managing, monitoring, and troubleshooting Apache Geode.
 
 -   **[Apache Geode Management and 
Monitoring](../managing/management/management_and_monitoring.html)**

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb
--
diff --git a/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb 
b/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb
index 38b4251..1439348 100644
--- a/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb
+++ b/geode-docs/managing/cache_snapshots/chapter_overview.html.md.erb
@@ -2,6 +2,23 @@
 title:  Cache and Region Snapshots
 ---
 
+
+
 Snapshots allow you to save region data and reload it later. A typical use 
case is loading data from one environment into another, such as capturing data 
from a production system and moving it into a smaller QA or development system.
 
 In effect, you can load data from one distributed system into another 
distributed system. Administrators export a snapshot of a region or an entire 
cache (multiple regions) and later import the snapshot into another region or 
distributed system by using the `RegionSnapshotService` or 
`CacheSnapshotService` interface and the `Region.getSnapshotService` or 
`Cache.getSnapshotService` method.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb
--
diff --git 
a/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb 
b/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb
index 1cd2065..eaddd41 100644
--- a/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb
+++ b/geode-docs/managing/cache_snapshots/exporting_a_snapshot.html.md.erb
@@ -2,6 +2,23 @@
 title:  Exporting Cache and Region Snapshots
 ---
 
+
+
 To save Geode cache or region data to a snapshot that you can later load into 
another distributed system or region, use the `cache.getSnapshotService.save` 
API, `region.getSnapshotService.save` API, or the `gfsh` command-line interface 
(`export data`).
 
 If an error occurs during export, the export halts and the snapshot operation 
is canceled. Typical errors that halt an export include scenarios such as full 
disk, problems with file permissions, and network partitioning.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/cache_snapshots/filtering_snapshot_entries.html.md.erb
--
diff --git 
a/geode-docs/managing/cache_snapshots/filtering_snapshot_en

[44/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/events/limit_server_subscription_queue_size.html.md.erb
--
diff --git a/developing/events/limit_server_subscription_queue_size.html.md.erb 
b/developing/events/limit_server_subscription_queue_size.html.md.erb
deleted file mode 100644
index ff571b2..000
--- a/developing/events/limit_server_subscription_queue_size.html.md.erb
+++ /dev/null
@@ -1,57 +0,0 @@

-title:  Limit the Server's Subscription Queue Memory Use

-
-
-These are options for limiting the amount of server memory the subscription 
queues consume.
-
--   Optional: Conflate the subscription queue messages.
--   Optional: Increase the frequency of queue synchronization. This only 
applies to configurations where server redundancy is used for high 
availability. Increase the client’s pool configuration, 
`subscription-ack-interval`. The client periodically sends a batch 
acknowledgment of messages to the server, rather than acknowledging each 
message individually. A lower setting speeds message delivery and generally 
reduces traffic between the server and client. A higher setting helps contain 
server queue size. Example:
-
-``` pre
-
- 
-   
-  ... 
-
-```
-
-You might want to lower the interval if you have a very busy system and 
want to reduce the space required in the servers for the subscription queues. 
More frequent acknowledgments means fewer events held in the server queues 
awaiting acknowledgment.
-
--   Optional: Limit Queue Size. Cap the server queue size using overflow or 
blocking. These options help avoid out of memory errors on the server in the 
case of slow clients. A slow client slows the rate that the server can send 
messages, causing messages to back up in the queue, possibly leading to out of 
memory on the server. You can use one or the other of these options, but not 
both:
--   Optional: Overflow to Disk. Configure subscription queue overflow by 
setting the server’s `client-subscription` properties. With overflow, the 
most recently used (MRU) events are written out to disk, keeping the oldest 
events, the ones that are next in line to be sent to the client, available in 
memory. Example:
-
-``` pre
-
- 
-   
-
-```
-
--   Optional: Block While Queue Full. Set the server’s 
`maximum-message-count` to the maximum number of event messages allowed in any 
single subscription queue before incoming messages are blocked. You can only 
limit the message count, not the size allocated for messages. Examples:
-
-XML:
-
-``` pre
-
-  
-```
-
-API:
-
-``` pre
-Cache cache = ...; 
-CacheServer cacheServer = cache.addCacheServer(); 
-cacheServer.setPort(41414); 
-cacheServer.setMaximumMessageCount(5); 
-cacheServer.start(); 
-```
-
-**Note:**
-With this setting, one slow client can slow the server and all of its 
other clients because this blocks the threads that write to the queues. All 
operations that add messages to the queue block until the queue size drops to 
an acceptable level. If the regions feeding these queues are partitioned or 
have `distributed-ack` or `global` scope, operations on them remain blocked 
until their event messages can be added to the queue. If you are using this 
option and see stalling on your server region operations, your queue capacity 
might be too low for your application behavior.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/events/list_of_event_handlers_and_events.html.md.erb
--
diff --git a/developing/events/list_of_event_handlers_and_events.html.md.erb 
b/developing/events/list_of_event_handlers_and_events.html.md.erb
deleted file mode 100644
index 5f63db1..000
--- a/developing/events/list_of_event_handlers_and_events.html.md.erb
+++ /dev/null
@@ -1,164 +0,0 @@

-title:  List of Event Handlers and Events

-
-Geode provides many types of events and event handlers to help you manage your 
different data and application needs.
-
-## Event Handlers
-
-Use either cache handlers or membership handlers in any single application. Do 
not use both. The event handlers in this table are cache handlers unless 
otherwise noted.
-
-
-
-
-
-
-
-
-
-Handler API
-Events received
-Description
-
-
-
-
-AsyncEventListener
-AsyncEvent
-Tracks changes in a region for write-behind processing. Extends th 
CacheCallback interface. You install a 
write-back cache listener to an AsyncEventQueue 
instance. You can then add the AsyncEventQueue 
instance to one or more regions for write-behind processing. See [Implementing 
an AsyncEventListener for Write-Behind Cache Event 
Handling](implementing_write_behind_event_handler.html#impl

[30/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/query_additional/case_sensitivity.html.md.erb
--
diff --git 
a/geode-docs/developing/query_additional/case_sensitivity.html.md.erb 
b/geode-docs/developing/query_additional/case_sensitivity.html.md.erb
new file mode 100644
index 000..2d49259
--- /dev/null
+++ b/geode-docs/developing/query_additional/case_sensitivity.html.md.erb
@@ -0,0 +1,19 @@
+---
+title:  Case Sensitivity
+---
+
+Query language keywords such as SELECT, NULL, DATE, and  are 
case-insensitive. Identifiers such as attribute names, method names, and path 
expressions are case-sensitive.
+
+In terms of query string and region entry matching, if you want to perform a 
case-insensitive search on a particular field, you can use the Java String 
class `toUpperCase` and `toLowerCase` methods in your query. For example:
+
+``` pre
+SELECT entry.value FROM /exampleRegion.entries entry WHERE 
entry.value.toUpperCase LIKE '%BAR%'
+```
+
+or
+
+``` pre
+SELECT * FROM /exampleRegion WHERE foo.toLowerCase LIKE '%bar%'
+```
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/query_additional/literals.html.md.erb
--
diff --git a/geode-docs/developing/query_additional/literals.html.md.erb 
b/geode-docs/developing/query_additional/literals.html.md.erb
new file mode 100644
index 000..37fcc0f
--- /dev/null
+++ b/geode-docs/developing/query_additional/literals.html.md.erb
@@ -0,0 +1,65 @@
+---
+title:  Supported Literals
+---
+
+## Comparing Values With java.util.Date
+
+Geode supports the following literal types:
+
+**boolean**
+A `boolean` value, either TRUE or FALSE
+**int** and **long**
+An integer literal is of type `long` if has a suffix of the ASCII letter 
L. Otherwise it is of type `int`.
+**floating point**
+A floating-point literal is of type `float` if it has a suffix of an ASCII 
letter `F`. Otherwise its type is `double`. Optionally, it can have a suffix of 
an ASCII letter `D`. A double or floating point literal can optionally include 
an exponent suffix of `E` or `e`, followed by a signed or unsigned number.
+
+**string**
+String literals are delimited by single quotation marks. Embedded 
single-quotation marks are doubled. For example, the character string `'Hello'` 
evaluates to the value `Hello`, while the character string `'He said, 
''Hello'''` evaluates to `He said, 'Hello'`. Embedded newlines are kept as part 
of the string literal.
+**char**
+A literal is of type char if it is a string literal prefixed by the 
keyword `CHAR`, otherwise it is of type `string`. The `CHAR` literal for the 
single-quotation mark character is `CHAR` `` (four single quotation 
marks).
+**date**
+A `java.sql.Date` object that uses the JDBC format prefixed with the DATE 
keyword: `DATE -mm-dd`. In the `Date`, `` represents the year, `mm` 
represents the month, and `dd` represents the day. The year must be represented 
by four digits; a two-digit shorthand for the year is not allowed.
+**time**
+A `java.sql.Time` object that uses the JDBC format (based on a 24-hour 
clock) prefixed with the TIME keyword: `TIME hh:mm:ss`. In the `Time`, `hh` 
represents the hours, `mm` represents the minutes, and `ss` represents the 
seconds.
+**timestamp**
+A `java.sql.Timestamp` object that uses the JDBC format with a TIMESTAMP 
prefix: `TIMESTAMP -mm-dd hh:mm:ss.f` In the `Timestamp`, 
`-mm-dd` represents the `date`, `hh:mm:ss` represents the `time`, and 
`f` represents the fractional seconds (up to nine digits).
+**NIL**
+Equivalent alternative of `NULL`.
+**NULL**
+The same as `null` in Java.
+**UNDEFINED**
+A special literal that is a valid value for any data type. An `UNDEFINED` 
value is the result of accessing an attribute of a null-valued attribute. Note 
that if you access an attribute that has an explicit value of null, then it is 
not undefined. For example if a query accesses the attribute address.city and 
address is null, the result is undefined. If the query accesses address, then 
the result is not undefined, it is `NULL`.
+
+You can compare temporal literal values `DATE`, `TIME`, and `TIMESTAMP` with 
`java.util.Date` values. There is no literal for `java.util.Date` in the query 
language.
+
+## Type Conversion
+
+The Geode query processor performs implicit type conversions and promotions 
under certain cases in order to evaluate expressions that contain different 
types. The query processor performs binary numeric promotion, method invocation 
conversion, and temporal type conversion.
+
+## Binary Numeric Promotion
+
+The query processor performs binary numeric promotion on the operands of the 
following operators:
+
+-   Comparison operators <, <=, >, and >=
+-   Equality operators = and <>
+-   Binary numeric promotion widens the operands in 

[33/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/events/ha_event_messaging_whats_next.html.md.erb
--
diff --git 
a/geode-docs/developing/events/ha_event_messaging_whats_next.html.md.erb 
b/geode-docs/developing/events/ha_event_messaging_whats_next.html.md.erb
new file mode 100644
index 000..f61aba6
--- /dev/null
+++ b/geode-docs/developing/events/ha_event_messaging_whats_next.html.md.erb
@@ -0,0 +1,78 @@
+---
+title:  Highly Available Client/Server Event Messaging
+---
+
+
+With server redundancy, each pool has a primary server and some number of 
secondaries. The primaries and secondaries are assigned on a per-pool basis and 
are generally spread out for load balancing, so a single client with multiple 
pools may have primary queues in more than one server.
+
+The primary server pushes events to clients and the secondaries maintain queue 
backups. If the primary server fails, one of the secondaries becomes primary to 
provide uninterrupted event messaging.
+
+For example, if there are six servers running and `subscription-redundancy` is 
set to two, one server is the primary, two servers are secondary, and the 
remaining three do not actively participate in HA for the client. If the 
primary server fails, the system assigns one of the secondaries as the new 
primary and attempts to add another server to the secondary pool to retain the 
initial redundancy level. If no new secondary server is found, then the 
redundancy level is not satisfied but the failover procedure completes 
successfully. As soon as another secondary is available, it is added.
+
+When high availability is enabled:
+
+-   The primary server sends event messages to the clients.
+-   Periodically, the clients send received messages to the server and the 
server removes the sent messages from its queues.
+-   Periodically, the primary server synchronizes with its secondaries, 
notifying them of messages that can be discarded because they have already been 
sent and received. There is a lag in notification, so the secondary servers 
remain only roughly synchronized with the primary. Secondary queues contain all 
messages that are contained in the primary queue plus possibly a few messages 
that have already been sent to clients.
+-   In the case of primary server failure, one of the secondaries becomes the 
primary and begins sending event messages from its queues to the clients. 
Immediately after failover, the new primary usually resends some messages that 
were already sent by the old primary. The client recognizes these as duplicates 
and discards them.
+
+In stage 1 of this figure, the primary sends an event message to the client 
and a synchronization message to its secondary. By stage 2, the secondary and 
client have updated their queue and message tracking information. If the 
primary failed at stage two, the secondary would start sending event messages 
from its queue beginning with message A10. The client would discard the resend 
of message A10 and then process subsequent messages as usual.
+
+
+## Change Server Queue Synchronization Frequency
+
+By default, the primary server sends queue synchronization messages to the 
secondaries every second. You can change this interval with the `gfsh alter 
runtime` command
+
+Set the interval for queue synchronization messages as follows:
+
+-   gfsh:
+
+``` pre
+gfsh>alter runtime --message-sync-interval=2
+```
+
+-   XML:
+
+``` pre
+ 
+
+```
+
+-   Java:
+
+``` pre
+cache = CacheFactory.create();
+cache.setMessageSyncInterval(2);  
+```
+
+The ideal setting for this interval depends in large part on your application 
behavior. These are the benefits of shorter and longer interval settings:
+
+-   A shorter interval requires less memory in the secondary servers because 
it reduces queue buildup between synchronizations. In addition, fewer old 
messages in the secondary queues means reduced message re-sends after a 
failover. These considerations are most important for systems with high data 
update rates.
+-   A longer interval requires fewer distribution messages between the primary 
and secondary, which benefits overall system performance.
+
+## Set Frequency of Orphan Removal from the Secondary 
Queues
+
+Usually, all event messages are removed from secondary subscription queues 
based on the primary's synchronization messages. Occasionally, however, some 
messages are orphaned in the secondary queues. For example, if a primary fails 
in the middle of sending a synchronization message to its secondaries, some 
secondaries might receive the message and some might not. If the failover goes 
to a secondary that did receive the message, the system will have secondary 
queues holding messages that are no longer in the primary queue. The new 
primary will never synchronize on these messages, leaving them orphaned 

[29/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
--
diff --git 
a/geode-docs/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
 
b/geode-docs/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
new file mode 100644
index 000..a834b60
--- /dev/null
+++ 
b/geode-docs/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
@@ -0,0 +1,62 @@
+---
+title:  Using Indexes on Equi-Join Queries using Multiple Regions
+---
+
+To query across multiple regions, identify all equi-join conditions. Then, 
create as few indexes for the equi-join conditions as you can while still 
joining all regions.
+
+
+If there are equi-join conditions that redundantly join two regions (in order 
to more finely filter the data, for example), then creating redundant indexes 
for these joins will negatively impact performance. Create indexes only on one 
equi-join condition for each region pair.
+
+In this example query:
+
+``` pre
+SELECT DISTINCT * 
+FROM /investors inv, /securities sc, /orders or, 
+inv.ordersPlaced inv_op, or.securities or_sec 
+WHERE inv_op.orderID = or.orderID 
+AND or_sec.secID = sc.secID
+```
+
+All conditions are required to join the regions, so you would create four 
indexes, two for each equi-join condition:
+
+| FROM clause  | Indexed expression |
+|--||
+| /investors inv, inv.ordersPlaced inv\_op | inv\_op.orderID|
+| /orders or, or.securities or\_sec| or.orderID |
+
+| FROM clause   | Indexed expression |
+|---||
+| /orders or, or.securities or\_sec | or\_sec.secID  |
+| /securities sc| sc.secID   |
+
+Adding another condition to the example:
+
+``` pre
+SELECT DISTINCT * 
+FROM /investors inv, /securities sc, /orders or, 
+inv.ordersPlaced inv_op, or.securities or_sec, sc.investors sc_invs 
+WHERE inv_op.orderID = or.orderID 
+AND or_sec.secID = sc.secID
+AND inv.investorID = sc_invs.investorID
+```
+
+You would still only want to use four indexes in all, as that's all you need 
to join all of the regions. You would need to choose the most performant two of 
the following three index pairs:
+
+| FROM clause  | Indexed expression |
+|--||
+| /investors inv, inv.ordersPlaced inv\_op | inv\_op.orderID|
+| /orders or, or.securities or\_sec| or.orderID |
+
+| FROM clause   | Indexed expression |
+|---||
+| /orders or, or.securities or\_sec | or\_sec.secID  |
+| /securities sc, sc.investors sc\_invs | sc.secID   |
+
+| FROM clause  | Indexed expression  |
+|--|-|
+| /investors inv, inv.ordersPlaced inv\_op | inv.investorID  |
+| /securities sc, sc.investors sc\_invs| sc\_invs.investorID |
+
+The most performant set is that which narrows the data to the smallest result 
set possible. Examine your data and experiment with the three index pairs to 
see which provides the best performance.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/query_select/aggregates.html.md.erb
--
diff --git a/geode-docs/developing/query_select/aggregates.html.md.erb 
b/geode-docs/developing/query_select/aggregates.html.md.erb
new file mode 100644
index 000..1a4e0aa
--- /dev/null
+++ b/geode-docs/developing/query_select/aggregates.html.md.erb
@@ -0,0 +1,92 @@
+---
+title:  OQL Aggregate Functions
+---
+
+The aggregate functions 
+```MIN```,
+```MAX```,
+```AVG```,
+```AVG``` over a DISTINCT expression,
+```SUM``` over a DISTINCT expression,
+```COUNT```, and
+```COUNT``` over a DISTINCT expression
+are supported.
+The ```GROUP BY``` extension is also supported where appropriate.
+
+The ```MIN``` function returns the smallest of the selected
+expression.
+The type of the expression must evaluate to a 
+```java.lang.Comparable```.
+
+The ```MAX``` function returns the largest of the selected
+expression.
+The type of the expression must evaluate to a 
+```java.lang.Comparable```.
+
+The ```AVG``` function returns the arithmetic mean of the set
+formed by the selected expression.
+The type of the expression must evaluate to a 
+```java.lang.Number```.
+For partitioned regions,
+each node's buckets provide both a sum and the number of elements
+to the node executing the query,
+such that a correct ave

[45/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/events/conflate_multisite_gateway_queue.html.md.erb
--
diff --git a/developing/events/conflate_multisite_gateway_queue.html.md.erb 
b/developing/events/conflate_multisite_gateway_queue.html.md.erb
deleted file mode 100644
index e2e7ff1..000
--- a/developing/events/conflate_multisite_gateway_queue.html.md.erb
+++ /dev/null
@@ -1,113 +0,0 @@

-title:  Conflating Events in a Queue

-
-Conflating a queue improves distribution performance. When conflation is 
enabled, only the latest queued value is sent for a particular key.
-
-
-**Note:**
-Do not use conflation if your receiving applications depend on the specific 
ordering of entry modifications, or if they need to be notified of every change 
to an entry.
-
-Conflation is most useful when a single entry is updated frequently, but other 
sites only need to know the current value of the entry (rather than the value 
of each update). When an update is added to a queue that has conflation 
enabled, if there is already an update message in the queue for the entry key, 
then the existing message assumes the value of the new update and the new 
update is dropped, as shown here for key A.
-
-
-
-**Note:**
-This method of conflation is different from the one used for server-to-client 
subscription queue conflation and peer-to-peer distribution within a 
distributed system.
-
-## Examples—Configuring Conflation for a Gateway 
Sender Queue
-
-To enable conflation for a gateway sender queue, use one of the following 
mechanisms:
-
--   **cache.xml configuration**
-
-``` pre
-
-   
-   ... 
-
-```
-
--   **Java API configuration**
-
-``` pre
-Cache cache = new CacheFactory().create();
-
-GatewaySenderFactory gateway = cache.createGatewaySenderFactory();
-gateway.setParallel(true);
-gateway.setPersistenceEnabled(true);
-gateway.setDiskStoreName("gateway-disk-store");
-gateway.setBatchConflationEnabled(true);
-GatewaySender sender = gateway.create("NY", "1");
-sender.start();
-```
-
-Entry updates in the current, in-process batch are not eligible for 
conflation.
-
--   **gfsh:**
-
-``` pre
-gfsh>create gateway-sender --id="NY" --parallel=true 
-   --remote-distributed-system-id="1"
-   --enable-persistence=true
-   --disk-store-name="gateway-disk-store"
-   --enable-batch-conflation=true
-```
-
-The following examples show how to configure conflation for an asynchronous 
event queue:
-
--   **cache.xml configuration**
-
-``` pre
-
-   
-  
- MyAsyncEventListener
-  
-   jdbc:db2:SAMPLE 
-  
-  
-   gfeadmin 
-  
-  
-   admin1 
-  
-   
- 
-...
-
-```
-
--   **Java API configuration**
-
-``` pre
-Cache cache = new CacheFactory().create();
-AsyncEventQueueFactory factory = cache.createAsyncEventQueueFactory();
-factory.setPersistent(true);
-factory.setDiskStoreName("async-disk-store");
-factory.setParallel(false);
-factory.setBatchConflationEnabled(true);
-AsyncEventListener listener = new MyAsyncEventListener();
-AsyncEventQueue sampleQueue = factory.create("customerWB", listener);
-```
-
-Entry updates in the current, in-process batch are not eligible for 
conflation.
-
--   **gfsh:**
-
-``` pre
-gfsh>create async-event-queue --id="sampleQueue" --persistent=true 
---disk-store="async-disk-store" --parallel="false" 
---listener=myAsyncEventListener 
---listener-param=url#jdbc:db2:SAMPLE 
---listener-param=username#gfeadmin 
---listener-param=password#admin1
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/events/conflate_server_subscription_queue.html.md.erb
--
diff --git a/developing/events/conflate_server_subscription_queue.html.md.erb 
b/developing/events/conflate_server_subscription_queue.html.md.erb
deleted file mode 100644
index f6d4990..000
--- a/developing/events/conflate_server_subscription_queue.html.md.erb
+++ /dev/null
@@ -1,36 +0,0 @@

-title:  Conflate the Server Subscription Queue

-
-
-Conflating the server subscription queue can save space in the server and time 
in message processing.
-
-Enable conflation at the server level in the server region configuration:
-
-``` pre
-
-   
-
-```
-
-Override the server setting as needed, on a per-client basis, in the 
client’s `gemfire.properties`:
-
-``` pre
-conflate-events=false
-```
-
-Valid `conflate-events` settings are:
--   `server`, which uses the server settings
--   `true`, which conflates everything sent to the client
--   `false`, which does not conflate anything sent to this client
-
-Conflation 

[50/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/.gitignore
--
diff --git a/.gitignore b/.gitignore
deleted file mode 100644
index eaf0351..000
--- a/.gitignore
+++ /dev/null
@@ -1,6 +0,0 @@
-geode-book/Gemfile.lock
-geode-book/final_app
-geode-book/output
-out
-temp
-*.bak

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/CONTRIBUTE.md
--
diff --git a/CONTRIBUTE.md b/CONTRIBUTE.md
deleted file mode 100644
index dd97f47..000
--- a/CONTRIBUTE.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# Contributing to the Project Geode Documentation
-
-Project Geode welcomes your contributions to the community's documentation 
efforts. You can participate by writing new content, reviewing and editing 
existing content, or fixing bugs. This document covers the following topics:
-
-- [How to Contribute](#contribute)
-- [Document Source Files and Tools](#source_tools)
-- [Writing Guidelines](#guidelines)
-
-[]()
-
-## How to Contribute
-
-We use the fork-and-pull collaboration method on GitHub:
-
-1. In your GitHub account, fork the gemfire/docs-geode-md repository.
-2. Create a local clone of your fork.
-3. Make changes and commit them in your fork.
-4. In the gemfire/docs-geode-md repository, create a pull request.
-
-See [Using Pull 
Requests](https://help.github.com/articles/using-pull-requests/) on GitHub for 
more about the fork-and-pull collaboration method.
-
-[]()
-
-## Document Source Files and Tools
-
-Project Geode documentation source files are written in markdown. Image files 
include .gif and .png graphics and editable image files in the open source SVG 
format.
-
-- [Working with Markdown Files](#markdown)
-- [Working with Images and Graphics](#images)
-
-[]()
-
-### Working with Markdown Files
-
-You can edit markdown files in any text editor. For more, read [Daring 
Fireball's Markdown Syntax 
page](https://daringfireball.net/projects/markdown/syntax).
-
-[]()
-
-### Working with Images and Graphics
-
-Image files in .gif or .png format are in the `images` directory in the 
Project Geode docs repo. Images in .svg format are in the `images_svg` 
directory.
-
-Most of the Project Geode image files have been converted to the open source 
SVG format. You can insert SVG images directly into an XML topic and modify 
images using a SVG editor.
-
-The Wikipedia page [Comparison of Vector Graphics 
Editors](http://en.wikipedia.org/wiki/Comparison_of_vector_graphics_editors) 
provides a list and comparison of commercial and free vector graphics editors. 
Note, however, that not all of these programs support the SVG format.
-
-[]()
-
-## Writing Guidelines
-
-The most important advice we can provide for working with the Project Geode 
docs is to spend some time becoming familiar with the existing source files and 
the structure of the project directory. In particular, note the following 
conventions and tips:
-
-- Top-level subdirectories organize topics into "books": basic_config, 
configuring, developing, etc.
-
-- Use lowercase characters for all file and directory names. Separate words in 
filenames with an underscore (`_`) character.
-
-- Use the `.md` file extension for topic files.
-
-- Add new topics to the existing directories by subject type. Only create a 
new directory if you are starting a new subject or a new book.
-
-- To start a new topic, you can make a copy of an existing file with similar 
content and edit it.
-
-- Use the appropriate document type for the content you are writing. Create 
multiple topics if you are writing overview, procedural, and reference content.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/README.md
--
diff --git a/README.md b/README.md
deleted file mode 100644
index a018ca1..000
--- a/README.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Project Geode End-User Documentation
-
-The latest check-ins to `project-geode/docs` are automatically built and 
published to .
-
-Project Geode provides the full source for end-user documentation in markdown 
format. The markdown can be built into HTML using 
[Bookbinder](https://github.com/pivotal-cf/bookbinder).
-
-Bookbinder is a gem that binds together a unified documentation web 
application from markdown, html, and/or DITA source material. The source 
material for bookbinder must be stored either in local directories or in GitHub 
repositories. Bookbinder runs [middleman](http://middlemanapp.com/) to produce 
a Rackup app that can be deployed locally or as a Web application.
-
-This document contains instructions for building the local Geode documentation 
and publishing it to Cloud Foundry or Pivotal Web Services. It contains the 
sections:
-
-- [Bookbinder Usage](#usage)
-- [Prerequisites](#prereq)
-- [Building the Documentation](#building)
-- [Pub

[52/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/sqlite-persistence/windows_install.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/sqlite-persistence/windows_install.html.md.erb 
b/geode-docs/nativeclient/sqlite-persistence/windows_install.html.md.erb
deleted file mode 100644
index d753366..000
--- a/geode-docs/nativeclient/sqlite-persistence/windows_install.html.md.erb
+++ /dev/null
@@ -1,37 +0,0 @@

-title:  Windows Installation

-
-This topic describes how to install the SQLite Persistence Manager on Windows 
for use with the Geode native client.
-
-The Geode Native Client has been tested with SQLite v3.7.14.1.
-
-The productDir directory refers to the native client 
product directory path.
-
-The following libraries are required. The productDir/bin 
directory containing these libraries must be present in the Windows `PATH` 
environment variable, and that directory is added to `PATH` during the Geode 
product installation.
-
--   The `sqliteimpl.dll` and `GemStone.GemFire.Plugins.SQLite.dll` files are 
provided in productDir/bin.
--   For .NET C\# native client application development, you need to obtain the 
`System.Data.SQLite.dll` SQLite library, as described below. The library can be 
copied to productDir/bin.
--   For C++ native client application development, you need the `SqLite3.dll` 
SQLite Library. You create this library and make it available in the runtime 
linking path, or copied to productDir/bin, as described 
below.
-
-## Downloading Pre-built System.Data.SQLite.dll Binaries
-
-If you are writing native client applications using the .NET caching API, 
obtain the SQLite library (version 3.12.2 or later) for Windows as follows:
-
-1.  Access the System.Data.SQLite Download Page at the following URL: 
[http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki).
-2.  Download the appropriate setup file for your .NET Framework installation 
and hardware architecture.
--   For 64-bit Windows, under **Precompiled Binaries for 64-bit Windows 
(.NET Framework 4.5.1)** download 
`sqlite-netFx451-binary-bundle-x64-2013-1.0.101.0.zip`.
-
-3.  Execute the setup .exe file, and follow the prompts in the installation 
wizard. Accept all default installation options.
-4.  Copy the `C:\Program 
Files\System.Data.SQLite\2010\bin\System.Data.SQLite.dll` file to your Geode 
Native Client distribution at `productDir\bin`.
-
-## Downloading, Building, and Installing the Library
-
-If you are writing native client applications using the C++ caching API, you 
need to build the SQLite solution for your Windows platform architecture.
-
-1.  Download the source code `sqlite-autoconf-NNN.tar.gz` file (where 
*NNN* corresponds to the version) for SQLite version 3.12.2 or later from 
[http://www.sqlite.org/download.html](http://www.sqlite.org/download.html).
-2.  Extract the source code from the .tar.gz file. You may need to use CygWin 
or a Windows-compatible tar extraction tool.
-3.  Using Visual Studio, build the version-specific SqLite solution either as 
a release or debug build:
--   If you are using 64-bit Windows, use the x64 configuration.
-
-4.  From the built files, copy the `SqLite3.dll` file to your Geode Native 
Client distribution at productDir/bin.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/system-statistics/cache_performance_statistics.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/system-statistics/cache_performance_statistics.html.md.erb
 
b/geode-docs/nativeclient/system-statistics/cache_performance_statistics.html.md.erb
deleted file mode 100644
index 0edcb18..000
--- 
a/geode-docs/nativeclient/system-statistics/cache_performance_statistics.html.md.erb
+++ /dev/null
@@ -1,30 +0,0 @@

-title:  Cache Performance Statistics

-
-Use cache performance statistics to determine the type and number of cache 
operations being performed and how much time they consume.
-
-These statistics are available if the member creates a cache.
-
-|  |   
   |
-|--|--|
-| `creates`| Total number of cache creates.
   |
-| `puts`   | Total number of cache puts.   
   |
-| `gets`   | Total number of cache gets.   
   |
-| `entries`

[35/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb
--
diff --git 
a/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb
 
b/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb
new file mode 100644
index 000..35cbe66
--- /dev/null
+++ 
b/geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb
@@ -0,0 +1,106 @@
+---
+title:  Extending the ReflectionBasedAutoSerializer
+---
+
+You can extend the `ReflectionBasedAutoSerializer` to handle serialization in 
a customized manner. This section provides an overview of the available 
method-based customization options and an example of extending the serializer 
to support BigDecimal and BigInteger types.
+
+## Reasons to Extend the ReflectionBasedAutoSerializer
+
+One of the main use cases for extending the `ReflectionBasedAutoSerializer` is 
that you want it to handle an object that would currently need to be handled by 
standard Java serialization. There are several issues with having to use 
standard Java serialization that can be addressed by extending the PDX 
`ReflectionBasedAutoSerializer`.
+
+-   Each time we transition from a Geode serialized object to an object that 
will be Java I/O serialized, extra data must get serialized. This can cause a 
great deal of serialization overhead. This is why it is worth extending the 
`ReflectionBasedAutoSerializer` to handle any classes that normally would have 
to be Java I/O serialized.
+-   Expanding the number of classes that can use the 
`ReflectionBasedAutoSerializer` is beneficial when you encounter object graphs. 
After we use Java I/O serialization on an object, any objects under that object 
in the object graph will also have to be Java I/O serialized. This includes 
objects that normally would have been serialized using PDX or 
`DataSerializable`.
+-   If standard Java I/O serialization is done on an object and you have 
enabled check-portability, then an exception will be thrown. Even if you are 
not concerned with the object's portability, you can use this flag to find out 
what classes would use standard Java serialization (by getting an exception on 
them) and then enhancing your auto serializer to handle them.
+
+## Overriding ReflectionBasedAutoSerializer Behavior
+
+You can customize the specific behaviors in `ReflectionBasedAutoSerializer` by 
overriding the following methods:
+
+-   **`isClassAutoSerialized`** customizes which classes to autoserialize.
+-   **`isFieldIncluded`** specifies which fields of a class to autoserialize.
+-   **`getFieldName`** defines the specific field names that will be generated 
during autoserialization.
+-   **`isIdentifyField`** controls which field is marked as the identity 
field. Identity fields are used when a PdxInstance computes its hash code to 
determine whether it is equal to another object.
+-   **`getFieldType`** determines the field type that will be used when 
autoserializing the given field.
+-   **`transformFieldValue`** controls whether specific field values of a PDX 
object can be transformed during serialization.
+-   **`writeTransform`** controls what field value is written during auto 
serialization.
+-   **`readTransform`** controls what field value is read during auto 
deserialization.
+
+These methods are only called the first time the 
`ReflectionBasedAutoSerializer` sees a new class. The results will be 
remembered and used the next time the same class is seen.
+
+For details on these methods and their default behaviors, see the JavaDocs on 
[ReflectionBasedAutoSerializer](/releases/latest/javadoc/org/apache/geode/pdx/ReflectionBasedAutoSerializer.html)
 for details.
+
+## Example of Optimizing Autoserialization of 
BigInteger and BigDecimal Types
+
+This section provides an example of extending the 
`ReflectionBasedAutoSerializer` to optimize the automatic serialization of 
BigInteger and BigDecimal types.
+
+The following code sample illustrates a subclass of the 
`ReflectionBasedAutoSerializer` that optimizes BigInteger and BigDecimal 
autoserialization:
+
+``` pre
+public static class BigAutoSerializer extends ReflectionBasedAutoSerializer {
+   public BigAutoSerializer(Boolean checkPortability, string… patterns) {
+super(checkPortability, patterns);
+}
+
+@Override
+public FieldType get FieldType(Field f, Class clazz) {
+   if (f.getType().equals(BigInteger.class)) {
+return FieldType.BYTE_ARRAY; 
+  } else if (f.getType().equals(BigDecimal.class)) {
+return FieldType.STRING; 
+  } else {
+return super.getFieldType(f, clazz);
+  }
+}
+@Override
+public boolean transformFieldValue(Field f, Class clazz) {
+  if (f.getType().equals(BigInteger.class)) {
+return true;
+  } else if (f.getType().equals(BigDecimal.class)) {
+

[64/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb
--
diff --git 
a/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb
index c79dd3e..c27c0d7 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/load-balance.html.md.erb
@@ -2,6 +2,23 @@
 title:  load-balance gateway-sender
 ---
 
+
+
 Causes the specified gateway sender to close its current connections and 
reconnect to remote gateway receivers in a more balanced fashion.
 
 Use this command to load balance connections between gateway senders to 
receivers. For example, when you add a new gateway receiver node at a remote 
site, execute this command so that the new gateway receiver can pick up 
connections from the specified gateway sender. Invoking this command 
redistributes a sender's connections more evenly among all the gateway 
receivers.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb
index e6988cb..1dc6628 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/locate.html.md.erb
@@ -2,6 +2,23 @@
 title:  locate entry
 ---
 
+
+
 Locate a region entry on a member.
 
 ## locate entry

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb
index 3ac0a5d..00446c1 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/netstat.html.md.erb
@@ -2,6 +2,23 @@
 title:  netstat
 ---
 
+
+
 Report network information and statistics via the "netstat" operating system 
command.
 
 Report important network usage information/statistics for the given member.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb
index 1ea2ab2..86a1d8c 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/pause.html.md.erb
@@ -2,6 +2,23 @@
 title:  pause gateway-sender
 ---
 
+
+
 Pause a gateway sender.
 
 Pause the gateway sender on a member or members. See [Pausing Gateway 
Senders](../../../topologies_and_comm/topology_concepts/multisite_overview.html#topic_9AA37B43642D4DE19072CA3367C849BA__section_hdt_2js_bq)
 for details on pausing gateway senders.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb
index bb57d13..4a3e85e 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/pdx.html.md.erb
@@ -2,6 +2,23 @@
 title:  pdx rename
 ---
 
+
+
 Renames PDX types in an offline disk store.
 
 Any PDX types that are renamed will be listed in the output. If no renames are 
done or the disk-store is online, then this command will fail.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb
index 38a5e6a..e5ab1e6 100644
--- a/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb
+++ b/geode-docs/tools_modules/gfsh/command-pages/put.html.md.erb
@@ -2,6 +2,23 @@
 title:  put
 ---
 
+
+
 Add or update a region entry.
 
 Add or update an entry in a region.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/tools_modules/gfsh/command-pages/query.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/query.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages

[59/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb
 
b/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb
deleted file mode 100644
index 62e033b..000
--- 
a/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb
+++ /dev/null
@@ -1,156 +0,0 @@

-title:  Pool Configuration Example and Settings

-
-Connection pools require standard client/server distributed system and cache 
configuration settings. You must also configure settings for the locator, 
server, and pool elements.
-
--   Locator. Host and port where a server locator is listening.
--   Server. Host and port where a server is listening.
--   Pool. Client/server connection pool.
-
-The example shows a declarative pool configuration. Following the example is a 
table that describes the attributes that can be configured.
-
-## Example—Declarative Pool Configuration
-
-This example shows a declarative pool configuration.
-
-**Note:**
-You create an instance of `PoolFactory` through `PoolManager`.
-
-``` pre
-
-   
-
-```
-
-## Pool Attributes
-
-
-
-
-
-
-
-
-
-Attribute Name
-Description
-Default
-
-
-
-
-free-connection-timeout
-Number of milliseconds (ms) that the client waits for a free connection 
if  max-connections limit is configured and all 
connections are in use.
-1 ms
-
-
-idle-timeout
-Number of milliseconds to wait for a connection to become idle for load 
balancing
-5000 ms
-
-
-load-conditioning-interval
-Interval in which the pool checks to see if a connection to a specific 
server should be moved to a different server to improve the load 
balance.
-30 ms (5 minutes)
-
-
-max-connections
-Maximum number of connections that the pool can create. If all 
connections are in use, an operation requiring a client-to server-connection is 
blocked until a connection is available or the  
free-connection-timeout is reached. If set to -1, there is no maximum. 
The setting must indicate a cap greater than  
min-connections.
-
-**Note:**
-If you use this setting to cap your pool connections, disable the pool 
attribute  pr-single-hop-enabled. Leaving single 
hop enabled can increase thrashing and lower performance.
-
--1
-
-
-min-connections
-Number of connections that must be created initially.
-5
-
-
-name
-Pool name.
-
-
-
-ping-interval
-Interval between pinging the server to show the client is alive, set in 
milliseconds. Pings are only sent when the ping-interval elapses between normal client messages. This must 
be set lower than the server’s maximum-time-between-pings.
-1 ms
-
-
-pr-single-hop-enabled
-Setting used for single-hop access to partitioned region data in the 
servers for some data operations. See PartitionResolver.
 See note in thread-local-connections 
below.
-True
-
-
-read-timeout
-Number of milliseconds to wait for a response from a server before the 
connection times out.
-1
-
-
-retry-attempts
-Number of times to retry an operation after a time-out or exception for 
high availability. If set to -1, the pool tries every available server once 
until it succeeds or has tried all servers.
--1
-
-
-server-group
-Server group from which to select connections. If not specified, the 
global group of all connected servers is used.
-empty
-
-
-socket-buffer-size
-Size of the socket buffer, in bytes, on each connection 
established.
-32768
-
-
-statistic-interval
-Default frequency, in milliseconds, with which the client statistics 
are sent to the server. A value of -1 indicates 
that the statistics are not sent to the server.
--1
-
-
-subscription-ack-interval
-Number of milliseconds to wait before sending an acknowledgment to the 
server about events received from the subscriptions.
-100
-
-
-subscription-enabled
-Whether to establish a server to client subscription.
-False
-
-
-subscription-message-tracking-timeout
-Number of milliseconds for which messages sent from a server to a 
client are tracked. The tracking is done to minimize duplicate events.
-9
-
-
-subscription-redundancy
-Redundancy for servers that contain subscriptions established by the 
client. A value of -1 causes all available 
servers in the specified group to be made redundant.
-0
-
-
-thread-local-connections
-Whether the connections must have affinity to the thread that last used 
them.
-
-**Note:**
-To set this to true, also set pr-single-hop-enabled to false. A true value in pr-single-hop-enabled automatically assigns a false value to thread-local-connections...
-
-False
-
-
-update-locator-list-interval
-An integer number of milliseconds defining the interval between locator 
list updates. If the value is less than or equal to 0, the update will be 
disabled.
-5000
-
-
-

[62/76] [abbrv] incubator-geode git commit: GEODE-1952: Update geode-docs dir for docs donation

[kmiller]

GEODE-1952: Update geode-docs dir for docs donation

- Alter the only 2 files that did not have a title component
at the top of the file. This facilitates easily adding the
Apache license to the files.


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/e0f52033
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/e0f52033
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/e0f52033

Branch: refs/heads/feature/GEODE-1952-2
Commit: e0f5203356991e15ab49abb193d25ed30030a572
Parents: 381d0fa
Author: Karen Miller 
Authored: Wed Oct 5 15:40:26 2016 -0700
Committer: Karen Miller 
Committed: Wed Oct 5 15:40:26 2016 -0700

--
 .../reference/topics/gfe_cache_xml.html.md.erb  |   3 +
 ...mory_requirements_for_cache_data.html.md.erb | 269 ++-
 ...requirements_guidelines_and_calc.html.md.erb | 269 ---
 3 files changed, 264 insertions(+), 277 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e0f52033/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
--
diff --git a/geode-docs/reference/topics/gfe_cache_xml.html.md.erb 
b/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
index fbe289d..03b0956 100644
--- a/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
+++ b/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
@@ -1,3 +1,6 @@
+---
+title: " Element Reference"
+---
 
 
 #  Element Reference

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/e0f52033/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb
--
diff --git 
a/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb 
b/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb
index 2de6d98..2111573 100644
--- a/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb
+++ b/geode-docs/reference/topics/memory_requirements_for_cache_data.html.md.erb
@@ -12,20 +12,273 @@ These requirements include estimates for the following 
resources:
 
 The information here is only a guideline, and assumes a basic understanding of 
Geode. While no two applications or use cases are exactly alike, the 
information here should be a solid starting point, based on real-world 
experience. Much like with physical database design, ultimately the right 
configuration and physical topology for deployment is based on the performance 
requirements, application data access characteristics, and resource constraints 
(i.e., memory, CPU, and network bandwidth) of the operating environment.
 
--   **[Core Guidelines for Geode Data Region 
Design](../../reference/topics/memory_requirements_guidelines_and_calc.html#topic_ipt_dqz_j4)**
 
--   **[Memory Usage 
Overview](../../reference/topics/memory_requirements_guidelines_and_calc.html#topic_ppn_pqz_j4)**
+
 
--   **[Calculating Application Object 
Overhead](../../reference/topics/memory_requirements_guidelines_and_calc.html#topic_kjx_brz_j4)**
+# Core Guidelines for Geode Data Region Design
 
--   **[Using Key Storage 
Optimization](../../reference/topics/memory_requirements_guidelines_and_calc.html#topic_exn_2tz_j4)**
+The following guidelines apply to region design:
 
--   **[Measuring Cache 
Overhead](../../reference/topics/memory_requirements_guidelines_and_calc.html#topic_ac4_mtz_j4)**
+-   For 32-bit JVMs: If you have a small data set (< 2GB) and a read-heavy 
requirement, you should be using replicated regions.
+-   For 64-bit JVMs: If you have a data set that is larger than 50-60% of the 
JVM heap space you can use replicated regions. For read heavy applications this 
can be a performance win. For write heavy applications you should use 
partitioned caches.
+-   If you have a large data set and you are concerned about scalability you 
should be using partitioned regions.
+-   If you have a large data set and can tolerate an on-disk subset of data, 
you should be using either replicated regions or partitioned regions with 
overflow to disk.
+-   If you have different data sets that meet the above conditions, then you 
might want to consider a hybrid solution mixing replicated and partition 
regions. Do not exceed 50 to 75% of the JVM heap size depending on how write 
intensive your application is.
 
--   **[Estimating Management and Monitoring 
Overhead](../../reference/topics/memory_requirements_guidelines_and_calc.html#topic_i1m_stz_j4)**
+## Memory Usage Overview
 
--   **[Determining Object Serialization 
Overhead](../../reference/topics/memory_requirements_guidelines_and_calc.html#topic_psn_5tz_j4)**
+The following guidelines should provide a rough estimate of the amount of 
memory cons

[54/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/programming-examples/serialization-java.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/programming-examples/serialization-java.html.md.erb 
b/geode-docs/nativeclient/programming-examples/serialization-java.html.md.erb
deleted file mode 100644
index ac11128..000
--- 
a/geode-docs/nativeclient/programming-examples/serialization-java.html.md.erb
+++ /dev/null
@@ -1,210 +0,0 @@

-title:  Java Serialization Example

-
-## Implementing an Embedded Object (Java)
-
-``` pre
-public class User implements DataSerializable
-{
-private String name;
-private int userId;
-private ExampleObject eo;
-static {
-Instantiator.register(
-   new Instantiator(User.class, (byte)45)
-   {
-public DataSerializable newInstance() {
-return new User();
-}
-} );
-}
-/**
- * Creates an "empty" User whose contents are filled in by
- * invoking its toData() method
- */
-
-private User() {
-this.name = "";
-this.userId = 0;
-this.eo = new ExampleObject(0);
-}
-
-public User(String name, int userId) {
-this.name = name;
-this.userId = userId;
-this.eo = new ExampleObject(userId);
-}
-
-public void setEO(ExampleObject eo) {
-this.eo = eo;
-}
-
-public ExampleObject getEO() {
-return eo;
-}
-
-public void toData(DataOutput out) throws IOException {
-out.writeUTF(this.name);
-out.writeInt(this.userId);
-eo.toData(out);
-}
-
-public void fromData(DataInput in) throws IOException,
- ClassNotFoundException {
-this.name = in.readUTF();
-this.userId = in.readInt();
-this.eo.fromData(in);
-}
-
-public int getUserId() {
-return userId;
-}
-
-public String getName() {
-return name;
-}
-
-public boolean equals(User o) {
-if (!this.name.equals(o.name)) return false;
-if (this.userId != o.userId) return false;
-if (!this.eo.equals(o.eo)) return false;
-return true;
-}
-}
-```
-
-## Implementing Complex Data Types (Java)
-
-``` pre
-public class ExampleObject implements DataSerializable {
-private double double_field;
-private long long_field;
-private float float_field;
-private int int_field;
-private short short_field;
-private java.lang.String string_field;
-private Vector string_vector;
-static {
-Instantiator.register(new Instantiator(ExampleObject.class, (byte) 46) 
{
-public DataSerializable newInstance() {
-return new ExampleObject();
-}
-});
-}
-public ExampleObject( ) {
-this.double_field = 0.0D;
-this.long_field = 0L;
-this.float_field = 0.0F;
-this.int_field = 0;
-this.short_field = 0;
-this.string_field = null;
-this.string_vector = null;
-}
-public ExampleObject(int id) {
-this.int_field = id;
-this.string_field = String.valueOf(id);
-this.short_field = Short.parseShort(string_field);
-this.double_field = Double.parseDouble(string_field);
-this.float_field = Float.parseFloat(string_field);
-this.long_field = Long.parseLong(string_field);
-this.string_vector = new Vector();
-for (int i=0; i<3; i++) {
-this.string_vector.addElement(string_field);
-}
-}
-public ExampleObject(String id_str) {
-this.int_field = Integer.parseInt(id_str);
-this.string_field = id_str;
-this.short_field = Short.parseShort(string_field);
-this.double_field = Double.parseDouble(string_field);
-this.float_field = Float.parseFloat(string_field);
-this.long_field = Long.parseLong(string_field);
-this.string_vector = new Vector();
-for (int i=0; i<3; i++) {
-this.string_vector.addElement(string_field);
-}
-}
-public double getDouble_field( ) {
-return this.double_field;
-}
-public void setDouble_field( double double_field ) {
-this.double_field = double_field;
-}
-public long getLong_field( ) {
-return this.long_field;
-}
-public void setLong_field( long long_field ) {
-this.long_field = long_field;
-}
-public float getFloat_field( ) {
-return this.float_field;
-}
-public void setFloat_field( float float_field ) {
-this.float_field = float_field;
-}
-public int getInt_field( ) {
-return this.int_field;
-}
-public void setInt_field( int int_field ) {
-   

[57/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/delta-propagation/how-delta-propagation-works.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/delta-propagation/how-delta-propagation-works.html.md.erb
 
b/geode-docs/nativeclient/delta-propagation/how-delta-propagation-works.html.md.erb
deleted file mode 100644
index eac1907..000
--- 
a/geode-docs/nativeclient/delta-propagation/how-delta-propagation-works.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@

-title:  How Delta Propagation Works

-
-Geode propagates object deltas using methods that you program on the client 
side. The methods are in the delta interface, which you implement in your 
cached objects’ classes.
-
-This figure shows delta propagation for a change to an entry with key, `k`, 
and value object, `v`.
-
-
-Figure: Delta Propagation
-
-
-
-1.  **get operation**. The `get` works as usual; the cache returns the full 
entry object from the local cache or, if it is unavailable there, from a server 
cache or from a loader.
-2.  **update methods**. You need to add code to the object’s update methods 
so that they save delta information for object updates, in addition to the work 
they were already doing.
-3.  **put operation**. The `put` works as usual in the local cache, using the 
full value, then calls `hasDelta` to check for deltas and `toDelta` to 
serialize the information.
-4.  **receipt of delta**. `fromDelta` extracts the delta information that was 
serialized by `toDelta` and applies it to the object in the local cache. The 
delta is applied directly to the existing value or to a clone, depending on how 
you configure it for the region.
-5.  **additional distributions**. As with full distributions, receiving 
members forward the delta according to their configurations and connections to 
other members. In the example, the server would forward the delta to its peers 
and its other clients as needed. Receiving members do not recreate the delta; 
`toDelta` is only called in the originating member.
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/delta-propagation/implementing-delta-propagation.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/delta-propagation/implementing-delta-propagation.html.md.erb
 
b/geode-docs/nativeclient/delta-propagation/implementing-delta-propagation.html.md.erb
deleted file mode 100644
index 6d1c3ee..000
--- 
a/geode-docs/nativeclient/delta-propagation/implementing-delta-propagation.html.md.erb
+++ /dev/null
@@ -1,41 +0,0 @@

-title:  Implementing Delta Propagation

-
-By default, delta propagation is enabled in your distributed system and is 
used for objects that implement the delta interface. You program the 
client-side methods to extract delta information for your entries and to apply 
received delta information.
-
-For more information, see [Delta Propagation 
API](delta-propagation-api.html#delta-propagation-api).
-
-**Prerequisites**
-
--   Study your object types and expected application behavior to determine 
which objects should use delta propagation. Delta propagation is not beneficial 
for all data and data modification scenarios. See [Exceptions and 
Limitations](performance.html#performance).
--   Decide whether to enable cloning. Cloning is disabled by default. See 
[cloning-enabled](delta-propagation-properties.html#delta-propagation-properties).
--   If you enable cloning, consider providing your own implementation, to 
optimize performance.
--   If you do not enable cloning, be sure to synchronize your delta code.
--   If you do not enable cloning, review all associated listener code for 
dependencies on the entry event old value. Without cloning, Geode modifies the 
entry in place and so loses its reference to the old value. For delta events, 
the `EntryEvent` methods to retrieve the old and new values both return the new 
value.
-
-**Procedure**
-
-For every class in which you want delta propagation, implement the delta 
interface and update your methods to support delta propagation. Exactly how you 
do this depends on your application and object needs, but these steps describe 
the basic approach.
-
-1.  Study the object contents to decide how to handle delta changes.
-
-Delta propagation has the same issues of distributed concurrency control 
as the distribution of full objects, but on a more detailed level. Some parts 
of your objects may be able to change independent of one another while others 
may always need to change together. Send deltas large enough to keep your data 
logically consistent. If, for example, field A and field B depend on each 
other, then your delta distributions should either update both fields or 
neither. As with regular updates, the fewer producers you have on a data 
region, the lower your likelihood of c

[38/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
--
diff --git 
a/geode-docs/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
 
b/geode-docs/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
new file mode 100644
index 000..d809635
--- /dev/null
+++ 
b/geode-docs/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
@@ -0,0 +1,129 @@
+---
+title:  Managing Data Entries
+---
+
+Program your applications to create, modify, and manage your cached data 
entries.
+
+
+**Note:**
+If you do not have the cache's `copy-on-read` attribute set to true, do not 
change the objects returned from the Java entry access methods. Instead, create 
a copy of the object, then modify the copy and pass it to the Java `put` 
method. Modifying a value in place bypasses the entire distribution framework 
provided by Geode, including cache listeners and expiration activities, and can 
produce undesired results.
+
+## Basic Create and Update
+
+To create or update an entry in the cache, use `Region.put`. For example:
+
+``` pre
+String name = ... 
+String value = ...  
+this.currRegion.put(name,value); 
+```
+
+**Note:**
+You can also use the `gfsh put` command to add entries to a region, and the 
`get` command to retrieve entries from a region. See 
[get](../../tools_modules/gfsh/command-pages/get.html) and 
[put](../../tools_modules/gfsh/command-pages/put.html) for more information.
+
+If you want only to create the entry (with a null value and with method 
failure if the entry already exists), use `Region.create` instead.
+
+## Batch Operations (getAll, putAll, removeAll)
+
+Geode provides three APIs to perform batch operations on multiple region 
entries:
+
+-   `Region.getAll`
+-   `Region.putAll`
+-   `Region.removeAll`
+
+The `getAll` method takes a collection of keys and returns a `Map` of values 
for the provided keys. If a given key does not exist in the region, then that 
key's value in the returned map will be null.
+
+The `putAll` method takes a `Map` of key-value pairs and puts them into the 
cache and distributes them in a single operation.
+
+**Example:**
+
+``` pre
+void putAll(String command) throws CacheException 
+{ 
+// Get Entry keys and values into Strings key1, ... keyN and value1, ... 
valueN 
+  Map map = new LinkedHashMap(); 
+  map.put(key1, value1)); 
+  ...
+  map.put(keyN, valueN));
+  this.currRegion.putAll(map); 
+}
+```
+
+The updates to the cache are done individually in the order in which they were 
placed in the `Map`. For partitioned regions, multiple events are sent as a 
single message to the primary buckets and then distributed to the secondary 
buckets.
+
+**Note:**
+The processing of maps with very many entries and/or very large data may 
affect system performance and cause cache update timeouts, especially if the 
region uses overflow or persistence to disk.
+
+The `removeAll` method takes a collection of keys and removes all of the 
entries for the specified keys from this region. This call performs the 
equivalent of calling`destroy(Object)` on this region once for each key in the 
specified collection. If an entry does not exist, then that key is skipped. An 
`EntryNotFoundException` is not thrown. This operation will be distributed to 
other caches if the region's scope is not set to `Scope.LOCAL`.
+
+## Safe Entry Modification
+
+When you get an entry value from the cache, by default, the retrieval methods 
return a direct reference to the cached object. This provides the value as 
quickly as possible, but also opens the cache to direct, in-place changes.
+
+**Note:**
+Do not directly modify cached values. Modifying a value in place bypasses the 
Geode distribution framework, including cache writers and listeners, expiration 
activities, and transaction management, and can produce undesired results.
+
+Always change your entries using copies of the retrieved objects—never 
directly modify the returned objects. You can do this in one of two ways:
+
+1.  Change the entry retrieval behavior for your cache by setting the cache 
attribute, `copy-on-read`, to true (the default is false).
+
+``` pre
+
+ ...
+
+```
+
+When `copy-on-read` is true, the entry access methods return copies of the 
entries. This protects you from inadvertently modifying in-place, but 
negatively impacts performance and memory consumption when copying is not 
needed.
+
+These entry access methods return an entry reference if `copy-on-read` is 
false and a copy of the entry if `copy-on-read` is true:
+
+`Region.get`
+result of `Region.put`
+`EntryEvent.getNewValue`
+`Region.values`
+`Region.Entry.getValue`
+`EntryEvent.getOldValue`
+`Query.select`
+
+2.  Create a copy of the returned object and work with that. For ob

[49/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/basic_config/the_cache/intro_cache_management.html.md.erb
--
diff --git a/basic_config/the_cache/intro_cache_management.html.md.erb 
b/basic_config/the_cache/intro_cache_management.html.md.erb
deleted file mode 100644
index 2d21a60..000
--- a/basic_config/the_cache/intro_cache_management.html.md.erb
+++ /dev/null
@@ -1,79 +0,0 @@

-title:  Introduction to Cache Management

-
-The cache provides in-memory storage and management for your data.
-
-
-You organize your data in the cache into *data regions*, each with its own 
configurable behavior. You store your data into your regions in key/value pairs 
called *data entries*. The cache also provides features like transactions, data 
querying, disk storage management, and logging. See the Javadocs for 
`org.apache.geode.cache.Cache`.
-
-You generally configure caches using the `gfsh` command-line utility or a 
combination of XML declarations and API calls. Geode loads and processes your 
XML declarations when you first create the cache.
-
-Geode has one cache type for managing server and peer caches and one for 
managing client caches. The cache server process automatically creates its 
server cache at startup. In your application process, the cache creation 
returns an instance of the server/peer or client cache. From that point on, you 
manage the cache through API calls in your application.
-
-## The Caching APIs
-
-Geode's caching APIs provide specialized behavior for different system member 
types and security settings.
-
--   **`org.apache.geode.cache.RegionService`**. Generally, you use the 
`RegionService` functionality through instances of `Cache` and `ClientCache`. 
You only specifically use instances of `RegionService` for limited-access users 
in secure client applications that service many users. The `RegionService` API 
provides access to existing cache data regions and to the standard query 
service for the cache. For client caches, queries are sent to the server tier. 
For server and peer caches, queries are run in the current cache and any 
available peers. `RegionService` is implemented by `GemFireCache`.
--   **`org.apache.geode.cache.GemFireCache`**. You do not specifically use 
instances of `GemFireCache`, but you use `GemFireCache` functionality in your 
instances of `Cache` and `ClientCache`. `GemFireCache` extends `RegionService` 
and adds general caching features like region attributes, disk stores for 
region persistence and overflow, and access to the underlying distributed 
system. `GemFireCache` is implemented by `Cache` and `ClientCache`.
--   **`org.apache.geode.cache.Cache`**. Use the `Cache` interface to manage 
server and peer caches. You have one `Cache` per server or peer process. The 
`Cache` extends `GemFireCache` and adds server/peer caching features like 
communication within the distributed system, region creation, transactions and 
querying, and cache server functionality.
--   **`org.apache.geode≈setting_cache_initializer.cache.ClientCache`**. Use 
the `ClientCache` interface to manage the cache in your clients. You have one 
`ClientCache` per client process. The `ClientCache` extends `GemFireCache` and 
adds client-specific caching features like client region creation, subscription 
keep-alive management for durable clients, querying on server and client tiers, 
and RegionService creation for secure access by multiple users within the 
client.
-
-## The Cache XML
-
-Your `cache.xml` must be formatted according to the product XML schema 
definition `cache-1.0.xsd`. The schema definition file is available in the 
product distribution at 
`$GEMFIRE/schemas/geode.apache.org/schema/cache/cache-1.0.xsd`.
-
-You use one format for peer and server caches and another for client caches.
-
-`cache.xml` for Peer/Server:
-
-``` pre
-
-http://geode.incubator.apache.org/schema/cache";
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
-xsi:schemaLocation="http://geode.incubator.apache.org/schema/cache 
http://geode.incubator.apache.org/schema/cache/cache-1.0.xsd";
-version="1.0”>
-...
-
-```
-
-`cache.xml` for Client:
-
-``` pre
-
-http://geode.incubator.apache.org/schema/cache";
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
-xsi:schemaLocation="http://geode.incubator.apache.org/schema/cache 
http://geode.incubator.apache.org/schema/cache/cache-1.0.xsd";
-version="1.0”>
-...
-
-```
-
-For more information on the `cache.xml` file, see 
[cache.xml](../../reference/topics/chapter_overview_cache_xml.html#cache_xml).
-
-## Create and Close a Cache
-
-Your system configuration and cache configuration are initialized when you 
start your member processes and create each member’s Geode cache. If you are 
using the cluster configuration service, member processes can pick up its cache 
configuration from the cluster or group's current configuration.

[69/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/querying_basics/chapter_overview.html.md.erb
--
diff --git a/geode-docs/developing/querying_basics/chapter_overview.html.md.erb 
b/geode-docs/developing/querying_basics/chapter_overview.html.md.erb
index 27611d0..328cc46 100644
--- a/geode-docs/developing/querying_basics/chapter_overview.html.md.erb
+++ b/geode-docs/developing/querying_basics/chapter_overview.html.md.erb
@@ -2,6 +2,23 @@
 title:  Querying
 ---
 
+
+
 Geode provides a SQL-like querying language called OQL that allows you to 
access data stored in Geode regions.
 
 Since Geode regions are key-value stores where values can range from simple 
byte arrays to complex nested objects, Geode uses a query syntax based on OQL 
(Object Query Language) to query region data. OQL is very similar to SQL, but 
OQL allows you to query complex objects, object attributes, and methods.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/querying_basics/comments_in_query_strings.html.md.erb
--
diff --git 
a/geode-docs/developing/querying_basics/comments_in_query_strings.html.md.erb 
b/geode-docs/developing/querying_basics/comments_in_query_strings.html.md.erb
index 5125609..d55bb3f 100644
--- 
a/geode-docs/developing/querying_basics/comments_in_query_strings.html.md.erb
+++ 
b/geode-docs/developing/querying_basics/comments_in_query_strings.html.md.erb
@@ -2,6 +2,23 @@
 title:  Comments in Query Strings
 ---
 
+
+
 Comment lines being with `--` (double dash). Comment blocks begin with `/*` 
and end with `*/`. For example:
 
 ``` pre

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/querying_basics/monitor_queries_for_low_memory.html.md.erb
--
diff --git 
a/geode-docs/developing/querying_basics/monitor_queries_for_low_memory.html.md.erb
 
b/geode-docs/developing/querying_basics/monitor_queries_for_low_memory.html.md.erb
index 3064b70..6d065c0 100644
--- 
a/geode-docs/developing/querying_basics/monitor_queries_for_low_memory.html.md.erb
+++ 
b/geode-docs/developing/querying_basics/monitor_queries_for_low_memory.html.md.erb
@@ -2,6 +2,23 @@
 title: Monitoring Queries for Low Memory
 ---
 
+
+
 
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/querying_basics/oql_compared_to_sql.html.md.erb
--
diff --git 
a/geode-docs/developing/querying_basics/oql_compared_to_sql.html.md.erb 
b/geode-docs/developing/querying_basics/oql_compared_to_sql.html.md.erb
index df13209..8b4d7f9 100644
--- a/geode-docs/developing/querying_basics/oql_compared_to_sql.html.md.erb
+++ b/geode-docs/developing/querying_basics/oql_compared_to_sql.html.md.erb
@@ -2,6 +2,23 @@
 title:  Advantages of OQL
 ---
 
+
+
 The following list describes some of the advantages of using an OQL-based 
querying language:
 
 -   You can query on any arbitrary object

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/querying_basics/performance_considerations.html.md.erb
--
diff --git 
a/geode-docs/developing/querying_basics/performance_considerations.html.md.erb 
b/geode-docs/developing/querying_basics/performance_considerations.html.md.erb
index b37e529..4e19250 100644
--- 
a/geode-docs/developing/querying_basics/performance_considerations.html.md.erb
+++ 
b/geode-docs/developing/querying_basics/performance_considerations.html.md.erb
@@ -2,6 +2,23 @@
 title:  Performance Considerations
 ---
 
+
+
 This topic covers considerations for improving query performance.
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/querying_basics/query_basics.html.md.erb
--
diff --git a/geode-docs/developing/querying_basics/query_basics.html.md.erb 
b/geode-docs/developing/querying_basics/query_basics.html.md.erb
index 89324f7..4121140 100644
--- a/geode-docs/developing/querying_basics/query_basics.html.md.erb
+++ b/geode-docs/developing/querying_basics/query_basics.html.md.erb
@@ -2,6 +2,23 @@
 title:  Basic Querying
 ---
 
+
+
 This section provides a high-level introduction to Geode querying such as 
building a query string and describes query language features.
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/developing/querying_basics/query_grammar_and_reserved_words.html.md.erb
--
diff --git 
a/geode-docs/developing/querying_basics/query_grammar_and_reserved_words.html.md.erb
 
b/geode-docs/developing/querying_basics/query_g

[56/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/dotnet-caching-api/object-lifetimes.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/dotnet-caching-api/object-lifetimes.html.md.erb 
b/geode-docs/nativeclient/dotnet-caching-api/object-lifetimes.html.md.erb
deleted file mode 100644
index b3acf2d..000
--- a/geode-docs/nativeclient/dotnet-caching-api/object-lifetimes.html.md.erb
+++ /dev/null
@@ -1,37 +0,0 @@

-title:  Object Lifetimes

-
-The .NET API provides a managed set of assemblies for the C++ API. The 
underlying C++ object will stay in memory until the .NET object is 
garbage-collected.
-
-The underlying C++ API employs reference counting using smart pointers for 
most classes. This means that all API operations with those objects return a 
reference to the underlying object and not a copy. Consequently, the underlying 
object will not be freed as long as the .NET application holds a reference to 
an object. In other words, the underlying object will stay in memory until the 
.NET object is garbage-collected. As long as a reference to an object is alive, 
the artifacts it maintains will also be alive.
-
-For example, as long as a `Region` object is not garbage-collected, then the 
destructor of the C++ native persistence manager (if any) for the region is not 
invoked.
-
-In the C++ API, the references to an object are reduced when the object goes 
out of scope for stack allocation, or is deleted explicitly for heap 
allocation. The object is destroyed when its reference count reaches zero. In 
the .NET API, the references are reduced when the object is garbage-collected 
or is explicitly disposed with the .NET `using` statement.
-
-Because a reference to the object is returned, any change to the object also 
immediately changes the object as stored internally. For example, if an object 
is put into the cache using `Region.Put`, a reference of the object is stored 
in the internal structures. If you modify the object, the internal object also 
changes. However, it is not distributed to other members of the distributed 
system until another `Region.Put` is done.
-
-To find out if a class is reference counted, look at the online API 
documentation for the class. If the class is wrapped by `UMWrap` or `SBWrap`, 
the class is reference counted.
-
-These are examples of classes that are reference counted:
-
--   `Cache`
--   `CacheStatistics`
--   `DistributedSystem`
--   `Properties`
--   `RegionAttributes`
--   `AttributesMutator`
--   `RegionEntry`
--   `Region`
--   `EntryEvent`
--   `RegionEvent`
-
-These are examples of classes that are not reference counted:
-
--   `AttributesFactory`
--   `DataInput`
--   `DataOutput`
--   `SystemProperties`
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/dotnet-caching-api/other-apis.html.md.erb
--
diff --git a/geode-docs/nativeclient/dotnet-caching-api/other-apis.html.md.erb 
b/geode-docs/nativeclient/dotnet-caching-api/other-apis.html.md.erb
deleted file mode 100644
index 89c34e4..000
--- a/geode-docs/nativeclient/dotnet-caching-api/other-apis.html.md.erb
+++ /dev/null
@@ -1,14 +0,0 @@

-title:  Property Collections and Logging APIs

-
-This section describes classes for property collections and logging.
-
--   **Properties** **class**. Provides a collection of properties, each of 
which is a key/value pair. Each key is a string, and the value can be a string 
or an integer.
--   **Log class**. Defines methods available to clients that need to write a 
log message to their Geode system shared log file. Any attempt to use an 
instance after its connection is disconnected throws a 
**NotConnectedException**. For any logged message the log file contains:
--   The log level of the message.
--   The time the message was logged.
--   The ID of the connection and thread that logged the message.
--   The message itself, possibly with an exception including its stack 
trace.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
 
b/geode-docs/nativeclient/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
deleted file mode 100644
index fa3bbf6..000
--- 
a/geode-docs/nativeclient/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
+++ /dev/null
@@ -1,30 +0,0 @@

-title:  Primary APIs

-
-These are the main APIs within `GemStone::GemFire::Cache::Generic` used for 
cache, region, and data entry management in Geode .NET. For detailed 
information about the APIs, see the .NET API documentation included in the 
product

[40/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/region_options/region_types.html.md.erb
--
diff --git a/developing/region_options/region_types.html.md.erb 
b/developing/region_options/region_types.html.md.erb
deleted file mode 100644
index 45908dd..000
--- a/developing/region_options/region_types.html.md.erb
+++ /dev/null
@@ -1,129 +0,0 @@

-title:  Region Types

-
-Region types define region behavior within a single distributed system. You 
have various options for region data storage and distribution.
-
-
-Within a Geode distributed system, you can define distributed regions and 
non-distributed regions, and you can define regions whose data is spread across 
the distributed system, and regions whose data is entirely contained in a 
single member.
-
-Your choice of region type is governed in part by the type of application you 
are running. In particular, you need to use specific region types for your 
servers and clients for effective communication between the two tiers:
-
--   Server regions are created inside a `Cache` by servers and are accessed by 
clients that connect to the servers from outside the server's distributed 
system. Server regions must have region type partitioned or replicated. Server 
region configuration uses the `RegionShortcut` enum settings.
--   Client regions are created inside a `ClientCache` by clients and are 
configured to distribute data and events between the client and the server 
tier. Client regions must have region type `local`. Client region configuration 
uses the `ClientRegionShortcut` enum settings.
--   Peer regions are created inside a `Cache`. Peer regions may be server 
regions, or they may be regions that are not accessed by clients. Peer regions 
can have any region type. Peer region configuration uses the `RegionShortcut` 
enum settings.
-
-When you configure a server or peer region using `gfsh` or with the 
`cache.xml` file, you can use *region shortcuts* to define the basic 
configuration of your region. A region shortcut provides a set of default 
configuration attributes that are designed for various types of caching 
architectures. You can then add additional configuration attributes as needed 
to customize your application. For more information and a complete reference of 
these region shortcuts, see [Region Shortcuts 
Reference](../../reference/topics/region_shortcuts_reference.html#reference_lt4_54c_lk).
-
-
-
-These are the primary configuration choices for each data region.
-
-
-
-
-
-
-
-
-
-Region Type
-Description
-Best suited for...
-
-
-
-
-Partitioned
-System-wide setting for the data set. Data is divided into buckets across 
the members that define the region. For high availability, configure redundant 
copies so each bucket is stored in multiple members with one member holding the 
primary.
-Server regions and peer regions
-
-Very large data sets
-High availability
-Write performance
-Partitioned event listeners and data loaders
-
-
-
-Replicated (distributed)
-Holds all data from the distributed region. The data from the distributed 
region is copied into the member replica region. Can be mixed with 
non-replication, with some members holding replicas and some holding 
non-replicas.
-Server regions and peer regions
-
-Read heavy, small datasets
-Asynchronous distribution
-Query performance
-
-
-
-Distributed non-replicated
-Data is spread across the members that define the region. Each member 
holds only the data it has expressed interest in. Can be mixed with 
replication, with some members holding replicas and some holding 
non-replicas.
-Peer regions, but not server regions and not client regions
-
-Asynchronous distribution
-Query performance
-
-
-
-Non-distributed (local)
-The region is visible only to the defining member.
-Client regions and peer regions
-
-Data that is not shared between applications
-
-
-
-
-
-## Partitioned Regions
-
-Partitioning is a good choice for very large server regions. Partitioned 
regions are ideal for data sets in the hundreds of gigabytes and beyond.
-
-**Note:**
-Partitioned regions generally require more JDBC connections than other region 
types because each member that hosts data must have a connection.
-
-Partitioned regions group your data into buckets, each of which is stored on a 
subset of all of the system members. Data location in the buckets does not 
affect the logical view - all members see the same logical data set.
-
-Use partitioning for:
-
--   **Large data sets**. Store data sets that are too large to fit into a 
single member, and all members will see the same logical data set. Partitioned 
regions divide the data into units of storage called buckets that are split 
across the members hosting the partitioned region data, so no member needs to 
host all of the region’s data. Geode provides dynamic redundancy recovery and 
rebalancing of partitioned regions, making them th

[58/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/cpp-caching-api/pdx_auto_serialization.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/cpp-caching-api/pdx_auto_serialization.html.md.erb 
b/geode-docs/nativeclient/cpp-caching-api/pdx_auto_serialization.html.md.erb
deleted file mode 100644
index 0bdda28..000
--- a/geode-docs/nativeclient/cpp-caching-api/pdx_auto_serialization.html.md.erb
+++ /dev/null
@@ -1,355 +0,0 @@

-title: Using Automatic PDX Serialization

-
-You can allow your native client C++ applications to automatically PDX 
serialize and deserialize domain objects without having to add any extra code 
by using the `pdxautoserializer` command line tool provided with the native 
client.
-
-When using the native client C++ API, you can automatically serialize and 
deserialize domain objects without making any code changes to those objects or 
having to implement a `PdxSerializer` or `PdxSerializable` interface and their 
related `fromData` and `toData` methods. The Geode native client includes a 
command-line utility, `pdxautoserializer`, that allows you to generate C++ code 
that will serialize your domain objects in the PDX format for you.
-
-## How to Use Automatic PDX 
Serialization
-
-**Prerequisites:**
-
--   Understand generally how to configure the Geode cache.
-
--   Understand how PDX serialization works and how to configure your 
application to use PdxSerializer.
-
-The procedure below uses the following sample class:
-
-``` pre
-class PortfolioPdx 
-{
-  private:
-int32_t id;
-char* pkid;
-PositionPdxPtr position1;
-PositionPdxPtr position2;
-CacheableHashMapPtr positions;
-char** names;
-int8_t* newVal;
-CacheableDatePtr creationDate;
-int8_t* arrayNull;
-int8_t* arrayZeroSize;
-  public:
-// CTOR
-// DTORS
-// Other Methods declarations
-```
-
-For each domain class you provide, all fields are considered for serialization 
except those defined as static or transient and those you explicitly exclude 
using macros.
-
-1.  Inherit your class from `gemfire::PdxSerializable`.
-
-``` pre
-class PortfolioPdx : public PdxSerializable
-```
-
-2.  Add the following method declarations in the public part of the class.
-
-``` pre
-const char* getClassName() const;
-virtual void toData(gemfire::PdxWriterPtr pw);
-virtual void fromData(gemfire::PdxReaderPtr pr);
-static PdxSerializable* createDeserializable();
-```
-
-3.  In your pre-build environment (for example in your **makefiles**), call 
`pdxautoserializer` as follows:
-
-``` pre
-/bin/pdxautoserializer.exe --outDir= 
/PortfolioPdx.hpp
-```
-
-4.  Include the generated file in your project and compile.
-
-The following is an example of a generated file:
-
-``` pre
-#include "PortfolioPdx.hpp"
-#include 
-#include 
-#include 
-namespace testobject
-{
-  void PortfolioPdx::toData(gemfire::PdxWriterPtr var)
-  {
-gemfire::PdxAutoSerializable::writePdxObject(var, "id", id);
-gemfire::PdxAutoSerializable::writePdxObject(var, "pkid", pkid);
-gemfire::PdxAutoSerializable::writePdxObject(var, "position1", position1);
-gemfire::PdxAutoSerializable::writePdxObject(var, "position2", position2);
-gemfire::PdxAutoSerializable::writePdxObject(var, "positions", positions);
-gemfire::PdxAutoSerializable::writePdxObject(var, "status", status);
-gemfire::PdxAutoSerializable::writePdxObject(var, "creationDate", 
creationDate);
-  }
-
-  void PortfolioPdx::fromData(PdxReaderPtr var)
-  {
-gemfire::PdxAutoSerializable::readPdxObject(var, "id", id);
-gemfire::PdxAutoSerializable::readPdxObject(var, "pkid", pkid);
-gemfire::PdxAutoSerializable::readPdxObject(var, "position1", position1);
-gemfire::PdxAutoSerializable::readPdxObject(var, "position2", position2);
-gemfire::PdxAutoSerializable::readPdxObject(var, "positions", positions);
-gemfire::PdxAutoSerializable::readPdxObject(var, "status", status);
-gemfire::PdxAutoSerializable::readPdxObject(var, "creationDate", 
creationDate);
-  }
-  
-  const char* PortfolioPdx::getClassName()  const
-  {
- return "PortfolioPdx";
-  }
-}
-```
-
-## Handling Arrays
-
-1.  Define the following macro in your header file:
-
-``` pre
-#define GFARRAYSIZE(x)
-```
-
-2.  Assuming that the following is the class member of type array:
-
-``` pre
-int8_t* newVal;
-```
-
-Then define a new variable which sets the length of the array:
-
-``` pre
-int32_t newValSize;
-```
-
-3.  Tag the new variable with the `GFARRAYSIZE` macro as follows:
-
-``` pre
-GFARRAYSIZE(newVal) int32_t newValSize;
-```
-
-## Using a Single Variable as Length for Multiple Arrays
-
-You can use the GFARRAYSIZES to have single length for multiple arrays.
-
-Define the GFARRAYSIZES macro as follows:
-
-``` pre
-#define GFARRA

[65/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/rest_apps/get_region_key_data.html.md.erb
--
diff --git a/geode-docs/rest_apps/get_region_key_data.html.md.erb 
b/geode-docs/rest_apps/get_region_key_data.html.md.erb
index f2df62d..8549ee0 100644
--- a/geode-docs/rest_apps/get_region_key_data.html.md.erb
+++ b/geode-docs/rest_apps/get_region_key_data.html.md.erb
@@ -2,6 +2,23 @@
 title:  GET /gemfire-api/v1/{region}/{key}
 ---
 
+
+
 Read data for a specific key in the region.
 
 ## Resource URL

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/rest_apps/get_region_keys.html.md.erb
--
diff --git a/geode-docs/rest_apps/get_region_keys.html.md.erb 
b/geode-docs/rest_apps/get_region_keys.html.md.erb
index 9089121..fa7bbd0 100644
--- a/geode-docs/rest_apps/get_region_keys.html.md.erb
+++ b/geode-docs/rest_apps/get_region_keys.html.md.erb
@@ -2,6 +2,23 @@
 title:  GET /gemfire-api/v1/{region}/keys
 ---
 
+
+
 List all keys for the specified region.
 
 ## Resource URL

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/rest_apps/get_regions.html.md.erb
--
diff --git a/geode-docs/rest_apps/get_regions.html.md.erb 
b/geode-docs/rest_apps/get_regions.html.md.erb
index 6633100..b8e6add 100644
--- a/geode-docs/rest_apps/get_regions.html.md.erb
+++ b/geode-docs/rest_apps/get_regions.html.md.erb
@@ -2,6 +2,23 @@
 title:  GET /gemfire-api/v1
 ---
 
+
+
 List all available resources (regions) in the Geode cluster.
 
 ## Resource URL

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/rest_apps/get_servers.html.md.erb
--
diff --git a/geode-docs/rest_apps/get_servers.html.md.erb 
b/geode-docs/rest_apps/get_servers.html.md.erb
index ea4a512..1ac585f 100644
--- a/geode-docs/rest_apps/get_servers.html.md.erb
+++ b/geode-docs/rest_apps/get_servers.html.md.erb
@@ -2,6 +2,23 @@
 title:  GET /gemfire-api/v1/servers
 ---
 
+
+
 Mechanism to obtain a list of all members in the distributed system that are 
running the REST API service.
 
 ## Resource URL

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/rest_apps/head_region_size.html.md.erb
--
diff --git a/geode-docs/rest_apps/head_region_size.html.md.erb 
b/geode-docs/rest_apps/head_region_size.html.md.erb
index 37dc8b0..3a83bb6 100644
--- a/geode-docs/rest_apps/head_region_size.html.md.erb
+++ b/geode-docs/rest_apps/head_region_size.html.md.erb
@@ -2,6 +2,23 @@
 title:  HEAD /gemfire-api/v1/{region}
 ---
 
+
+
 An HTTP HEAD request that returns region's size (number of entries) within the 
HEADERS, which is a response without the content-body. Region size is specified 
in the pre-defined header named "Resource-Count".
 
 ## Resource URL

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/rest_apps/ping_service.html.md.erb
--
diff --git a/geode-docs/rest_apps/ping_service.html.md.erb 
b/geode-docs/rest_apps/ping_service.html.md.erb
index 2467b26..d6339e3 100644
--- a/geode-docs/rest_apps/ping_service.html.md.erb
+++ b/geode-docs/rest_apps/ping_service.html.md.erb
@@ -2,6 +2,23 @@
 title:  \[HEAD | GET\] /gemfire-api/v1/ping
 ---
 
+
+
 Mechanism to check for REST API server and service availability.
 
 ## Resource URL

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/rest_apps/post_create_query.html.md.erb
--
diff --git a/geode-docs/rest_apps/post_create_query.html.md.erb 
b/geode-docs/rest_apps/post_create_query.html.md.erb
index 9e4743d..9062948 100644
--- a/geode-docs/rest_apps/post_create_query.html.md.erb
+++ b/geode-docs/rest_apps/post_create_query.html.md.erb
@@ -2,6 +2,23 @@
 title:  POST /gemfire-api/v1/queries?id=&q=
 ---
 
+
+
 Create (prepare) the specified parameterized query and assign the 
corresponding ID for lookup.
 
 ## Resource URL

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/rest_apps/post_execute_functions.html.md.erb
--
diff --git a/geode-docs/rest_apps/post_execute_functions.html.md.erb 
b/geode-docs/rest_apps/post_execute_functions.html.md.erb
index ee7064c..32d8cd7 100644
--- a/geode-docs/rest_apps/post_execute_functions.html.md.erb
+++ b/geode-docs/rest_apps/post_execute_functions.html.md.erb
@@ -2,6 +2,23 @@
 title:  POST /gemfire-api/v1/functions/{functionId}
 ---
 
+
+
 Execute Geode function on entire cluster or on a specified region, members and 
memb

[41/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
--
diff --git 
a/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
 
b/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
deleted file mode 100644
index a834b60..000
--- 
a/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
+++ /dev/null
@@ -1,62 +0,0 @@

-title:  Using Indexes on Equi-Join Queries using Multiple Regions

-
-To query across multiple regions, identify all equi-join conditions. Then, 
create as few indexes for the equi-join conditions as you can while still 
joining all regions.
-
-
-If there are equi-join conditions that redundantly join two regions (in order 
to more finely filter the data, for example), then creating redundant indexes 
for these joins will negatively impact performance. Create indexes only on one 
equi-join condition for each region pair.
-
-In this example query:
-
-``` pre
-SELECT DISTINCT * 
-FROM /investors inv, /securities sc, /orders or, 
-inv.ordersPlaced inv_op, or.securities or_sec 
-WHERE inv_op.orderID = or.orderID 
-AND or_sec.secID = sc.secID
-```
-
-All conditions are required to join the regions, so you would create four 
indexes, two for each equi-join condition:
-
-| FROM clause  | Indexed expression |
-|--||
-| /investors inv, inv.ordersPlaced inv\_op | inv\_op.orderID|
-| /orders or, or.securities or\_sec| or.orderID |
-
-| FROM clause   | Indexed expression |
-|---||
-| /orders or, or.securities or\_sec | or\_sec.secID  |
-| /securities sc| sc.secID   |
-
-Adding another condition to the example:
-
-``` pre
-SELECT DISTINCT * 
-FROM /investors inv, /securities sc, /orders or, 
-inv.ordersPlaced inv_op, or.securities or_sec, sc.investors sc_invs 
-WHERE inv_op.orderID = or.orderID 
-AND or_sec.secID = sc.secID
-AND inv.investorID = sc_invs.investorID
-```
-
-You would still only want to use four indexes in all, as that's all you need 
to join all of the regions. You would need to choose the most performant two of 
the following three index pairs:
-
-| FROM clause  | Indexed expression |
-|--||
-| /investors inv, inv.ordersPlaced inv\_op | inv\_op.orderID|
-| /orders or, or.securities or\_sec| or.orderID |
-
-| FROM clause   | Indexed expression |
-|---||
-| /orders or, or.securities or\_sec | or\_sec.secID  |
-| /securities sc, sc.investors sc\_invs | sc.secID   |
-
-| FROM clause  | Indexed expression  |
-|--|-|
-| /investors inv, inv.ordersPlaced inv\_op | inv.investorID  |
-| /securities sc, sc.investors sc\_invs| sc\_invs.investorID |
-
-The most performant set is that which narrows the data to the smallest result 
set possible. Examine your data and experiment with the three index pairs to 
see which provides the best performance.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/query_select/aggregates.html.md.erb
--
diff --git a/developing/query_select/aggregates.html.md.erb 
b/developing/query_select/aggregates.html.md.erb
deleted file mode 100644
index 1a4e0aa..000
--- a/developing/query_select/aggregates.html.md.erb
+++ /dev/null
@@ -1,92 +0,0 @@

-title:  OQL Aggregate Functions

-
-The aggregate functions 
-```MIN```,
-```MAX```,
-```AVG```,
-```AVG``` over a DISTINCT expression,
-```SUM``` over a DISTINCT expression,
-```COUNT```, and
-```COUNT``` over a DISTINCT expression
-are supported.
-The ```GROUP BY``` extension is also supported where appropriate.
-
-The ```MIN``` function returns the smallest of the selected
-expression.
-The type of the expression must evaluate to a 
-```java.lang.Comparable```.
-
-The ```MAX``` function returns the largest of the selected
-expression.
-The type of the expression must evaluate to a 
-```java.lang.Comparable```.
-
-The ```AVG``` function returns the arithmetic mean of the set
-formed by the selected expression.
-The type of the expression must evaluate to a 
-```java.lang.Number```.
-For partitioned regions,
-each node's buckets provide both a sum and the number of elements
-to the node executing the query,
-such that a correct average may be computed.
-
-The ```AVG``` function where the DISTINCT modifier is a

[61/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

GEODE-1952: removed native client docs, set aside until native client code is 
merged in (see GEODE-1964)


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/381d0faa
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/381d0faa
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/381d0faa

Branch: refs/heads/feature/GEODE-1952-2
Commit: 381d0faaedeba3c8079a03a4da971615d9762da5
Parents: ccc2fbd
Author: Dave Barnes 
Authored: Tue Oct 4 17:15:37 2016 -0700
Committer: Dave Barnes 
Committed: Tue Oct 4 17:15:37 2016 -0700

--
 .../about_native_client_users_guide.html.md.erb |  83 -
 .../cache-init-file/cache-dtd.html.md.erb   | 267 --
 .../chapter-overview.html.md.erb|  21 --
 .../example-cache-file.html.md.erb  |  48 ---
 .../cache-init-file/file-basics.html.md.erb |  18 -
 .../client-cache/accessing-entries.html.md.erb  |  38 --
 .../adding-entries-to-cache.html.md.erb |  32 --
 .../application-plugins.html.md.erb | 262 --
 .../client-cache/cache-management.html.md.erb   |  29 --
 .../client-cache/cache-ownership.html.md.erb|  11 -
 .../client-cache/caches.html.md.erb |  27 --
 .../client-cache/caching-apis.html.md.erb   |  28 --
 .../client-cache/caching-enabled.html.md.erb|  27 --
 .../client-cache/chapter-overview.html.md.erb   |  37 --
 .../client-to-server-connection.html.md.erb |  39 --
 .../client-cache/closing-cache.html.md.erb  |  11 -
 .../concurrency-checks-enabled.html.md.erb  |  18 -
 .../client-cache/concurrency-level.html.md.erb  |  18 -
 .../consistency_checking_in_regions.html.md.erb |  19 -
 .../controlling-cache-size.html.md.erb  |  20 --
 .../create-access-cache.html.md.erb |  53 ---
 .../declarative-region-creation.html.md.erb |  38 --
 .../client-cache/disk-policy.html.md.erb|  34 --
 .../client-cache/entries.html.md.erb|  20 --
 .../expiration-attributes.html.md.erb   |  65 
 .../getting-the-region-size.html.md.erb |  11 -
 .../client-cache/initial-capacity.html.md.erb   |  15 -
 .../invalidating-cached-entries.html.md.erb |  16 -
 .../invalidating-region.html.md.erb |  25 --
 .../client-cache/load-factor.html.md.erb|  15 -
 .../client-cache/lru-entries-limit.html.md.erb  |  31 --
 .../managing-lifetime-cached-object.html.md.erb |  48 ---
 .../notification-for-operations.html.md.erb |  16 -
 .../overview-client-cache.html.md.erb   |  24 --
 .../persistence-manager.html.md.erb | 224 
 .../programmatic-region-creation.html.md.erb|  24 --
 .../client-cache/region-access.html.md.erb  |  21 --
 .../region-attributes-desc.html.md.erb  |  39 --
 .../client-cache/region-attributes.html.md.erb  |  35 --
 .../client-cache/region-shortcuts.html.md.erb   |  63 
 .../client-cache/regions.html.md.erb|  32 --
 ...registering-interest-for-entries.html.md.erb |  93 -
 .../requirements-for-distrib.html.md.erb|  11 -
 .../specify-region-attributes.html.md.erb   |   9 -
 .../client-cache/troubleshooting.html.md.erb|  41 ---
 .../client-cache/updating-entries.html.md.erb   |  16 -
 .../using-serverkeys-to-retrieve.html.md.erb|  32 --
 .../using-thread-safety.html.md.erb |  13 -
 .../common/images/10-Continuous_Querying-1.gif  | Bin 7411 -> 0 bytes
 .../common/images/10-Continuous_Querying-3.gif  | Bin 8611 -> 0 bytes
 .../common/images/6-DotNet_API-1.gif| Bin 4218 -> 0 bytes
 .../common/images/7-Preserving_Data-2.gif   | Bin 13146 -> 0 bytes
 .../common/images/client-cache-data-flow.gif| Bin 4422 -> 0 bytes
 .../common/images/client-cache-plugins-run.gif  | Bin 4340 -> 0 bytes
 .../common/images/client-server-arch.gif| Bin 7198 -> 0 bytes
 .../common/images/data-dep-func-from-client.gif | Bin 10336 -> 0 bytes
 .../common/images/data-dep-func-with-filter.gif | Bin 11062 -> 0 bytes
 .../images/data-indep-func-from-client.gif  | Bin 8105 -> 0 bytes
 .../delta-propagation-in-client-server.gif  | Bin 7115 -> 0 bytes
 .../common/images/delta-propagation.gif | Bin 8817 -> 0 bytes
 .../common/images/ha-data-dep-func.gif  | Bin 14684 -> 0 bytes
 .../common/images/native-client-overview.gif| Bin 6421 -> 0 bytes
 .../images/security-client-connections.gif  | Bin 8300 -> 0 bytes
 .../common/images/xact-run-from-client.gif  | Bin 9928 -> 0 bytes
 .../about-connection-pools.html.md.erb  |  20 --
 .../about-server-locators.html.md.erb   |  17 -
 .../client-load-balancing.html.md.erb   |  21 --
 ...iguring-pools-attributes-example.html.md.erb | 156 
 .../configuring-pools.html.md.erb   |  25 --
 .../connection-pools.html.md.erb   

[53/76] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/remote-querying/96-progexamples/3-query-code-examples-structset.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/remote-querying/96-progexamples/3-query-code-examples-structset.html.md.erb
 
b/geode-docs/nativeclient/remote-querying/96-progexamples/3-query-code-examples-structset.html.md.erb
deleted file mode 100644
index d4c2ba3..000
--- 
a/geode-docs/nativeclient/remote-querying/96-progexamples/3-query-code-examples-structset.html.md.erb
+++ /dev/null
@@ -1,192 +0,0 @@

-title:  Query Code Samples Returning StructSet

-
-These examples return a `StructSet` for built-in and user-defined data types, 
`Struct` objects, and collections.
-
-## Query Returning a StructSet for a Built-In Data Type
-
-``` pre
-QueryServicePtr qrySvcPtr = cachePtr->getQueryService("examplePool");
-const char * querystring =
-   "SELECT DISTINCT ID, pkid, status, getType FROM /portfolios";
-QueryPtr query = qrySvcPtr->newQuery(querystring);
-//specify 10 seconds for the query timeout period
-SelectResultsPtr results = query->execute(10);
-if (results == NULLPTR)
-{
-   printf( "\nNo results returned from the server");
-}
-//obtaining a handle to resultset
-StructSetPtr ss(dynamic_cast (results.ptr()));
-if (ss == NULLPTR)
-{
-   printf ("\nStructSet is not obtained \n");
-   return;
-}
-//iterating through the resultset using indexes.
-for ( int32_t row=0; row < ss->size(); row++)
-{
-   Struct * siptr = (Struct*) dynamic_cast ( ((*ss)[row]).ptr() );
-   if (siptr == NULL)
-   {
-  printf("\nstruct is empty \n");
-  continue;
- 
-}
-//iterate through fields now
-for( int32_t field=0; field < siptr->length(); field++)
-{
-   SerializablePtr fieldptr((*siptr)[field]);
-   if(fieldptr == NULLPTR )
-   {
-  printf("\nnull data received\n");
-   }
-   CacheableStringPtr
-  str(dynamic_cast(fieldptr.ptr()));
-   if (str == NULLPTR)
-   {
-  printf("\n field is of some other type \n");
-   }
-   else
-   {
-  printf("\n Data for %s is %s ", siptr->getFieldName(field), 
str->asChar() );
-   }
-} //end of columns
- } // end of rows
-```
-
-## Returning Struct Objects
-
-``` pre
-QueryServicePtr qrySvcPtr = cachePtr->getQueryService("examplePool");
-const char * querystring =
-   "SELECT DISTINCT derivedProjAttrbts, key: p.key FROM "
-   "/Portfolios.entries p, (SELECT DISTINCT x.ID, myPos.secId FROM "
-   "/Portfolios x, x.positions.values AS myPos) derivedProjAttrbts WHERE "
-   "p.value.ID = derivedProjAttrbts.ID AND derivedProjAttrbts.secId = 'IBM'";
-QueryPtr query = qrySvcPtr->newQuery(querystring);
-//specify 10 seconds for the query timeout period
-SelectResultsPtr results = query->execute(10);
-if (results == NULLPTR)
-{
-   printf( "\nNo results returned from the server");
-}
-//obtaining a handle to resultset
-StructSetPtr ss(dynamic_cast (results.ptr()));
-if (ss == NULLPTR)
-{
-   printf ("\nStructSet is not obtained \n");
-   return;
-}
-//iterating through the resultset using indexes.
-for (int32_t row=0; row < ss->size(); row++)
-{
-   Struct * siptr = (Struct*) dynamic_cast ( ((*ss)[row]).ptr() );
-   if (siptr == NULL) { printf("\nstruct is empty \n"); }
-   //iterate through fields now
-   for (int32_t field=0; field < siptr->length(); field++) {
-   SerializablePtr fieldptr((*siptr)[field]);
-   if (fieldptr == NULLPTR )
-   {
-  printf("\nnull data received\n");
-   }
-   CacheableStringPtr
-  str(dynamic_cast(fieldptr.ptr()));
-   if (str != NULLPTR) {
-  printf("\n Data for %s is %s ", siptr->getFieldName(field),
-  str->asChar() );
-   }
-   else
-   {
-  StructPtr simpl(dynamic_cast (fieldptr.ptr()));
-  if (simpl == NULLPTR)
-  {
-  printf("\n field is of some other type \n"); continue;
-  }
-  printf( "\n struct received %s \n", siptr->getFieldName(field) );
-  for (int32_t inner_field=0; inner_field < simpl->length(); 
inner_field++)
-  {
-  SerializablePtr innerfieldptr((*simpl)[inner_field]);
-  if (innerfieldptr == NULLPTR)
-  {
-  printf("\nfield of struct is NULL\n");
-  }
-  CacheableStringPtr str(dynamic_cast
- (innerfieldptr.ptr()));
-  if (str != NULLPTR)
-  {
-  printf("\n Data for %s is %s ",
-  simpl->getFieldName(inner_field),str->asChar() );
-  }
-  else
-  {
-  printf("\n some other object type inside struct\n");
-  }
-   }
-}
-} //end of columns
- }//end of rows
-```
-
-## Returning Collections
-
-``` pre
-QueryServicePtr qrySvcPtr = cachePtr->getQueryS

[36/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/configuring/running/running_the_cacheserver.html.md.erb
--
diff --git a/geode-docs/configuring/running/running_the_cacheserver.html.md.erb 
b/geode-docs/configuring/running/running_the_cacheserver.html.md.erb
new file mode 100644
index 000..9de1189
--- /dev/null
+++ b/geode-docs/configuring/running/running_the_cacheserver.html.md.erb
@@ -0,0 +1,182 @@
+---
+title:  Running Geode Server Processes
+---
+
+A Geode server is a process that runs as a long-lived, configurable member of 
a client/server system.
+
+
+The Geode server is used primarily for hosting long-lived data regions and for 
running standard Geode processes such as the server in a client/server 
configuration. You can start and stop servers using the following methods:
+
+-   The `gfsh` tool allows you to manage Geode server processes from the 
command line.
+-   You can also start, stop and manage the Geode servers through the 
`org.apache.geode.distributed.ServerLauncher` API. The `ServerLauncher` API can 
only be used for Geode Servers that were started with `gfsh` or with the 
`ServerLauncher` class itself. See the JavaDocs for additional specifics on 
using the `ServerLauncher` API.
+
+## Default Server Configuration and Log Files
+
+The `gfsh` utility uses a working directory for its configuration files and 
log files. These are the defaults and configuration options:
+
+-   When you start a standalone server using `gfsh`, `gfsh` will automatically 
load the required JAR files `$GEMFIRE/lib/server-dependencies.jar` and 
`$JAVA_HOME/lib/tools.jar` into the CLASSPATH of the JVM process. If you start 
a standalone server using the ServerLauncher API, you must specify 
`$GEMFIRE/lib/server-dependencies.jar` inside your command to launch the 
process. For more information on CLASSPATH settings in Geode, see [Setting Up 
the CLASSPATH](../../getting_started/setup_classpath.html).
+-   Servers are configured like any other Geode process, with 
`gemfire.properties` and shared cluster configuration files. It is not 
programmable except through application plug-ins. Typically, you provide the 
`gemfire.properties` file and the `gfsecurity.properties` file (if you are 
using a separate, restricted access security settings file). You can also 
specify a `cache.xml` file in the cache server’s working directory.
+-   By default, a new server started with `gfsh` receives its initial cache 
configuration from the cluster configuration service, assuming the locator is 
running the cluster configuration service. If you specify a group when starting 
the server, the server also receives configurations that apply to a group. The 
shared configuration consists of `cache.xml` files, `gemfire.properties` files, 
and deployed jar files. You can disable use of the cluster configuration 
service by specifying `--use-cluster-configuration=false` when starting the 
server using `gfsh`.
+
+See [Overview of the Cluster Configuration 
Service](../cluster_config/gfsh_persist.html#concept_r22_hyw_bl).
+
+-   If you are using the Spring Framework, you can specify a Spring 
ApplicationContext XML file when starting up your server in `gfsh` by using the 
`--spring-xml-location` command-line option. This option allows you to 
bootstrap your Geode server process with your Spring application's 
configuration. See [Spring 
documentation](http://docs.spring.io/spring/docs/3.2.x/spring-framework-reference/html/resources.html#resources-app-ctx)
 for more information on this file.
+-   For logging output, log file output defaults to `server_name.log` in the 
cache server's working directory. If you restart a server with the same server 
name, the existing *server\_name*.log file is automatically renamed for you 
(for example, `server1-01-01.log` or `server1-02-01.log`). You can modify the 
level of logging details in this file by specifying a level in the 
`--log-level` argument when starting up the server.
+-   By default, the server will start in a subdirectory (named after the 
server's specified `--name`) under the directory where `gfsh` is executed. This 
subdirectory is considered the current working directory. You can also specify 
a different working directory when starting the cache server in `gfsh`.
+-   By default, a server process that has been shutdown and disconnected due 
to a network partition event or member unresponsiveness will restart itself and 
automatically try to reconnect to the existing distributed system. See 
[Handling Forced Cache Disconnection Using 
Autoreconnect](../../managing/autoreconnect/member-reconnect.html#concept_22EE6DDE677F4E8CAF5786E17B4183A9)
 for more details.
+-   You can pass JVM parameters to the server's JVM by using the 
`--J=-Dproperty.name=value` upon server startup. These parameters can be Java 
properties or Geode configuration properties such as `gemfire.jmx-manager`. For

[43/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/outside_data_sources/sync_outside_data.html.md.erb
--
diff --git a/developing/outside_data_sources/sync_outside_data.html.md.erb 
b/developing/outside_data_sources/sync_outside_data.html.md.erb
deleted file mode 100644
index 54e4f48..000
--- a/developing/outside_data_sources/sync_outside_data.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@

-title:  Keeping the Cache in Sync with Outside Data Sources

-
-Keep your distributed cache in sync with an outside data source by programming 
and installing application plug-ins for your region.
-
--   **[Overview of Outside Data 
Sources](../../developing/outside_data_sources/chapter_overview.html)**
-
-Apache Geode has application plug-ins to read data into the cache and 
write it out.
-
--   **[How Data Loaders 
Work](../../developing/outside_data_sources/how_data_loaders_work.html)**
-
-By default, a region has no data loader defined. Plug an 
application-defined loader into any region by setting the region attribute 
cache-loader on the members that host data for the region.
-
--   **[Implement a Data 
Loader](../../developing/outside_data_sources/implementing_data_loaders.html)**
-
-Program a data loader and configure your region to use it.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/partitioned_regions/chapter_overview.html.md.erb
--
diff --git a/developing/partitioned_regions/chapter_overview.html.md.erb 
b/developing/partitioned_regions/chapter_overview.html.md.erb
deleted file mode 100644
index 56e65e1..000
--- a/developing/partitioned_regions/chapter_overview.html.md.erb
+++ /dev/null
@@ -1,43 +0,0 @@

-title:  Partitioned Regions

-
-In addition to basic region management, partitioned regions include options 
for high availability, data location control, and data balancing across the 
distributed system.
-
--   **[Understanding 
Partitioning](../../developing/partitioned_regions/how_partitioning_works.html)**
-
-To use partitioned regions, you should understand how they work and your 
options for managing them.
-
--   **[Configuring Partitioned 
Regions](../../developing/partitioned_regions/managing_partitioned_regions.html)**
-
-Plan the configuration and ongoing management of your partitioned region 
for host and accessor members and configure the regions for startup.
-
--   **[Configuring the Number of Buckets for a Partitioned 
Region](../../developing/partitioned_regions/configuring_bucket_for_pr.html)**
-
-Decide how many buckets to assign to your partitioned region and set the 
configuration accordingly.
-
--   **[Custom-Partitioning and Colocating 
Data](../../developing/partitioned_regions/overview_custom_partitioning_and_data_colocation.html)**
-
-You can customize how Apache Geode groups your partitioned region data 
with custom partitioning and data colocation.
-
--   **[Configuring High Availability for Partitioned 
Regions](../../developing/partitioned_regions/overview_how_pr_ha_works.html)**
-
-By default, Apache Geode stores only a single copy of your partitioned 
region data among the region's data stores. You can configure Geode to maintain 
redundant copies of your partitioned region data for high availability.
-
--   **[Configuring Single-Hop Client Access to Server-Partitioned 
Regions](../../developing/partitioned_regions/overview_how_pr_single_hop_works.html)**
-
-Single-hop data access enables the client pool to track where a 
partitioned region’s data is hosted in the servers. To access a single entry, 
the client directly contacts the server that hosts the key, in a single hop.
-
--   **[Rebalancing Partitioned Region 
Data](../../developing/partitioned_regions/rebalancing_pr_data.html)**
-
-In a distributed system with minimal contention to the concurrent threads 
reading or updating from the members, you can use rebalancing to dynamically 
increase or decrease your data and processing capacity.
-
--   **[Checking Redundancy in Partitioned 
Regions](../../developing/partitioned_regions/checking_region_redundancy.html)**
-
-Under some circumstances, it can be important to verify that your 
partitioned region data is redundant and that upon member restart, redundancy 
has been recovered properly across partitioned region members.
-
--   **[Moving Partitioned Region Data to Another 
Member](../../developing/partitioned_regions/moving_partitioned_data.html)**
-
-You can use the `PartitionRegionHelper` `moveBucketByKey` and `moveData` 
methods to explicitly move partitioned region data from one member to another.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/partitioned_regions/checking_region_redundancy.html.md.erb

[37/76] [abbrv] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/basic_config/the_cache/setting_cache_initializer.html.md.erb
--
diff --git 
a/geode-docs/basic_config/the_cache/setting_cache_initializer.html.md.erb 
b/geode-docs/basic_config/the_cache/setting_cache_initializer.html.md.erb
new file mode 100644
index 000..20cc2c6
--- /dev/null
+++ b/geode-docs/basic_config/the_cache/setting_cache_initializer.html.md.erb
@@ -0,0 +1,59 @@
+---
+title:  Launching an Application after Initializing the Cache
+---
+
+You can specify a callback application that is launched after the cache 
initialization.
+
+By specifying an `` element in your cache.xml file, you can 
trigger a callback application, which is run after the cache has been 
initialized. Applications that use the cacheserver script to start up a server 
can also use this feature to hook into a callback application. To use this 
feature, you need to specify the callback class within the `` 
element. This element should be added to the end of your `cache.xml` file.
+
+You can specify the `` element for either server caches or client 
caches.
+
+The callback class must implement the `Declarable` interface. When the 
callback class is loaded, its `init` method is called, and any parameters 
defined in the `` element are passed as properties.
+
+The following is an example specification.
+
+In cache.xml:
+
+``` pre
+
+   MyInitializer
+  
+ 2
+  
+
+```
+
+Here's the corresponding class definition:
+
+``` pre
+ 
+import org.apache.geode.cache.Declarable;
+
+public class MyInitializer implements Declarable {
+   public void init(Properties properties) {
+  System.out.println(properties.getProperty("members"));
+   }
+}
+```
+
+The following are some additional real-world usage scenarios:
+
+1.  Start a SystemMembershipListener
+
+``` pre
+
+   TestSystemMembershipListener
+
+```
+
+2.  Write a custom tool that monitors cache resources
+
+``` pre
+
+   ResourceMonitorCacheXmlLoader
+
+```
+
+Any singleton or timer task or thread can be instantiated and started using 
the initializer element.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
--
diff --git 
a/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb 
b/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
new file mode 100644
index 000..76d5066
--- /dev/null
+++ b/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
@@ -0,0 +1,22 @@
+---
+title:  Options for Configuring the Cache and Data Regions
+---
+
+To populate your Apache Geode cache and fine-tune its storage and distribution 
behavior, you need to define cached data regions and provide custom 
configuration for the cache and regions.
+
+
+Cache configuration properties define:
+
+-   Cache-wide settings such as disk stores, communication timeouts, and 
settings designating the member as a server
+-   Cache data regions
+
+Configure the cache and its data regions through one or more of these methods:
+
+-   Through a persistent configuration that you define when issuing commands 
that use the gfsh command line utility. `gfsh` supports the administration, 
debugging, and deployment of Apache Geode processes and applications. You can 
use gfsh to configure regions, locators, servers, disk stores, event queues, 
and other objects.
+
+As you issue commands, gfsh saves a set of configurations that apply to 
the entire cluster and also saves configurations that only apply to defined 
groups of members within the cluster. You can re-use these configurations to 
create a distributed system. See [Overview of the Cluster Configuration 
Service](../../configuring/cluster_config/gfsh_persist.html).
+
+-   Through declarations in the XML file named in the `cache-xml-file` 
`gemfire.properties` setting. This file is generally referred to as the 
`cache.xml` file, but it can have any name. See 
[cache.xml](../../reference/topics/chapter_overview_cache_xml.html#cache_xml).
+-   Through application calls to the `org.apache.geode.cache.CacheFactory`, 
`org.apache.geode.cache.Cache` and `org.apache.geode.cache.Region` APIs.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/configuring/chapter_overview.html.md.erb
--
diff --git a/geode-docs/configuring/chapter_overview.html.md.erb 
b/geode-docs/configuring/chapter_overview.html.md.erb
new file mode 100644
index 000..8026e72
--- /dev/null
+++ b/geode-docs/configuring/chapter_overview.html.md.erb
@@ -0,0 +1,67 @@
+---
+title:  Configuring and Running a Cluster
+---
+
+You use the `gfsh` command-line utility to configure your Apache Geode cluster 

[67/76] [abbrv] incubator-geode git commit: GEODE-1952: Add Apache license to all geode-docs erb files

[kmiller]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/management/programming_example.html.md.erb
--
diff --git a/geode-docs/managing/management/programming_example.html.md.erb 
b/geode-docs/managing/management/programming_example.html.md.erb
index 45e4ac5..17cfcd4 100644
--- a/geode-docs/managing/management/programming_example.html.md.erb
+++ b/geode-docs/managing/management/programming_example.html.md.erb
@@ -2,6 +2,23 @@
 title:  Management and Monitoring Programming Examples
 ---
 
+
+
 One example demonstrates the use of an MBean server to manage and monitor a 
node in a distributed system, and the other example acts as the managed node.
 
 ## JMX Manager Node Example

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb
--
diff --git a/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb 
b/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb
index 09f868b..adc10c9 100644
--- a/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb
+++ b/geode-docs/managing/monitor_tune/cache_consistency.html.md.erb
@@ -2,6 +2,23 @@
 title:  Maintaining Cache Consistency
 ---
 
+
+
 Maintaining data consistency between caches in a distributed Geode system is 
vital for ensuring its functional integrity and preventing data loss.
 
 ## General 
Guidelines

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb
--
diff --git a/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb 
b/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb
index da69f00..db09945 100644
--- a/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb
+++ b/geode-docs/managing/monitor_tune/chapter_overview.html.md.erb
@@ -2,6 +2,23 @@
 title:  Performance Tuning and Configuration
 ---
 
+
+
 A collection of tools and controls allow you to monitor and adjust Apache 
Geode performance.
 
 -   **[Improving Geode Performance on 
vSphere](../../managing/monitor_tune/gemfire_performance_on_vsphere.html)**

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb
--
diff --git 
a/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb 
b/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb
index 249a7dd..2be5502 100644
--- 
a/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb
+++ 
b/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere.html.md.erb
@@ -2,6 +2,23 @@
 title:  Improving Geode Performance on vSphere
 ---
 
+
+
 This topic provides guidelines for tuning vSphere virtualized environments 
that host Apache Geode deployments.
 
 Without tuning, Geode can suffer a performance drop in virtual environments, 
including the VMware vSphere virtual platform.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb
--
diff --git 
a/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb
 
b/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb
index d8b7248..b5cb8a2 100644
--- 
a/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb
+++ 
b/geode-docs/managing/monitor_tune/gemfire_performance_on_vsphere_guidelines.html.md.erb
@@ -1,6 +1,23 @@
 ---
 title: Operating System Guidelines
 ---
+
+
 
 
 

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/6bea8204/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb
--
diff --git 
a/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb 
b/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb
index 3574cc7..ba823c6 100644
--- a/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb
+++ b/geode-docs/managing/monitor_tune/multicast_communication.html.md.erb
@@ -2,6 +2,23 @@
 title:  Multicast Communication
 ---
 
+
+
 You can make configuration adjustments to improve the UDP multicast 
performance of peer-to-peer communication in your Geode system.
 
 Before you begin, you should understand Geode [Basic Configuration and 
Programming](../../basic_config/book_intro.html). See also the general 
communication tuning and UDP tuning covered in [Socket 
Communication](socket_communication.html) and [UDP 
Communication](udp_communication.html#udp_comm).

http://g

incubator-geode git commit: fixed formatting. Removed class sync on rmqFactory

[dschneider]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEM-983 7f920879a -> 8165e6047


fixed formatting. Removed class sync on rmqFactory


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/8165e604
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/8165e604
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/8165e604

Branch: refs/heads/feature/GEM-983
Commit: 8165e60471f99bd9d078f523cf54355891dd7d12
Parents: 7f92087
Author: Darrel Schneider 
Authored: Wed Oct 12 11:37:41 2016 -0700
Committer: Darrel Schneider 
Committed: Wed Oct 12 11:37:41 2016 -0700

--
 .../geode/internal/cache/GemFireCacheImpl.java  | 121 ---
 1 file changed, 52 insertions(+), 69 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/8165e604/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
--
diff --git 
a/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
 
b/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
index 9da3e79..0e23aaa 100755
--- 
a/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
+++ 
b/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
@@ -843,7 +843,7 @@ public class GemFireCacheImpl implements InternalCache, 
ClientCache, HasCachePer
   
   this.cqService = CqServiceProvider.create(this);
 
-  initReliableMessageQueueFactory();
+  this.rmqFactory = new ReliableMessageQueueFactoryImpl();
 
   // Create the CacheStatistics
   this.cachePerfStats = new CachePerfStats(system);
@@ -1678,40 +1678,38 @@ public class GemFireCacheImpl implements InternalCache, 
ClientCache, HasCachePer
   return;
 }
 
-synchronized(GemFireCacheImpl.class) {
-  synchronized(this) {
-// bug 44031 requires multithread shutdownall should be grouped
-// by root region. However, shutDownAllDuringRecovery.conf test revealed 
that
-// we have to close colocated child regions first.
-// Now check all the PR, if anyone has colocate-with attribute, sort all 
the
-// PRs by colocation relationship and close them sequentially, otherwise 
still
-// group them by root region.
-TreeMap> prTrees = getPRTrees();
-if (prTrees.size() > 1 && shutdownAllPoolSize != 1) {
-  ExecutorService es = getShutdownAllExecutorService(prTrees.size());
-  for (final Map prSubMap : prTrees.values()) {
-es.execute(new Runnable() {
-  public void run() {
-ConnectionTable.threadWantsSharedResources();
-shutdownSubTreeGracefully(prSubMap);
-  }
-});
-  } // for each root
-  es.shutdown();
-  try {
-es.awaitTermination(Integer.MAX_VALUE, TimeUnit.SECONDS);
-  } catch (InterruptedException e) {
-logger.debug("Shutdown all interrupted while waiting for PRs to be 
shutdown gracefully.");
-  }
+synchronized (GemFireCacheImpl.class) {
+  // bug 44031 requires multithread shutdownall should be grouped
+  // by root region. However, shutDownAllDuringRecovery.conf test revealed 
that
+  // we have to close colocated child regions first.
+  // Now check all the PR, if anyone has colocate-with attribute, sort all 
the
+  // PRs by colocation relationship and close them sequentially, otherwise 
still
+  // group them by root region.
+  TreeMap> prTrees = getPRTrees();
+  if (prTrees.size() > 1 && shutdownAllPoolSize != 1) {
+ExecutorService es = getShutdownAllExecutorService(prTrees.size());
+for (final Map prSubMap : prTrees.values()) 
{
+  es.execute(new Runnable() {
+public void run() {
+  ConnectionTable.threadWantsSharedResources();
+  shutdownSubTreeGracefully(prSubMap);
+}
+  });
+} // for each root
+es.shutdown();
+try {
+  es.awaitTermination(Integer.MAX_VALUE, TimeUnit.SECONDS);
+} catch (InterruptedException e) {
+  logger.debug("Shutdown all interrupted while waiting for PRs to be 
shutdown gracefully.");
+}
 
-} else {
-  for (final Map prSubMap : prTrees.values()) {
-shutdownSubTreeGracefully(prSubMap);
+  } else {
+for (final Map prSubMap : prTrees.values()) 
{
+  shutdownSubTreeGracefully(prSubMap);
+}
   }
-}
 
-close("Shut down all members", null, false, true);
-  }
+  close("Shut down all members", null, false, true);
 }
   }
 
@@ -4061,17 +4059,17 @@ public class GemFireCacheImpl implements InternalCache, 
ClientCache, HasCachePer
* cache requires, or does

incubator-geode git commit: GEODE-1978: Slowing down the receivers

[nnag]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop a78fa7537 -> 313bbab55


GEODE-1978: Slowing down the receivers

* Slowing down the receivers so that the senders do not complete
* transmission before the regions are destroyed in the receivers.
* Removing the flaky test tag


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/313bbab5
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/313bbab5
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/313bbab5

Branch: refs/heads/develop
Commit: 313bbab5513a9ec01ecf9206955c19d70a8fc26c
Parents: a78fa75
Author: nabarun 
Authored: Wed Oct 12 10:04:32 2016 -0700
Committer: nabarun 
Committed: Wed Oct 12 12:52:13 2016 -0700

--
 .../ConcurrentWANPropagation_1_DUnitTest.java   | 36 +++-
 1 file changed, 19 insertions(+), 17 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/313bbab5/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/concurrent/ConcurrentWANPropagation_1_DUnitTest.java
--
diff --git 
a/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/concurrent/ConcurrentWANPropagation_1_DUnitTest.java
 
b/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/concurrent/ConcurrentWANPropagation_1_DUnitTest.java
index 8bfd8e7..041e3ca 100644
--- 
a/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/concurrent/ConcurrentWANPropagation_1_DUnitTest.java
+++ 
b/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/concurrent/ConcurrentWANPropagation_1_DUnitTest.java
@@ -319,7 +319,6 @@ public class ConcurrentWANPropagation_1_DUnitTest extends 
WANTestBase {
* 
* @throws Exception
*/
-  @Category(FlakyTest.class) // GEODE-1978
   @Test
   public void testReplicatedSerialPropagationWithRemoteRegionDestroy() throws 
Exception {
 Integer lnPort = (Integer)vm0.invoke(() -> 
WANTestBase.createFirstLocatorWithDSId( 1 ));
@@ -327,37 +326,40 @@ public class ConcurrentWANPropagation_1_DUnitTest extends 
WANTestBase {
 
 //these are part of remote site
 createCacheInVMs(nyPort, vm2, vm3);
+
+//create one RR (RR_1) on remote site
+vm2.invoke(() -> WANTestBase.createReplicatedRegion(
+  getTestMethodName() + "_RR_1", null, isOffHeap() ));
+vm3.invoke(() -> WANTestBase.createReplicatedRegion(
+  getTestMethodName() + "_RR_1", null, isOffHeap() ));
+
 createReceiverInVMs(vm2, vm3);
 
+vm2.invoke(() -> 
addListenerToSleepAfterCreateEvent(1000,getTestMethodName() + "_RR_1"));
+vm3.invoke(() -> 
addListenerToSleepAfterCreateEvent(1000,getTestMethodName() + "_RR_1"));
 
 //these are part of local site
 createCacheInVMs(lnPort, vm4, vm5, vm6, vm7);
 
+//create one RR (RR_1) on local site
+vm4.invoke(() -> WANTestBase.createReplicatedRegion(
+  getTestMethodName() + "_RR_1", "ln", isOffHeap() ));
+vm5.invoke(() -> WANTestBase.createReplicatedRegion(
+  getTestMethodName() + "_RR_1", "ln", isOffHeap() ));
+vm6.invoke(() -> WANTestBase.createReplicatedRegion(
+  getTestMethodName() + "_RR_1", "ln", isOffHeap() ));
+vm7.invoke(() -> WANTestBase.createReplicatedRegion(
+  getTestMethodName() + "_RR_1", "ln", isOffHeap() ));
+
 //senders are created on local site
 vm4.invoke(() -> WANTestBase.createConcurrentSender( "ln", 2,
 false, 100, 500, false, false, null, true, 5, OrderPolicy.KEY ));
 vm5.invoke(() -> WANTestBase.createConcurrentSender( "ln", 2,
 false, 100, 500, false, false, null, true, 5, OrderPolicy.KEY ));
 
-//create one RR (RR_1) on remote site
-vm2.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", null, isOffHeap() ));
-vm3.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", null, isOffHeap() ));
-
 //start the senders on local site
 startSenderInVMs("ln", vm4, vm5);
 
-//create one RR (RR_1) on local site
-vm4.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", "ln", isOffHeap() ));
-vm5.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", "ln", isOffHeap() ));
-vm6.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", "ln", isOffHeap() ));
-vm7.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", "ln", isOffHeap() ));
-
 IgnoredException.addIgnoredException(BatchException70.class.getName());
 
IgnoredException.addIgnoredException(ServerOperationException.class.getName());
 

incubator-geode git commit: GEODE-1985: Check for index expression reevalaution using a time window

[upthewaterspout]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEODE-1985 [created] 7b9a3832b


GEODE-1985: Check for index expression reevalaution using a time window

Changing the logic for how to we check to see if an entry may have been
concurrently modified while an indexed query is in progress.

The new logic just has a time window, defaulting to 10 minutes. If the
entry was changed less than 10 minutes for the query started, we will
reevaluate the index expression to make sure the entry is still valid.


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/7b9a3832
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/7b9a3832
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/7b9a3832

Branch: refs/heads/feature/GEODE-1985
Commit: 7b9a3832b7e0e28c85f7157f98cf7b90085fe843
Parents: 280d2d8
Author: Dan Smith 
Authored: Mon Oct 10 17:41:07 2016 -0700
Committer: Dan Smith 
Committed: Tue Oct 11 13:21:09 2016 -0700

--
 .../query/internal/index/IndexManager.java  | 60 ++---
 .../geode/internal/cache/GemFireCacheImpl.java  |  2 +-
 .../geode/internal/cache/LocalRegion.java   |  1 -
 .../query/internal/IndexManagerJUnitTest.java   | 57 ++---
 ...AbstractIndexMaintenanceIntegrationTest.java | 88 +++-
 ...aintenanceNoReevaluationIntegrationTest.java | 43 ++
 .../internal/index/RangeIndexAPIJUnitTest.java  |  6 +-
 .../cache/PartitionedRegionQueryDUnitTest.java  | 41 ++---
 8 files changed, 150 insertions(+), 148 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/7b9a3832/geode-core/src/main/java/org/apache/geode/cache/query/internal/index/IndexManager.java
--
diff --git 
a/geode-core/src/main/java/org/apache/geode/cache/query/internal/index/IndexManager.java
 
b/geode-core/src/main/java/org/apache/geode/cache/query/internal/index/IndexManager.java
index d12cec4..547ae46 100644
--- 
a/geode-core/src/main/java/org/apache/geode/cache/query/internal/index/IndexManager.java
+++ 
b/geode-core/src/main/java/org/apache/geode/cache/query/internal/index/IndexManager.java
@@ -103,10 +103,11 @@ public class IndexManager  {
   public static boolean TEST_RANGEINDEX_ONLY = false;
   public static final String INDEX_ELEMARRAY_THRESHOLD_PROP = 
"index_elemarray_threshold";
   public static final String INDEX_ELEMARRAY_SIZE_PROP = 
"index_elemarray_size";
+  public static final String IN_PROGRESS_UPDATE_WINDOW_PROP = 
"index.IN_PROGRESS_UPDATE_WINDOW_MS";
   public static final int INDEX_ELEMARRAY_THRESHOLD = 
Integer.parseInt(System.getProperty(INDEX_ELEMARRAY_THRESHOLD_PROP,"100"));
   public static final int INDEX_ELEMARRAY_SIZE = 
Integer.parseInt(System.getProperty(INDEX_ELEMARRAY_SIZE_PROP,"5"));
-  public final static AtomicLong SAFE_QUERY_TIME = new AtomicLong(0);
-  public static boolean ENABLE_UPDATE_IN_PROGRESS_INDEX_CALCULATION = true;
+
+  public static long IN_PROGRESS_UPDATE_WINDOW = 
Long.getLong(IN_PROGRESS_UPDATE_WINDOW_PROP, 10 * 60 * 1000);
   /** The NULL constant */
   public static final Object NULL = new NullToken();
 
@@ -137,37 +138,9 @@ public class IndexManager  {
   }

   /**
-   * Stores the largest combination of current time + delta
-   * If there is a large delta/hiccup in timings, this allows us to calculate 
the 
-   * correct results for a query but, reevaluate more aggressively.
-   * But the large hiccup will eventually be rolled off as time is always 
increasing
-   * This is a fix for #47475
-   * 
-   * @param operationTime the last modified time from version tag
-   * @param currentCacheTime
-   */
-  public static boolean setIndexBufferTime(long operationTime, long 
currentCacheTime) {
-long timeDifference = currentCacheTime - operationTime;
-return setNewLargestValue(SAFE_QUERY_TIME, currentCacheTime + 
timeDifference);
-  }
-  
-  /** only for test purposes 
-   * This should not be called from any product code.  Calls from product code 
will 
-   * possibly cause continous reevaluation (performance issue) OR
-   * incorrect query results (functional issue)
-   **/
-  public static void resetIndexBufferTime() {
-SAFE_QUERY_TIME.set(0);
-  }
-  
-  /**
-   * Calculates whether we need to reevluate the key for the region entry
-   * We added a way to determine whether to reevaluate an entry for query 
execution
-   * The method is to keep track of the delta and current time in a single 
long value
-   * The value is then used by the query to determine if a region entry needs 
to be reevaluated,
-   * based on subtracting the value with the query execution time.  This 
provides a delta + some false positive time (dts)
-   * If the dts + last modified time of the region entry i

incubator-geode git commit: back to volatile boolean so that second SDA will wait for the first

[dschneider]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEM-983 8165e6047 -> 4b80441bc


back to volatile boolean so that second SDA will wait for the first


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/4b80441b
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/4b80441b
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/4b80441b

Branch: refs/heads/feature/GEM-983
Commit: 4b80441bc0c7f69285bbcf47a4314820525a4051
Parents: 8165e60
Author: Darrel Schneider 
Authored: Wed Oct 12 14:50:09 2016 -0700
Committer: Darrel Schneider 
Committed: Wed Oct 12 14:50:09 2016 -0700

--
 .../geode/internal/cache/GemFireCacheImpl.java  | 41 +---
 1 file changed, 19 insertions(+), 22 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/4b80441b/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
--
diff --git 
a/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
 
b/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
index 0e23aaa..20eed44 100755
--- 
a/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
+++ 
b/geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java
@@ -523,7 +523,7 @@ public class GemFireCacheImpl implements InternalCache, 
ClientCache, HasCachePer
 
   private final Object clientMetaDatServiceLock = new Object();
 
-  private final AtomicBoolean isShutDownAll = new AtomicBoolean(false);
+  private volatile boolean isShutDownAll = false;
 
   private final ResourceAdvisor resourceAdvisor;
   private final JmxManagerAdvisor jmxAdvisor;
@@ -1641,7 +1641,7 @@ public class GemFireCacheImpl implements InternalCache, 
ClientCache, HasCachePer
   }
 
   public boolean isCacheAtShutdownAll() {
-return isShutDownAll.get();
+return isShutDownAll;
   }
 
   /**
@@ -1656,29 +1656,26 @@ public class GemFireCacheImpl implements InternalCache, 
ClientCache, HasCachePer
   }
 
   public void shutDownAll() {
-boolean testIGE = Boolean.getBoolean("TestInternalGemFireError");
+synchronized (GemFireCacheImpl.class) {
+  boolean testIGE = Boolean.getBoolean("TestInternalGemFireError");
 
-if (testIGE) {
-  InternalGemFireError assErr = new 
InternalGemFireError(LocalizedStrings.GemFireCache_UNEXPECTED_EXCEPTION.toLocalizedString());
-  throw assErr;
-}
-if (isCacheAtShutdownAll()) {
-  // it's already doing shutdown by another thread
-  return;
-}
-if (LocalRegion.ISSUE_CALLBACKS_TO_CACHE_OBSERVER) {
-  try {
-CacheObserverHolder.getInstance().beforeShutdownAll();
-  } finally {
-LocalRegion.ISSUE_CALLBACKS_TO_CACHE_OBSERVER = false;
+  if (testIGE) {
+InternalGemFireError assErr = new 
InternalGemFireError(LocalizedStrings.GemFireCache_UNEXPECTED_EXCEPTION.toLocalizedString());
+throw assErr;
   }
-}
-if (!this.isShutDownAll.compareAndSet(false, true)) {
-  // it's already doing shutdown by another thread
-  return;
-}
+  if (isCacheAtShutdownAll()) {
+// it's already doing shutdown by another thread
+return;
+  }
+  if (LocalRegion.ISSUE_CALLBACKS_TO_CACHE_OBSERVER) {
+try {
+  CacheObserverHolder.getInstance().beforeShutdownAll();
+} finally {
+  LocalRegion.ISSUE_CALLBACKS_TO_CACHE_OBSERVER = false;
+}
+  }
+  this.isShutDownAll = true;
 
-synchronized (GemFireCacheImpl.class) {
   // bug 44031 requires multithread shutdownall should be grouped
   // by root region. However, shutDownAllDuringRecovery.conf test revealed 
that
   // we have to close colocated child regions first.

incubator-geode git commit: GEODE-1874: Changed setNextNeighbor to not create HashMap for every p2p invocation

[udo]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEODE-1874 edaa462eb -> fb725edbc


GEODE-1874: Changed setNextNeighbor to not create HashMap for every p2p 
invocation


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/fb725edb
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/fb725edb
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/fb725edb

Branch: refs/heads/feature/GEODE-1874
Commit: fb725edbc3dfa4897b7e7916431c7bf5a2456678
Parents: edaa462
Author: Udo Kohlmeyer 
Authored: Thu Oct 13 10:46:44 2016 +1100
Committer: Udo Kohlmeyer 
Committed: Thu Oct 13 10:46:44 2016 +1100

--
 .../internal/membership/gms/fd/GMSHealthMonitor.java | 15 ++-
 1 file changed, 6 insertions(+), 9 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/fb725edb/geode-core/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
--
diff --git 
a/geode-core/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
 
b/geode-core/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
index 97a413c..b3598cd 100644
--- 
a/geode-core/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
+++ 
b/geode-core/src/main/java/org/apache/geode/distributed/internal/membership/gms/fd/GMSHealthMonitor.java
@@ -374,15 +374,14 @@ public class GMSHealthMonitor implements HealthMonitor, 
MessageHandler {
*/
   private void contactedBy(InternalDistributedMember sender, long timeStamp) {
 TimeStamp cTS = new TimeStamp(timeStamp);
-//TODO Udo: why putIfAbsent. Surely only put is required
 cTS = memberTimeStamps.putIfAbsent(sender, cTS);
 if (cTS != null && cTS.getTime() < timeStamp) {
   cTS.setTime(timeStamp);
 }
 if (suspectedMemberInView.remove(sender) != null) {
   logger.info("No longer suspecting {}", sender);
+  setNextNeighbor(currentView, null);
 }
-setNextNeighbor(currentView, null);
   }
 
 
@@ -834,7 +833,7 @@ public class GMSHealthMonitor implements HealthMonitor, 
MessageHandler {
 }
 
 List allMembers = newView.getMembers();
-
+//
 //Set checkAllSuspected = new 
HashSet<>(allMembers);
 //checkAllSuspected.removeAll(suspectedMemberInView.keySet());
 //checkAllSuspected.remove(localAddress);
@@ -1066,10 +1065,7 @@ public class GMSHealthMonitor implements HealthMonitor, 
MessageHandler {
 
   private void processHeartbeat(HeartbeatMessage m) {
 this.stats.incHeartbeatsReceived();
-if (m.getRequestId() < 0) {
-  // a periodic heartbeat
-  contactedBy(m.getSender(), System.currentTimeMillis());
-} else {
+if (m.getRequestId() >= 0) {
   Response resp = requestIdVsResponse.get(m.getRequestId());
   logger.trace("Got heartbeat from member {}. {}", m.getSender(), (resp != 
null ? "Check thread still waiting" : "Check thread is not waiting"));
   if (resp != null) {
@@ -1078,9 +1074,10 @@ public class GMSHealthMonitor implements HealthMonitor, 
MessageHandler {
   resp.notify();
 }
   }
-  //we got heartbeat lets update timestamp
-  contactedBy(m.getSender(), System.currentTimeMillis());
+
 }
+//we got heartbeat lets update timestamp
+contactedBy(m.getSender(), System.currentTimeMillis());
   }
 
   /**