[jira] [Commented] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

[ https://issues.apache.org/jira/browse/GEODE-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869213#comment-15869213 ] Jacob S. Barrett commented on GEODE-2493: - Replace {{HostAsm::nanoSleep}} and

[jira] [Commented] (GEODE-2486) SSL ciphers other than NULL not supported

[ https://issues.apache.org/jira/browse/GEODE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869069#comment-15869069 ] ASF subversion and git services commented on GEODE-2486: Commit

[jira] [Commented] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

[ https://issues.apache.org/jira/browse/GEODE-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869186#comment-15869186 ] Jacob S. Barrett commented on GEODE-2493: - Replace {{HostAsm::getCpuCount}} with

[jira] [Created] (GEODE-2494) Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex. You can find several public domain examples of how to implement a spinlock_mutex that can be

Jacob S. Barrett created GEODE-2494: --- Summary: Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex. You can find several public domain examples of how to implement a spinlock_mutex that can be used with std::lock_guard.

[jira] [Commented] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

[ https://issues.apache.org/jira/browse/GEODE-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869180#comment-15869180 ] Jacob S. Barrett commented on GEODE-2493: - Replace {{SpinLock}} class with C++11 style

[jira] [Commented] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

[ https://issues.apache.org/jira/browse/GEODE-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869218#comment-15869218 ] Jacob S. Barrett commented on GEODE-2493: - Replace {{HostAsm::atomicAdd}} and {{AtomicInc}} with

Re: GeodeRedisAdapter improvments/feedback

I think we as a community need to determine what value do we want to add with the Redis adapter. Redis already does a great job storing small data structures in memory and sharding them. We do a great job of making sure that these data structures are horizontally scalable; why would we want to

Re: Requesting more JIRA permission

Great! You should have access now. -Dan On Wed, Feb 15, 2017 at 5:00 PM, Addison Huddy wrote: > ahuddy > > Not planning any major reorganization of tickets. If that is ever needed, I > will make a formal proposal to the community. > > \ah >

[ANNOUNCE] Apache Geode release 1.1.0

The Apache Geode team is proud to announce Apache Geode release version 1.1.0 Apache *Geode* is a data management platform that provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high

Review Request 56738: GEODE-2489: Avoid sending tombstone GC messages to peer nodes if there is no client registration

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56738/ --- Review request for geode, Darrel Schneider and Eric Shu. Repository: geode

[GitHub] geode issue #398: Split the redis adapter into its own package

Github user metatype commented on the issue: https://github.com/apache/geode/pull/398 Also, I believe redis is started by providing an option to `start server`. How do you plan to extract that from `geode-core`? --- If your project is set up for it, you can reply to this email and

[GitHub] geode pull request #398: Split the redis adapter into its own package

Github user galen-pivotal commented on a diff in the pull request: https://github.com/apache/geode/pull/398#discussion_r101374277 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java --- @@ -1330,21 +1360,12 @@ private void

[jira] [Commented] (GEODE-2464) Review Redis tests

[ https://issues.apache.org/jira/browse/GEODE-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868511#comment-15868511 ] Galen O'Sullivan commented on GEODE-2464: - We'll also need some manual tests to make sure that

Re: PROXY and CACHING_PROXY regions on Client

@John The intention behind this proposal is to make Geode client development easy for new users. So, looking at this as a new user, I would say that having to "create" a PROXY region only to find out that it does nothing on the server, is more confusing than an overloaded getRegion(). To

[jira] [Created] (GEODE-2490) Tombstone messages are getting processed inline

Anilkumar Gingade created GEODE-2490: Summary: Tombstone messages are getting processed inline Key: GEODE-2490 URL: https://issues.apache.org/jira/browse/GEODE-2490 Project: Geode Issue

[GitHub] geode pull request #398: Split the redis adapter into its own package

Github user metatype commented on a diff in the pull request: https://github.com/apache/geode/pull/398#discussion_r101375546 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java --- @@ -1330,21 +1360,12 @@ private void startMemcachedServer() {

[jira] [Assigned] (GEODE-2489) Tombstone message with keys are sent to peer partitioned region nodes even though no clinets are registered

[ https://issues.apache.org/jira/browse/GEODE-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade reassigned GEODE-2489: Assignee: Anilkumar Gingade > Tombstone message with keys are sent to peer

Re: GeodeRedisAdapter improvments/feedback

We should be careful here on a decision. If we start replicating fat lists/sets/hash maps synchronously every update, the Geode user will complain how slow the API is compared with Redis. Note: Redis replicates asynchronously. For fat collections we’re better off creating a region and

Re: GeodeRedisAdapter improvments/feedback

>>>The Redis adapter was designed so that we can scale all the Redis data structures horizontally. If you bring the data structures to region entry level, there is no reason for anyone to use our implementation over Redis. hmm, here we need to understand when we need to create partition-region for

[jira] [Created] (GEODE-2491) Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

Jason Huynh created GEODE-2491: -- Summary: Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners Key: GEODE-2491 URL: https://issues.apache.org/jira/browse/GEODE-2491

[jira] [Assigned] (GEODE-2491) Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

[ https://issues.apache.org/jira/browse/GEODE-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh reassigned GEODE-2491: -- Assignee: Jason Huynh > Reduce logging of handled exceptions in LuceneEventListener and >

[jira] [Resolved] (GEODE-2424) afterSecondary call needs to handle specific exception rather than generic exception

[ https://issues.apache.org/jira/browse/GEODE-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-2424. Resolution: Duplicate Assignee: Jason Huynh Going to close this one as it is related to a

Review Request 56719: GEODE-2491: Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56719/ --- Review request for geode, Lynn Hughes-Godfrey, nabarun nag, and Dan Smith.

[jira] [Assigned] (GEODE-2490) Tombstone messages are getting processed inline

[ https://issues.apache.org/jira/browse/GEODE-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade reassigned GEODE-2490: Assignee: Anilkumar Gingade > Tombstone messages are getting processed inline >

Re: PROXY and CACHING_PROXY regions on Client

Re: breaking existing code; we could throw UnsupportedOperationException for these two methods: - invalidateRegion() - destroyRegion() I do not see anyone using/depending on invalidateRegion, since the behavior currently is a no-op. destroyRegion currently only gets rid of the handle to the

Re: Gradle build for idea

I think this sort of error message would indicate that we have something wrong in our gradle files. So, yes we should be concerned and fix it. Unfortunately, I don't know how to fix it... On Tue, Feb 14, 2017 at 1:36 PM, Udo Kohlmeyer wrote: > Ok... just to clarify... I

[GitHub] geode-native pull request #3: Replace ace calls to standard functions

Github user asfgit closed the pull request at: https://github.com/apache/geode-native/pull/3 --- 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

[jira] [Commented] (GEODE-2449) Move redis adapter to extension framework

[ https://issues.apache.org/jira/browse/GEODE-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868353#comment-15868353 ] ASF subversion and git services commented on GEODE-2449: Commit

[jira] [Commented] (GEODE-2449) Move redis adapter to extension framework

[ https://issues.apache.org/jira/browse/GEODE-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868352#comment-15868352 ] ASF subversion and git services commented on GEODE-2449: Commit

[jira] [Updated] (GEODE-2488) Netstat command fails with OutOfMemoryError

[ https://issues.apache.org/jira/browse/GEODE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2488: - Summary: Netstat command fails with OutOfMemoryError (was: NetstatDUnitTest fails with OutOfMemoryError)

[jira] [Assigned] (GEODE-2469) Redis adapter Hash key support

[ https://issues.apache.org/jira/browse/GEODE-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Khamesra reassigned GEODE-2469: -- Assignee: Hitesh Khamesra > Redis adapter Hash key support >

[jira] [Updated] (GEODE-2488) Netstat command fails with OutOfMemoryError

[ https://issues.apache.org/jira/browse/GEODE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2488: - Description: Note: this can occur outside of dunit tests as well. Just using the gfsh netstat command on

Re: Build failed in Jenkins: Geode-nightly #749

Galen - I'm guessing you might be trying to click on the link below? I'm not sure jenkins actually keeps that stuff - I think it's just looking for file:/// urls in the console output and translating them to http:// urls. You should be able to find the test results by going to the test result link

[GitHub] geode issue #398: Split the redis adapter into its own package

Github user bschuchardt commented on the issue: https://github.com/apache/geode/pull/398 @metatype there are no changes in the netty NOTICE.txt between 4.1.7 and 4.1.8 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[jira] [Closed] (GEODE-84) Extract Redis adaptor from core

[ https://issues.apache.org/jira/browse/GEODE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar closed GEODE-84. - > Extract Redis adaptor from core > --- > > Key: GEODE-84 >

[jira] [Resolved] (GEODE-84) Extract Redis adaptor from core

[ https://issues.apache.org/jira/browse/GEODE-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar resolved GEODE-84. --- Resolution: Duplicate > Extract Redis adaptor from core > --- > >

Re: PROXY and CACHING_PROXY regions on Client

I agree with what Mike said. Plus, I don't think this is as simple as it appears. For instance, if I ... Region students = clientCache.getRegion("Students"); What happens when the "Students" Region does not exist server-side? This would require a check to determine whether the Students Region

Re: PROXY and CACHING_PROXY regions on Client

Introducing an API like this gives us the opportunity to split the client/server region API’s. I don’t think we should return Region, but something specific to “server view”. How would those API’s operate on a CACHING_PROXY? Anthony > On Feb 15, 2017, at 6:44 AM, Swapnil Bawaskar

Re: Review Request 56633: GEODE-2474: refactor code to use SystemUtils to read OS system props

On Feb. 14, 2017, 4:33 p.m., Kirk Lund wrote: > > Everything else looks great. It happens from following TDD. I write the test first and then write the code. This is an example where the results of TDD produce a test with questionable value, but if the tests are very fast (and they are) then

Re: Review Request 56637: refactor ServerStarterRule and LocatorStarterRule so that they can be created without a Properties first.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56637/#review165731 --- Ship it! Ship It! - Kevin Duling On Feb. 14, 2017, 11 a.m.,

Re: Review Request 56635: GEODE-2481: extract default properties generation to its own class

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56635/#review165732 --- Ship it! Ship It! - Kevin Duling On Feb. 13, 2017, 6:33

[GitHub] geode pull request #398: Split the redis adapter into its own package

GitHub user galen-pivotal opened a pull request: https://github.com/apache/geode/pull/398 Split the redis adapter into its own package Under this PR, the redis adapter is moved to its own source root, and registered as a service. We're intending to make this a feature

[jira] [Comment Edited] (GEODE-2488) NetstatDUnitTest fails with OutOfMemoryError

[ https://issues.apache.org/jira/browse/GEODE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868317#comment-15868317 ] Kirk Lund edited comment on GEODE-2488 at 2/15/17 6:37 PM: --- NetstatFunction

[jira] [Updated] (GEODE-2421) Create VS2017 AMI

[ https://issues.apache.org/jira/browse/GEODE-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt updated GEODE-2421: Description: VS2017 is due to RTM in early March 2017, it would be nice to have a dev AMI

[jira] [Resolved] (GEODE-2442) Address link breaking

[ https://issues.apache.org/jira/browse/GEODE-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt resolved GEODE-2442. - Resolution: Invalid > Address link breaking > - > >

[jira] [Created] (GEODE-2488) NetstatDUnitTest fails with OutOfMemoryError

Kirk Lund created GEODE-2488: Summary: NetstatDUnitTest fails with OutOfMemoryError Key: GEODE-2488 URL: https://issues.apache.org/jira/browse/GEODE-2488 Project: Geode Issue Type: Bug

Re: Review Request 56682: GEODE-2444: move Redis out of geode-core.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56682/ --- (Updated Feb. 15, 2017, 5:53 p.m.) Review request for geode, Bruce Schuchardt,

[jira] [Updated] (GEODE-2488) NetstatDUnitTest fails with OutOfMemoryError

[ https://issues.apache.org/jira/browse/GEODE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2488: - Labels: MiscellaneousCommands NetstatCommand netstat (was: ) > NetstatDUnitTest fails with

[jira] [Updated] (GEODE-2488) NetstatDUnitTest fails with OutOfMemoryError

[ https://issues.apache.org/jira/browse/GEODE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2488: - Component/s: management > NetstatDUnitTest fails with OutOfMemoryError >

[jira] [Commented] (GEODE-2485) CacheTransactionManager suspend/resume can leak memory for 30 minutes

[ https://issues.apache.org/jira/browse/GEODE-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868312#comment-15868312 ] Eric Shu commented on GEODE-2485: - Suspend and resume could be called from product. For each create on a

[jira] [Commented] (GEODE-2486) SSL ciphers other than NULL not supported

[ https://issues.apache.org/jira/browse/GEODE-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868328#comment-15868328 ] ASF GitHub Bot commented on GEODE-2486: --- Github user asfgit closed the pull request at:

[jira] [Comment Edited] (GEODE-2421) Create VS2017 AMI

[ https://issues.apache.org/jira/browse/GEODE-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868277#comment-15868277 ] Michael Martell edited comment on GEODE-2421 at 2/15/17 6:45 PM: - Suggest

[GitHub] geode-native pull request #11: GEODE-2486: Initialize OpenSSL for DEFAULT ci...

Github user asfgit closed the pull request at: https://github.com/apache/geode-native/pull/11 --- 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

Re: Review Request 56668: GEODE-2474: mark NetstatDUnitTest as flaky

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56668/#review165730 --- Ship it! Ship It! - Kevin Duling On Feb. 14, 2017, 9:01

Re: PROXY and CACHING_PROXY regions on Client

@Eric- Hmm... Well, I'd argue that it is still confusing to "*overload*" the purpose of getRegion("path") to dually "*get*" (the primary function/purpose) and also "*create*" (secondary). I'd also say that the getRegion("path") API call is not exclusive to a *ClientCache*, particularly since

[jira] [Commented] (GEODE-2421) Create VS2015 AMI

[ https://issues.apache.org/jira/browse/GEODE-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868277#comment-15868277 ] Michael Martell commented on GEODE-2421: Since VS 2017 is needed by dodNetty, Ernie and I suggest

[jira] [Commented] (GEODE-2488) NetstatDUnitTest fails with OutOfMemoryError

[ https://issues.apache.org/jira/browse/GEODE-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868317#comment-15868317 ] Kirk Lund commented on GEODE-2488: -- NetstatFunction reads in every line from the netstat output and lsof

Re: PROXY and CACHING_PROXY regions on Client

I have strong fears that if we make these wholesale changes to existing APIs we're going to end up breaking lots of existing code. For instance, if we make destroyRegion propagate when it never did before, we may end up destroying a server side region in production that wasn't expected. I will

Re: [DISCUSS] JIRA guidelines

+1 > On 14 Feb, 2017, at 20:50, William Markito Oliveira > wrote: > > +1 > > Finally!! ;) > > Sent from my iPhone > >> On Feb 14, 2017, at 7:59 PM, Galen M O'Sullivan >> wrote: >> >> +1 to the article and removing the draft label >> >>>

Build failed in Jenkins: Geode-nightly #749

See Changes: [kmiller] GEODE-2479 Remove docs reference to gemstone.com package [jiliao] GEODE-2474: mark NetstatDUnitTest as flaky [jiliao] refactor ServerStarterRule and LocatorStarterRule so that they can be [gzhou] GEODE-2471: fix

Re: PROXY and CACHING_PROXY regions on Client

John, The proposed solution is actually try to solve the situation you mentioned -- create a proxy Region failed silently on a client when region does not reside on the server. Region students = clientCache.getRegion("Students"); The getRegion will check on the server side and it should fail

Re: PROXY and CACHING_PROXY regions on Client

I agree with Mike that whatever changes in behavior are made to the Java client library should also be made in the C++ and C# libraries. Sarge > On 15 Feb, 2017, at 08:02, Michael Stolz wrote: > > I have strong fears that if we make these wholesale changes to existing >

Re: GeodeRedisAdapter improvments/feedback

Thinking about this, I think that the “spill”/ “unspill” option may actually be the best solution. If the criteria waffles back and forth along the threshold, well, that’s the acceptable worst case. How’s this?: 1) Create a separate region for the collection key - for fat collections

Re: GeodeRedisAdapter improvments/feedback

With the suggestion from Wes, the constraint on the names would have to apply for both small and large. We wouldn't want the thing to explode when it gets converted... Is there a way to just make it configurable? If they know they want a "large" set, somehow let them specify it. Otherwise go

Re: GeodeRedisAdapter improvments/feedback

Doing the spill/unspill option could be pretty tricky to implement, so you have to do a lot of fancy logic in the transition period. I think Jason's suggestion of configuring things might make more sense. -Dan On Wed, Feb 15, 2017 at 1:12 PM, Jason Huynh wrote: > With the

Re: Review Request 56719: GEODE-2491: Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

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

Re: Review Request 56719: GEODE-2491: Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

> On Feb. 15, 2017, 9:33 p.m., nabarun nag wrote: > > geode-lucene/src/main/java/org/apache/geode/cache/lucene/internal/LuceneBucketListener.java, > > line 58 > > > > > > Hi Jason, > > > > I am not sure but

Re: Review Request 56719: GEODE-2491: Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56719/#review165766 --- Ship it! Ship It! - nabarun nag On Feb. 15, 2017, 8:54

[GitHub] geode-native pull request #12: GEODE-2309: Remove or ignore apache-rat flagg...

GitHub user dgkimura opened a pull request: https://github.com/apache/geode-native/pull/12 GEODE-2309: Remove or ignore apache-rat flagged files `resolv.config` used to work around Solaris SPARC networking issues on a local OpenStack instance. It should not be needed going

[GitHub] geode pull request #399: Minor non-functional changes in response to PR comm...

GitHub user galen-pivotal opened a pull request: https://github.com/apache/geode/pull/399 Minor non-functional changes in response to PR comments. @bschuchardt You can merge this pull request into a Git repository by running: $ git pull

[GitHub] geode pull request #398: Split the redis adapter into its own package

Github user galen-pivotal commented on a diff in the pull request: https://github.com/apache/geode/pull/398#discussion_r101388974 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java --- @@ -1330,21 +1360,12 @@ private void

[GitHub] geode-native pull request #13: GEODE-2476: Replace gfcpp with geode.

GitHub user PivotalSarge opened a pull request: https://github.com/apache/geode-native/pull/13 GEODE-2476: Replace gfcpp with geode. - Rename directories and files with gfcpp into their name to instead use geode and update all references thereto. - Rename the gfcpp

[GitHub] geode pull request #400: Add geode-redis to assembly.

GitHub user galen-pivotal opened a pull request: https://github.com/apache/geode/pull/400 Add geode-redis to assembly. This makes starting a server with Redis actually work, at least on my machine. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] geode pull request #398: Split the redis adapter into its own package

Github user galen-pivotal commented on a diff in the pull request: https://github.com/apache/geode/pull/398#discussion_r101388584 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java --- @@ -1330,21 +1360,12 @@ private void

[GitHub] geode pull request #399: Minor non-functional changes in response to PR comm...

Github user asfgit closed the pull request at: https://github.com/apache/geode/pull/399 --- 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

[GitHub] geode pull request #398: Split the redis adapter into its own package

Github user metatype commented on a diff in the pull request: https://github.com/apache/geode/pull/398#discussion_r101391406 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java --- @@ -1330,21 +1360,12 @@ private void startMemcachedServer() {

[jira] [Commented] (GEODE-2478) Replace gf with geode

[ https://issues.apache.org/jira/browse/GEODE-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868674#comment-15868674 ] Michael Dodge commented on GEODE-2478: -- clicache/src/gf_defs.hpp clicache/src/gf_includes.hpp

[jira] [Updated] (GEODE-2125) GFSH cannot information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Issue Type: Bug (was: Improvement) > GFSH cannot information about Locators that go into reconnect mode

[jira] [Updated] (GEODE-2125) GFSH cannot information about Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Summary: GFSH cannot information about Locators that go into reconnect mode (was: GFSH should provide

[jira] [Commented] (GEODE-2309) Replace or add ASF copyright statements in source.

[ https://issues.apache.org/jira/browse/GEODE-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868561#comment-15868561 ] ASF GitHub Bot commented on GEODE-2309: --- GitHub user dgkimura opened a pull request:

Re: GeodeRedisAdapter improvments/feedback

Does delta propagation make worrying about frequently updated fat collections moot? On Feb 15, 2017, at 4:29 PM, Dan Smith > wrote: Doing the spill/unspill option could be pretty tricky to implement, so you have to do a lot of fancy logic in the

Re: [DISCUSS] JIRA guidelines

The draft bit has been removed. Thanks to William for writing these in the first place! -Dan On Wed, Feb 15, 2017 at 8:16 AM, Michael William Dodge wrote: > +1 > > > On 14 Feb, 2017, at 20:50, William Markito Oliveira < > william.mark...@gmail.com> wrote: > > > > +1 > > > >

[jira] [Commented] (GEODE-2476) Replace gfcpp with geode

[ https://issues.apache.org/jira/browse/GEODE-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868619#comment-15868619 ] ASF GitHub Bot commented on GEODE-2476: --- GitHub user PivotalSarge opened a pull request:

Re: Review Request 56719: GEODE-2491: Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56719/#review165774 --- Ship it! Ship It! - Dan Smith On Feb. 15, 2017, 8:54 p.m.,

[jira] [Commented] (GEODE-2125) GFSH cannot communicate with Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868703#comment-15868703 ] Kirk Lund commented on GEODE-2125: -- Note: because the stop commands are asynchronously stopping Locator

[jira] [Commented] (GEODE-2449) Move redis adapter to extension framework

[ https://issues.apache.org/jira/browse/GEODE-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868715#comment-15868715 ] Galen O'Sullivan commented on GEODE-2449: - >From @metatype: Good news! There is a way to start

[jira] [Commented] (GEODE-2125) GFSH cannot communicate with Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868740#comment-15868740 ] Swapnil Bawaskar commented on GEODE-2125: - [~bschuchardt] Even though the logs clearly show that

[jira] [Commented] (GEODE-2487) SSL should not require external security library

[ https://issues.apache.org/jira/browse/GEODE-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868698#comment-15868698 ] Addison commented on GEODE-2487: [~jbarrett]Can we rename this story to ".NET developer should not have to

[jira] [Updated] (GEODE-2125) GFSH cannot communicate with Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2125: - Summary: GFSH cannot communicate with Locators that go into reconnect mode (was: GFSH cannot information

Re: GeodeRedisAdapter improvments/feedback

On Wed, Feb 15, 2017 at 1:34 PM, Real Wes wrote: > Does delta propagation make worrying about frequently updated fat collections moot? As long as we don't have collections on the order of the available RAM on a single server (in which case we'd want to distribute it

[jira] [Commented] (GEODE-2125) GFSH cannot communicate with Locators that go into reconnect mode

[ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868769#comment-15868769 ] Bruce Schuchardt commented on GEODE-2125: - [~swapnilb] That's not a bad idea but I think it

Re: Review Request 56719: GEODE-2491: Reduce logging of handled exceptions in LuceneEventListener and LuceneBucketListeners

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56719/#review165772 --- Ship it! Ship It! - xiaojian zhou On Feb. 15, 2017, 8:54

[GitHub] geode pull request #398: Split the redis adapter into its own package

Github user galen-pivotal commented on a diff in the pull request: https://github.com/apache/geode/pull/398#discussion_r101401136 --- Diff: geode-core/src/main/java/org/apache/geode/internal/cache/GemFireCacheImpl.java --- @@ -1330,21 +1360,12 @@ private void

[jira] [Commented] (GEODE-348) MemoryThresholdsOffHeapDUnitTest.testPRClientPutRejection fail intermittently with "Expected to go normal"

[ https://issues.apache.org/jira/browse/GEODE-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868718#comment-15868718 ] ASF GitHub Bot commented on GEODE-348: -- GitHub user echobravopapa opened a pull request:

[GitHub] geode-native pull request #14: GEODE-348: fix cast to be in compliance with ...

GitHub user echobravopapa opened a pull request: https://github.com/apache/geode-native/pull/14 GEODE-348: fix cast to be in compliance with standards. You can merge this pull request into a Git repository by running: $ git pull https://github.com/echobravopapa/geode-native

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

--- Spring Data GemFire > Nightly-ApacheGeode > #473 was successful. --- Scheduled 1681 tests in total. https://build.spring.io/browse/SGF-NAG-473/ -- This

Voting Process

Hi, Now that we are a top-level project, we need to make sure votes are counted correctly, according to the Apache Voting Process [1]. For this past release vote, we only had PMC votes, however, that could change in the future as we would like to encourage community feedback. In the future, i

Re: Voting Process

> On Feb 15, 2017, at 2:40 PM, Mark Bretl wrote: > > Hi, > > Now that we are a top-level project, we need to make sure votes are counted > correctly, according to the Apache Voting Process [1]. For this past > release vote, we only had PMC votes, however, that could change

Re: Voting Process

+0.9 :) > On 15 Feb, 2017, at 14:48, Anthony Baker wrote: > >> >> On Feb 15, 2017, at 2:40 PM, Mark Bretl wrote: >> >> Hi, >> >> Now that we are a top-level project, we need to make sure votes are counted >> correctly, according to the Apache Voting

Re: [jira] [Commented] (GEODE-2125) GFSH cannot communicate with Locators that go into reconnect mode

I agree that is a special case and should be handled specially. I also think that attaching via the administrative endpoints should be allowed even if you are ringfenced so that we can issue a stop or other command to the locator. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile:

  1   2   >