Re: off heap

[Gregory Chase]

Ben,
Such questions are excellent right here on the Dev List.  Other people may
be interested in the answers to your questions.

-Greg

On Mon, May 29, 2017 at 5:58 AM, Dor Ben Dov  wrote:

> Hi,
>
> Did anyone test / used under load or kind of load the off heap new feature?
>
> To whom should I direct questions regard the service, for example how it
> was implemented?
>
> Regards,
> Dor
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>



-- 
Greg Chase

Product team
http://www.pivotal.io/big-data

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

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

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #569 was SUCCESSFUL (with 1848 tests)

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #569 was successful.
---
Scheduled
1850 tests in total.

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





--
This message is automatically generated by Atlassian Bamboo

off heap

[Dor Ben Dov]

Hi,

Did anyone test / used under load or kind of load the off heap new feature?

To whom should I direct questions regard the service, for example how it was 
implemented?

Regards,
Dor
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

[jira] [Updated] (GEODE-3003) Geode doesn't start after cluster restart when using cluster-configuration

[Anton Mironenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Mironenko updated GEODE-3003:
---
Attachment: readme.txt
20170522-geode-vyazma.zip
20170522-geode-klyazma.zip
geode-host2.zip
geode-host1.zip

"geode-host1.zip" and "geode-host2.zip" - bash scripts and Server.xml for 
reproducing the issue
"20170522-geode-klyazma.zip" and "20170522-geode-vyazma.zip" - Geode folder 
content with logs

> Geode doesn't start after cluster restart when using cluster-configuration
> --
>
> Key: GEODE-3003
> URL: https://issues.apache.org/jira/browse/GEODE-3003
> Project: Geode
>  Issue Type: Bug
>  Components: configuration
>Reporter: Anton Mironenko
>Priority: Blocker
> Attachments: 20170522-geode-klyazma.zip, 20170522-geode-vyazma.zip, 
> geode-host1.zip, geode-host2.zip, readme.txt
>
>
> There is a two-host Geode cluster with locator and server on each host.
> First start of all nodes goes well.
> Then all nodes are gracefully stopped (kill [locator-PID] [server-PID]).
> The second start goes wrong: the locator on the first host always doesn't 
> join the rest of the cluster with the error in the locator log:
> "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data."
> And sometimes (once per 5 starts) some server shuts down just after start 
> with the error 
> "org.apache.geode.GemFireConfigException: cluster configuration service not 
> available".
> This bug started appearing only when we moved to Geode 1.1.1. And it totally 
> blocks us.
> On GemFire 8.2.1 there was no such a bug.
> This is very easy to reproduce.
> Test preparation:
> -
> Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
> 1) unzip "geode-host1.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 
> and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) in start-server.sh 
> "locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to 
> the values of your host1 and host2
> 4) do the bullets 1)-4) for host2, the folder where you unzip the file should 
> be the same as on the first host
> Test running:
> ---
> 1) rm -rf {locator0,server1}
> 2) run ./start-locator.sh; ./start-server.sh on both hosts. See that this 
> cluster start is successful.
> 3) kill locator and server processes on both hosts
> kill [locator-PID] [server-PID]
> 4) run ./start-locator.sh; ./start-server.sh on both hosts
> 5) see that actually there are two clusters: "host1-locator" and 
> "host1-server, host2-locator, host2-server" instead of one cluster. And 
> sometimes there is no "host1-server", because it shutdown with error "Region 
> /_ConfigurationRegion has potentially stale data. It is waiting for another 
> member to recover the latest data.".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (GEODE-3003) Geode doesn't start after cluster restart when using cluster-configuration

[Anton Mironenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Mironenko updated GEODE-3003:
---
Priority: Blocker  (was: Major)

> Geode doesn't start after cluster restart when using cluster-configuration
> --
>
> Key: GEODE-3003
> URL: https://issues.apache.org/jira/browse/GEODE-3003
> Project: Geode
>  Issue Type: Bug
>  Components: configuration
>Reporter: Anton Mironenko
>Priority: Blocker
>
> There is a two-host Geode cluster with locator and server on each host.
> First start of all nodes goes well.
> Then all nodes are gracefully stopped (kill [locator-PID] [server-PID]).
> The second start goes wrong: the locator on the first host always doesn't 
> join the rest of the cluster with the error in the locator log:
> "Region /_ConfigurationRegion has potentially stale data. It is waiting for 
> another member to recover the latest data."
> And sometimes (once per 5 starts) some server shuts down just after start 
> with the error 
> "org.apache.geode.GemFireConfigException: cluster configuration service not 
> available".
> This bug started appearing only when we moved to Geode 1.1.1. And it totally 
> blocks us.
> On GemFire 8.2.1 there was no such a bug.
> This is very easy to reproduce.
> Test preparation:
> -
> Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
> 1) unzip "geode-host1.zip" into some folder on your first host
> 2) in start-locator.sh change the IPs of locators to the values of your host1 
> and host2
> "--locators=10.50.3.38[20236],10.50.3.14[20236]"
> 3) in start-server.sh 
> "locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to 
> the values of your host1 and host2
> 4) do the bullets 1)-4) for host2, the folder where you unzip the file should 
> be the same as on the first host
> Test running:
> ---
> 1) rm -rf {locator0,server1}
> 2) run ./start-locator.sh; ./start-server.sh on both hosts. See that this 
> cluster start is successful.
> 3) kill locator and server processes on both hosts
> kill [locator-PID] [server-PID]
> 4) run ./start-locator.sh; ./start-server.sh on both hosts
> 5) see that actually there are two clusters: "host1-locator" and 
> "host1-server, host2-locator, host2-server" instead of one cluster. And 
> sometimes there is no "host1-server", because it shutdown with error "Region 
> /_ConfigurationRegion has potentially stale data. It is waiting for another 
> member to recover the latest data.".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (GEODE-3003) Geode doesn't start after cluster restart when using cluster-configuration

[Anton Mironenko (JIRA)]

Anton Mironenko created GEODE-3003:
--

 Summary: Geode doesn't start after cluster restart when using 
cluster-configuration
 Key: GEODE-3003
 URL: https://issues.apache.org/jira/browse/GEODE-3003
 Project: Geode
  Issue Type: Bug
  Components: configuration
Reporter: Anton Mironenko


There is a two-host Geode cluster with locator and server on each host.
First start of all nodes goes well.
Then all nodes are gracefully stopped (kill [locator-PID] [server-PID]).
The second start goes wrong: the locator on the first host always doesn't join 
the rest of the cluster with the error in the locator log:
"Region /_ConfigurationRegion has potentially stale data. It is waiting for 
another member to recover the latest data."

And sometimes (once per 5 starts) some server shuts down just after start with 
the error 
"org.apache.geode.GemFireConfigException: cluster configuration service not 
available".

This bug started appearing only when we moved to Geode 1.1.1. And it totally 
blocks us.
On GemFire 8.2.1 there was no such a bug.

This is very easy to reproduce.

Test preparation:
-
Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
1) unzip "geode-host1.zip" into some folder on your first host
2) in start-locator.sh change the IPs of locators to the values of your host1 
and host2
"--locators=10.50.3.38[20236],10.50.3.14[20236]"
3) in start-server.sh 
"locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to 
the values of your host1 and host2
4) do the bullets 1)-4) for host2, the folder where you unzip the file should 
be the same as on the first host

Test running:
---
1) rm -rf {locator0,server1}
2) run ./start-locator.sh; ./start-server.sh on both hosts. See that this 
cluster start is successful.
3) kill locator and server processes on both hosts
kill [locator-PID] [server-PID]
4) run ./start-locator.sh; ./start-server.sh on both hosts
5) see that actually there are two clusters: "host1-locator" and "host1-server, 
host2-locator, host2-server" instead of one cluster. And sometimes there is no 
"host1-server", because it shutdown with error "Region /_ConfigurationRegion 
has potentially stale data. It is waiting for another member to recover the 
latest data.".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] geode issue #404: Geode 2469

[yhilem]

Github user yhilem commented on the issue:

https://github.com/apache/geode/pull/404
  
Hi Team,
Would you like to integrate this PR in the next delivery please?
Best regards,
Youcef HILEM


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