If you’re in for the game... Pokémon or Big Data?

[Avinash Dongre]

https://pixelastic.github.io/pokemonorbigdata/


[image: image.png]

How to shutdown cluster in non-interactive mode using gfsh

[Avinash Dongre]

When I try using gfsh I get following

gfsh>shutdown --include-locators=yes --time-out=5
As a lot of data in memory will be lost, including possibly events in
queues, do you really want to shutdown the entire distributed system?
(Y/n): n

And command line version hangs, probably waiting for input

bin/gfsh -e "connect" -e "shutdown --include-locators=yes"

Any clue how I can bypass this

Thanks
Avinash

Re: Intermittent join-response hang

[Avinash Dongre]

May not be related to this, but for me precheckin took ~22 hrs to finish.

Thanks
Avinash


On Fri, Feb 16, 2018 at 3:14 AM, Bruce Schuchardt 
wrote:

> If it happens again send comms a full log and maybe we can diagnose the
> problem.  I haven't had this happen on my mac.
>
>
>
> On 2/15/18 1:35 PM, Kirk Lund wrote:
>
>> I'm intermittently seeing dunit tests hang (actually fails after timing
>> out) at this point in joining a cluster:
>>
>> [locator] [info 2018/02/15 12:56:25.583 PST 
>> tid=71] This member is becoming coordinator
>>
>> [vm0] [info 2018/02/15 12:56:25.584 PST > Connection(1)-10.118.20.39> tid=20] Probable coordinator is still
>> 10.118.33.216(17575:locator):32769 - waiting for a join-response
>>
>> This is when running any dunit test that has a cluster in IntelliJ on my
>> Mac.
>>
>> It's like the code just intermittently gets stuck in the join-response for
>> coordinator.
>>
>> Any ideas if this is specific to Mac or something? I don't see this
>> happing
>> in precheckin on Linux.
>>
>>
>

Geode Client Server JMH Benchmarks

[Avinash Dongre]

Hello Team,

I am trying to write JMH benchmark test for Geode Client Server operations.

Here is the one I wrote based on my understanding

https://github.com/davinash/MyBenchmarks/blob/develop/getPerfGeode/src/main/java/io/davinash/GeodeGetBenchmark.java

Helper script to execute JMH is at

https://github.com/davinash/MyBenchmarks/blob/develop/getPerfGeode/runBenchmark.sh


It will help me if someone review and check if I am in correct direction.

Here are the numbers I am getting with Single Server, Single Client and PR
with Single Bucket.

Following test is executed with Fork value 10 , warmup iteration 10 and
measurement iteration 20 with Single Thread.



Benchmark   (numOfKeys)   Mode  Cnt
  Score  Error  Units
GeodeGetBenchmark.benchmarkClientServerGet1  thrpt  200
53744.248 ± 1933.360  ops/s
GeodeGetBenchmark.benchmarkClientServerGet   10  thrpt  200
53004.883 ± 2027.630  ops/s
GeodeGetBenchmark.benchmarkClientServerGet  100  thrpt  200
50733.528 ± 2206.536  ops/s
GeodeGetBenchmark.benchmarkClientServerGet 1000  thrpt  200
52667.264 ± 2162.186  ops/s
GeodeGetBenchmark.benchmarkClientServerGet1  thrpt  200
54979.023 ± 1800.375  ops/s
GeodeGetBenchmark.benchmarkClientServerGet   10  thrpt  200
50929.571 ± 2205.263  ops/s
GeodeGetBenchmark.benchmarkClientServerGet  100  thrpt  200
49499.981 ± 2179.255  ops/s
GeodeGetBenchmark.benchmarkClientServerGet 1000  thrpt  200
49546.312 ± 1970.804  ops/s


Thanks
Avinash

Re: Need Help on understanding vsd files

[Avinash Dongre]

Hi Barry,
Still cannot see them.

Thanks
Avinash


On Fri, Sep 22, 2017 at 2:18 PM, Barry Oglesby <bogle...@pivotal.io> wrote:

> Interesting. I can see them, but here they are again. I dragged/dropped
> them this time.
>
> [image: Inline image 1][image: Inline image 2][image: Inline image 3][image:
> Inline image 4][image: Inline image 5]
>
> Thanks,
> Barry Oglesby
>
>
> On Thu, Sep 21, 2017 at 10:23 PM, Avinash Dongre <adon...@apache.org>
> wrote:
>
>> Thanks Barry for your help and explanation.
>> Could you please re-attach the charts for the steps. I do not see them in
>> the email.
>>
>> Thanks
>> Avinash
>>
>>
>> On Fri, Sep 22, 2017 at 2:30 AM, Barry Oglesby <bogle...@pivotal.io>
>> wrote:
>>
>> > You probably need more than just the getTime stat to see whats going on
>> > there. That stat is basically telling you how much time per second get
>> > operations are occurring. You probably need to also know how many gets
>> are
>> > occurring.
>> >
>> > What I generally do is:
>> >
>> > - plot time stat (getTime in this case)
>> > - divide time stat by 100 to get milliseconds (top right in vsd)
>> > - plot operation stat (getsCompleted in this case)
>> > - change both to 'No Filter' (top right drop down in vsd). This tells
>> you
>> > total time and number of operations.
>> > - Divide time stat by operations stat to get average time per operation.
>> > You can do this with either vsd or a calculator. I generally use a
>> > calculator and divide the maximum of each stat, but with vsd:
>> >   - select time stat line
>> >   - select 'Line' -> 'Divide Lines' menu option
>> >   - select operation stat line
>> >   - the last sample of the resulting line is the average for the entire
>> run
>> >
>> > I attached charts for each step.
>> >
>> >
>> > Thanks,
>> > Barry Oglesby
>> >
>> >
>> > On Thu, Sep 21, 2017 at 10:29 AM, Anilkumar Gingade <
>> aging...@pivotal.io>
>> > wrote:
>> >
>> >> At a high level, you can find stat descriptions by "selecting a stat"
>> and
>> >> then clicking (in vsd) main->"Show Statistic Info".
>> >>
>> >> -Anil.
>> >>
>> >>
>> >> On Thu, Sep 21, 2017 at 2:24 AM, Avinash Dongre <adon...@apache.org>
>> >> wrote:
>> >>
>> >>> Attaching the graph.
>> >>>
>> >>> On Thu, Sep 21, 2017 at 2:45 PM, Avinash Dongre <adon...@apache.org>
>> >>> wrote:
>> >>>
>> >>>> Hi All,
>> >>>>>
>> >>>>> I am looking at  getTime-PartitionedRegionStats using vsd tools. I
>> >>>>> need some help on how to interpret following graph.
>> >>>>> If there is a document which helps to explain please let me know.
>> >>>>>
>> >>>>>
>> >>>>> [image: Inline image 1]
>> >>>>>
>> >>>>>
>> >>>>> Thanks
>> >>>>> Avinash
>> >>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> >
>>
>
>

Re: Need Help on understanding vsd files

[Avinash Dongre]

Thanks Barry for your help and explanation.
Could you please re-attach the charts for the steps. I do not see them in
the email.

Thanks
Avinash


On Fri, Sep 22, 2017 at 2:30 AM, Barry Oglesby <bogle...@pivotal.io> wrote:

> You probably need more than just the getTime stat to see whats going on
> there. That stat is basically telling you how much time per second get
> operations are occurring. You probably need to also know how many gets are
> occurring.
>
> What I generally do is:
>
> - plot time stat (getTime in this case)
> - divide time stat by 100 to get milliseconds (top right in vsd)
> - plot operation stat (getsCompleted in this case)
> - change both to 'No Filter' (top right drop down in vsd). This tells you
> total time and number of operations.
> - Divide time stat by operations stat to get average time per operation.
> You can do this with either vsd or a calculator. I generally use a
> calculator and divide the maximum of each stat, but with vsd:
>   - select time stat line
>   - select 'Line' -> 'Divide Lines' menu option
>   - select operation stat line
>   - the last sample of the resulting line is the average for the entire run
>
> I attached charts for each step.
>
>
> Thanks,
> Barry Oglesby
>
>
> On Thu, Sep 21, 2017 at 10:29 AM, Anilkumar Gingade <aging...@pivotal.io>
> wrote:
>
>> At a high level, you can find stat descriptions by "selecting a stat" and
>> then clicking (in vsd) main->"Show Statistic Info".
>>
>> -Anil.
>>
>>
>> On Thu, Sep 21, 2017 at 2:24 AM, Avinash Dongre <adon...@apache.org>
>> wrote:
>>
>>> Attaching the graph.
>>>
>>> On Thu, Sep 21, 2017 at 2:45 PM, Avinash Dongre <adon...@apache.org>
>>> wrote:
>>>
>>>> Hi All,
>>>>>
>>>>> I am looking at  getTime-PartitionedRegionStats using vsd tools. I
>>>>> need some help on how to interpret following graph.
>>>>> If there is a document which helps to explain please let me know.
>>>>>
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>>
>>>>> Thanks
>>>>> Avinash
>>>>>
>>>>>
>>>>
>>>
>>
>

Re: Need Help on understanding vsd files

[Avinash Dongre]

Attaching the graph.

On Thu, Sep 21, 2017 at 2:45 PM, Avinash Dongre <adon...@apache.org> wrote:

> Hi All,
>>
>> I am looking at  getTime-PartitionedRegionStats using vsd tools. I need
>> some help on how to interpret following graph.
>> If there is a document which helps to explain please let me know.
>>
>>
>> [image: Inline image 1]
>>
>>
>> Thanks
>> Avinash
>>
>>
>

Re: New Committer: Deepak Dixit

[Avinash Dongre]

Welcome Deepak !

Thanks
Avinash

On Sat, Jul 15, 2017 at 8:08 AM Anthony Baker  wrote:

> Welcome Deepak!
>
> Anthony
>
> Sent from my iPhone
>
> > On Jul 14, 2017, at 4:46 PM, Mark Bretl  wrote:
> >
> > The Apache Geode Project Management Committee has invited Deepak Dixit to
> > be committer on the project. We are pleased to announce he has accepted.
> >
> > Please join me in welcoming Deepak!
> >
> > Thanks,
> >
> > Mark
> > On behalf of the Apache Geode PMC
>

[jira] [Commented] (GEODE-2908) Swagger UI Tags seems broken in Latest

[Avinash Dongre (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023118#comment-16023118
 ] 

Avinash Dongre commented on GEODE-2908:
---

Hi [~amb] This is not merged to developed yet, since the review is still 
pending.

> Swagger UI Tags seems broken in Latest
> --
>
> Key: GEODE-2908
> URL: https://issues.apache.org/jira/browse/GEODE-2908
> Project: Geode
>  Issue Type: Bug
>    Reporter: Avinash Dongre
>Assignee: Prasad Subhash Indulkar
> Fix For: 1.2.0
>
> Attachments: After.png, Before.png
>
>
> Swagger UI Tags seems broken in Latest



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

[jira] [Assigned] (GEODE-2980) Code Cleanup : Remove redundant modifier from the Interface definition

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-2980:
-

Assignee: Avinash Dongre

> Code Cleanup : Remove redundant modifier from the Interface definition
> --
>
> Key: GEODE-2980
> URL: https://issues.apache.org/jira/browse/GEODE-2980
> Project: Geode
>  Issue Type: Task
>    Reporter: Avinash Dongre
>        Assignee: Avinash Dongre
>
> All methods in an interface are implicitly {{public}} and {{abstract}}
> All fields in an interface are implicitly {{public}}, {{static}} and 
> {{final}}.
> We have almost in all the interface public modifier for all the methods in 
> the Interfaces, we should remove the same.



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

[jira] [Created] (GEODE-2980) Code Cleanup : Remove redundant modifier from the Interface definition

[Avinash Dongre (JIRA)]

Avinash Dongre created GEODE-2980:
-

 Summary: Code Cleanup : Remove redundant modifier from the 
Interface definition
 Key: GEODE-2980
 URL: https://issues.apache.org/jira/browse/GEODE-2980
 Project: Geode
  Issue Type: Task
Reporter: Avinash Dongre


All methods in an interface are implicitly {{public}} and {{abstract}}
All fields in an interface are implicitly {{public}}, {{static}} and {{final}}.

We have almost in all the interface public modifier for all the methods in the 
Interfaces, we should remove the same.



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

[jira] [Resolved] (GEODE-237) Remove EntryEvent deprecated methods

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-237.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Remove EntryEvent deprecated methods
> 
>
> Key: GEODE-237
> URL: https://issues.apache.org/jira/browse/GEODE-237
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The following EntryEvent methods need to be removed:
> - isLocalLoad: change to getOperation().isLocalLoad
> - isNetLoad: change to getOperation().isNetLoad
> - isLoad: change to getOperation().isLoad
> - isNetSearch: change to getOperation().isNetSearch
> - isBridgeEvent: change to hasClientOrigin
> these should be pretty easy to change



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

[jira] [Updated] (GEODE-2908) Swagger UI Tags seems broken in Latest

[Avinash Dongre (JIRA)]

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

Avinash Dongre updated GEODE-2908:
--
Attachment: Before.png

> Swagger UI Tags seems broken in Latest
> --
>
> Key: GEODE-2908
> URL: https://issues.apache.org/jira/browse/GEODE-2908
> Project: Geode
>  Issue Type: Bug
>    Reporter: Avinash Dongre
> Attachments: Before.png
>
>
> Swagger UI Tags seems broken in Latest



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

[jira] [Created] (GEODE-2908) Swagger UI Tags seems broken in Latest

[Avinash Dongre (JIRA)]

Avinash Dongre created GEODE-2908:
-

 Summary: Swagger UI Tags seems broken in Latest
 Key: GEODE-2908
 URL: https://issues.apache.org/jira/browse/GEODE-2908
 Project: Geode
  Issue Type: Bug
Reporter: Avinash Dongre


Swagger UI Tags seems broken in Latest



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

[jira] [Commented] (GEODE-234) remove deprecated MirrorType class

[Avinash Dongre (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001238#comment-16001238
 ] 

Avinash Dongre commented on GEODE-234:
--

[~dschneider] 
I found following files have reference of 'mirror-type'

geode-docs/reference/topics/cache_xml.html.md.erb
geode-docs/reference/topics/client-cache.html.md.erb
geode-docs/reference/topics/gfe_cache_xml.html.md.erb

I am not sure how docs are generated, this may be safe to ignore.


> remove deprecated MirrorType class
> --
>
> Key: GEODE-234
> URL: https://issues.apache.org/jira/browse/GEODE-234
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>
> All uses of MirrorType should be changed to use DataPolicy.REPLICATE.
> All apis that take it as a parameter or return it need to be deleted.
> The cache-9.0.xsd should also be changed to no longer have the "mirror-type" 
> region-attribute.



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

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

[Avinash Dongre]

It looks like
org.apache.geode.distributed.internal.ConsoleDistributionManagerDUnitTest >
testApplications FAILED
because of my changes in GEODE-254.

Since it is marked as Flaky I just ignore it but after replacing

assertEquals(2, root.keySet().size());

with

assertEquals(2, ((AdminRegion)root).keys().size());

Test is passing again.

I am failing to understand why there is special impl for keys in AdminRegion ?

and If this is correct fix.


Thanks

Avinash



On Mon, May 8, 2017 at 11:26 PM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See 
>
> --
> [...truncated 120.69 KB...]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.CacheClosedException: The cache is closed.
> at org.apache.geode.internal.cache.execute.
> LocalResultCollectorImpl.setException(LocalResultCollectorImpl.java:187)
> at org.apache.geode.internal.cache.execute.
> PartitionedRegionFunctionResultSender.setException(
> PartitionedRegionFunctionResultSender.java:381)
> at org.apache.geode.internal.cache.execute.AbstractExecution.
> handleException(AbstractExecution.java:587)
> at org.apache.geode.internal.cache.execute.AbstractExecution.
> executeFunctionLocally(AbstractExecution.java:358)
> at org.apache.geode.internal.cache.execute.
> AbstractExecution$1.run(AbstractExecution.java:275)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at org.apache.geode.distributed.internal.DistributionManager.
> runUntilShutdown(DistributionManager.java:625)
> at org.apache.geode.distributed.internal.DistributionManager$
> 9$1.run(DistributionManager.java:1071)
> ... 1 more
> Caused by: org.apache.geode.cache.CacheClosedException: The cache is
> closed.
> at org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.
> generateCancelledException(GemFireCacheImpl.java:1519)
> at org.apache.geode.CancelCriterion.checkCancelInProgress(
> CancelCriterion.java:83)
> at org.apache.geode.internal.cache.LocalRegion.
> checkRegionDestroyed(LocalRegion.java:7656)
> at org.apache.geode.internal.cache.LocalRegion.
> checkReadiness(LocalRegion.java:2788)
> at org.apache.geode.internal.cache.BucketRegion.
> checkReadiness(BucketRegion.java:1371)
> at org.apache.geode.internal.cache.LocalRegion.size(
> LocalRegion.java:9140)
> at org.apache.geode.internal.cache.LocalRegion.isEmpty(
> LocalRegion.java:9176)
> at org.apache.geode.internal.cache.BucketRegionQueue.
> waitUntilFlushed(BucketRegionQueue.java:485)
> at org.apache.geode.internal.cache.wan.parallel.
> WaitUntilParallelGatewaySenderFlushedCoordinator$
> WaitUntilBucketRegionQueueFlushedCallable.call(
> WaitUntilParallelGatewaySenderFlushedCoordinator.java:131)
> at org.apache.geode.internal.cache.wan.parallel.
> WaitUntilParallelGatewaySenderFlushedCoordinator$
> WaitUntilBucketRegionQueueFlushedCallable.call(
> WaitUntilParallelGatewaySenderFlushedCoordinator.java:111)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at org.apache.geode.distributed.internal.DistributionManager.
> runUntilShutdown(DistributionManager.java:625)
> at org.apache.geode.distributed.internal.DistributionManager$
> 6$1.run(DistributionManager.java:952)
> ... 1 more
>
> 300 tests completed, 1 failed
> :geode-lucene:distributedTest FAILED
> :geode-lucene:flakyTest
> :geode-lucene:integrationTest
> :geode-old-client-support:assemble
> :geode-old-client-support:compileTestJava
> :geode-old-client-support:processTestResources NO-SOURCE
> :geode-old-client-support:testClasses
> :geode-old-client-support:checkMissedTests
> :geode-old-client-support:spotlessJavaCheck
> :geode-old-client-support:spotlessCheck
> :geode-old-client-support:test
> :geode-old-client-support:check
> :geode-old-client-support:build
> :geode-old-client-support:distributedTest
> :geode-old-client-support:flakyTest
> :geode-old-client-support:integrationTest
> :geode-old-versions:javadoc NO-SOURCE
> :geode-old-versions:javadocJar
> :geode-old-versions:sourcesJar
> :geode-old-versions:signArchives SKIPPED
> :geode-old-versions:assemble
> :geode-old-versions:compileTestJava NO-SOURCE
> :geode-old-versions:processTestResources NO-SOURCE
> 

[jira] [Assigned] (GEODE-276) Remove deprecated RegionFactory constructors

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-276:


Assignee: Avinash Dongre

> Remove deprecated RegionFactory constructors
> 
>
> Key: GEODE-276
> URL: https://issues.apache.org/jira/browse/GEODE-276
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The RegionFactory constructors were deprecated and should be removed. If you 
> want to create a RegionFactory the cache now has factory methods that will 
> create one.
> The old constructors are used in many tests but it should not be too hard to 
> convert them to use the new methods on the cache.



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

[jira] [Resolved] (GEODE-254) Remove deprecated Region.keys and Region.entries

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-254.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Remove deprecated Region.keys and Region.entries
> 
>
> Key: GEODE-254
> URL: https://issues.apache.org/jira/browse/GEODE-254
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Remove the deprecated Region.keys and Region.entries. Any calls can be simply 
> changed to Region.keySet and Region.entrySet so this should be an easy change.
> A large number of tests call the deprecated methods.



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

[jira] [Assigned] (GEODE-240) Remove deprecated methods on TransactionEvent

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-240:


Assignee: Shankar Hundekar

> Remove deprecated methods on TransactionEvent
> -
>
> Key: GEODE-240
> URL: https://issues.apache.org/jira/browse/GEODE-240
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>Assignee: Shankar Hundekar
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The following methods should all be deleted from TransactionEvent and callers 
> should be changed to instead use getEvents. The caller may have to do its own 
> filtering on getEvents to find the event(s) it is interested in.
> - getCreateEvents
> - getDestroyEvents
> - getPutEvents
> - getInvalidateEvents
> Some of the existing unit tests depend on the filtering done by these methods 
> so that filtering will need to move to some test util methods.



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

[jira] [Assigned] (GEODE-231) Remove deprecated AttributesMutator.setCacheListener

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-231:


Assignee: Shankar Hundekar

> Remove deprecated AttributesMutator.setCacheListener
> 
>
> Key: GEODE-231
> URL: https://issues.apache.org/jira/browse/GEODE-231
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>Assignee: Shankar Hundekar
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> It looks like AttributesMutator.setCacheListener is currently only called 
> from test code. All of these calls can be replaced with 
> AttributesMutator.initCacheListeners with an array of one listener.
> It is probably not safe to use AttributesMutator.addCacheListener since it 
> leaves an original listeners in place.
> The method is called in about 25 different tests.



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

[jira] [Assigned] (GEODE-234) remove deprecated MirrorType class

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-234:


Assignee: Avinash Dongre

> remove deprecated MirrorType class
> --
>
> Key: GEODE-234
> URL: https://issues.apache.org/jira/browse/GEODE-234
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>
> All uses of MirrorType should be changed to use DataPolicy.REPLICATE.
> All apis that take it as a parameter or return it need to be deleted.
> The cache-9.0.xsd should also be changed to no longer have the "mirror-type" 
> region-attribute.



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

[jira] [Updated] (GEODE-2866) Bytes.java is not used in product, Only used in BytesJUnitTest, should be removed

[Avinash Dongre (JIRA)]

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

Avinash Dongre updated GEODE-2866:
--
Summary: Bytes.java is not used in product, Only used in BytesJUnitTest, 
should be removed  (was: Bytes.java is not used only used in BytesJUnitTest, 
should be removed)

> Bytes.java is not used in product, Only used in BytesJUnitTest, should be 
> removed
> -
>
> Key: GEODE-2866
> URL: https://issues.apache.org/jira/browse/GEODE-2866
> Project: Geode
>  Issue Type: Sub-task
>        Reporter: Avinash Dongre
>
> Bytes.java is not used only used in BytesJUnitTest, should be removed
> FYI [~bschuchardt]



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

[jira] [Created] (GEODE-2866) Bytes.java is not used only used in BytesJUnitTest, should be removed

[Avinash Dongre (JIRA)]

Avinash Dongre created GEODE-2866:
-

 Summary: Bytes.java is not used only used in BytesJUnitTest, 
should be removed
 Key: GEODE-2866
 URL: https://issues.apache.org/jira/browse/GEODE-2866
 Project: Geode
  Issue Type: Sub-task
Reporter: Avinash Dongre


Bytes.java is not used only used in BytesJUnitTest, should be removed
FYI [~bschuchardt]



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

[jira] [Assigned] (GEODE-254) Remove deprecated Region.keys and Region.entries

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-254:


Assignee: Avinash Dongre

> Remove deprecated Region.keys and Region.entries
> 
>
> Key: GEODE-254
> URL: https://issues.apache.org/jira/browse/GEODE-254
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Remove the deprecated Region.keys and Region.entries. Any calls can be simply 
> changed to Region.keySet and Region.entrySet so this should be an easy change.
> A large number of tests call the deprecated methods.



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

[jira] [Resolved] (GEODE-289) Remove deprecated LicenseException

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-289.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Remove deprecated LicenseException
> --
>
> Key: GEODE-289
> URL: https://issues.apache.org/jira/browse/GEODE-289
> Project: Geode
>  Issue Type: Sub-task
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>    Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>
> com.gemstone.gemfire.LicenseException currently exists only for backwards 
> compatibility of user code. It should be removed from Geode.
> If GemFire requires it for backwards compatibility then it will be moved to 
> GemFire.



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

[jira] [Resolved] (GEODE-267) Remove deprecated ThreadInterruptedException

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-267.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Remove deprecated ThreadInterruptedException
> 
>
> Key: GEODE-267
> URL: https://issues.apache.org/jira/browse/GEODE-267
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The ThreadInterruptedException is deprecated and should be removed. None of 
> our product code nor our test code uses it so it should be easy to remove.



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

[jira] [Resolved] (GEODE-260) Remove deprecated RemoteTransactionException

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-260.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Remove deprecated RemoteTransactionException
> 
>
> Key: GEODE-260
> URL: https://issues.apache.org/jira/browse/GEODE-260
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> RemoteTransactionException is not used by any code so should be very easy to 
> remove.



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

[jira] [Resolved] (GEODE-255) Remove deprecated DataSerializer.register(Class,byte)

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-255.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Remove deprecated DataSerializer.register(Class,byte)
> -
>
> Key: GEODE-255
> URL: https://issues.apache.org/jira/browse/GEODE-255
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Remove the deprecated DataSerializer.register(Class,byte) method.
> It should be simple to change all callers to DataSerializer.register(Class) 
> since the current implementation does that.



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

[jira] [Resolved] (GEODE-266) Remove deprecated ObjectSizerImpl

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-266.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Remove deprecated ObjectSizerImpl
> -
>
> Key: GEODE-266
> URL: https://issues.apache.org/jira/browse/GEODE-266
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Remove the deprecated ObjectSizerImpl class. It can simply be replaced with 
> ObjectSizer.DEFAULT. It is used in some tests but should be easy to remove.



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

[jira] [Resolved] (GEODE-253) Remove deprecated EntryNotFoundInRegion

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-253.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Remove deprecated EntryNotFoundInRegion
> ---
>
> Key: GEODE-253
> URL: https://issues.apache.org/jira/browse/GEODE-253
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The EntryNotFoundInRegion is not used at all so should be very easy to remove.



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

[jira] [Resolved] (GEODE-2723) remove "localCacheEnabled" dead code from PartitionedRegion

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-2723.
---
   Resolution: Fixed
Fix Version/s: 1.2.0

> remove "localCacheEnabled" dead code from PartitionedRegion
> ---
>
> Key: GEODE-2723
> URL: https://issues.apache.org/jira/browse/GEODE-2723
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>
> The PartionedRegion class has a final field named "localCacheEnabled". It is 
> always false and never set to true. We have 5 methods that test for it being 
> true and do a bunch of stuff. This dead code should be removed.



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

Code Contribution Steps Errors

[Avinash Dongre]

I am following steps from
https://cwiki.apache.org/confluence/display/GEODE/Code+contributions for
merging my PR to origin/develop.  Previously all the steps used to work,
but now I am getting following error
fatal: Couldn't find remote ref pull/471/head

adongre@hp-pun-02 ~/source/open/t $ git clone
https://git-wip-us.apache.org/repos/asf/geode.git
Cloning into 'geode'...
remote: Counting objects: 140560, done.
remote: Compressing objects: 100% (41754/41754), done.
remote: Total 140560 (delta 89401), reused 135891 (delta 85551)
Receiving objects: 100% (140560/140560), 79.25 MiB | 899.00 KiB/s, done.
Resolving deltas: 100% (89401/89401), done.
Checking connectivity... done.

adongre@hp-pun-02 ~/source/open/t $ cd geode/
adongre@hp-pun-02 ~/source/open/t/geode (master) $ git checkout develop

adongre@hp-pun-02 ~/source/open/t/geode (develop) $ git remote add
aviGitHub https://github.com/davinash/geode

adongre@hp-pun-02 ~/source/open/t/geode (develop) $ git fetch
aviGitHub  pull/471/head:feature/GEODE-289
fatal: Couldn't find remote ref pull/471/head

[jira] [Assigned] (GEODE-236) Remove deprecated CacheEvent methods

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-236:


Assignee: Avinash Dongre

> Remove deprecated CacheEvent methods
> 
>
> Key: GEODE-236
> URL: https://issues.apache.org/jira/browse/GEODE-236
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The following methods need to be removed:
> - CacheEvent.isExpiration: change to CacheEvent.getOperation().isExpiration
> - CacheEvent.isDistributed: change to CacheEvent.getOperation().isDistributed
> This should be a pretty easy task to complete.



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

[jira] [Assigned] (GEODE-253) Remove deprecated EntryNotFoundInRegion

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-253:


Assignee: Avinash Dongre

> Remove deprecated EntryNotFoundInRegion
> ---
>
> Key: GEODE-253
> URL: https://issues.apache.org/jira/browse/GEODE-253
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The EntryNotFoundInRegion is not used at all so should be very easy to remove.



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

[jira] [Assigned] (GEODE-260) Remove deprecated RemoteTransactionException

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-260:


Assignee: Avinash Dongre

> Remove deprecated RemoteTransactionException
> 
>
> Key: GEODE-260
> URL: https://issues.apache.org/jira/browse/GEODE-260
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> RemoteTransactionException is not used by any code so should be very easy to 
> remove.



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

[jira] [Assigned] (GEODE-267) Remove deprecated ThreadInterruptedException

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-267:


Assignee: Avinash Dongre

> Remove deprecated ThreadInterruptedException
> 
>
> Key: GEODE-267
> URL: https://issues.apache.org/jira/browse/GEODE-267
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The ThreadInterruptedException is deprecated and should be removed. None of 
> our product code nor our test code uses it so it should be easy to remove.



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

[jira] [Assigned] (GEODE-289) Remove deprecated LicenseException

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-289:


Assignee: Avinash Dongre

> Remove deprecated LicenseException
> --
>
> Key: GEODE-289
> URL: https://issues.apache.org/jira/browse/GEODE-289
> Project: Geode
>  Issue Type: Sub-task
>Affects Versions: 1.0.0-incubating
>Reporter: Kirk Lund
>    Assignee: Avinash Dongre
>
> com.gemstone.gemfire.LicenseException currently exists only for backwards 
> compatibility of user code. It should be removed from Geode.
> If GemFire requires it for backwards compatibility then it will be moved to 
> GemFire.



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

[jira] [Assigned] (GEODE-237) Remove EntryEvent deprecated methods

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-237:


Assignee: Avinash Dongre

> Remove EntryEvent deprecated methods
> 
>
> Key: GEODE-237
> URL: https://issues.apache.org/jira/browse/GEODE-237
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The following EntryEvent methods need to be removed:
> - isLocalLoad: change to getOperation().isLocalLoad
> - isNetLoad: change to getOperation().isNetLoad
> - isLoad: change to getOperation().isLoad
> - isNetSearch: change to getOperation().isNetSearch
> - isBridgeEvent: change to hasClientOrigin
> these should be pretty easy to change



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

[jira] [Assigned] (GEODE-258) Remove deprecated Cache.getLoggerI18n and getSecurityLoggerI18n methods

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-258:


Assignee: Avinash Dongre

> Remove deprecated Cache.getLoggerI18n and getSecurityLoggerI18n methods
> ---
>
> Key: GEODE-258
> URL: https://issues.apache.org/jira/browse/GEODE-258
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Remove the deprecated Cache.getLoggerI18n and getSecurityLoggerI18n methods. 
> All calls can be replaced with getLogger().convertToLogWriterI18n() so this 
> should be a quick task.



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

[jira] [Assigned] (GEODE-255) Remove deprecated DataSerializer.register(Class,byte)

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-255:


Assignee: Avinash Dongre

> Remove deprecated DataSerializer.register(Class,byte)
> -
>
> Key: GEODE-255
> URL: https://issues.apache.org/jira/browse/GEODE-255
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Remove the deprecated DataSerializer.register(Class,byte) method.
> It should be simple to change all callers to DataSerializer.register(Class) 
> since the current implementation does that.



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

[jira] [Commented] (GEODE-2746) Investigate and Evaluate Existing RPC frameworks.

[Avinash Dongre (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967922#comment-15967922
 ] 

Avinash Dongre commented on GEODE-2746:
---

When I was trying out gRPC, I also faced the same problem. One need to use 
ServerCallStreamObserver and ServerCallStreamObserver.setOnReadyHandler, when 
you have lot of message in case of stream. ( 
https://github.com/davinash/grpc-bench)

> Investigate and Evaluate Existing RPC frameworks.
> -
>
> Key: GEODE-2746
> URL: https://issues.apache.org/jira/browse/GEODE-2746
> Project: Geode
>  Issue Type: Sub-task
>  Components: messaging
>Reporter: Galen O'Sullivan
>
> There are several existing RPC frameworks for which you can define the 
> structure of your protocol and the tool will generate code for talking over 
> the wire, generally down to serialization of objects.
> If one of those RPC frameworks does not fit all our requirements, we'll 
> design our own binary protocol. This protocol would define both what kind of 
> messages can be sent and how they are encoded on the wire. How we encode the 
> objects that we are sending in requests, however, could still be pluggable.
> A few contenders:
> * [BERT|http://bert-rpc.org]
> * [thrift|https://thrift.apache.org/]
> * [gRPC|http://www.grpc.io/]
> * [Avro|https://avro.apache.org/]
> These are two not-entirely-common features we will need to have:
> * support for SSL/TLS, ability to connect to a server with IP & port.
> * support for push messages from the server without polling (this is needed 
> for CQs).
> This is one half of GEODE-2734.



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

[jira] [Assigned] (GEODE-266) Remove deprecated ObjectSizerImpl

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-266:


Assignee: Avinash Dongre

> Remove deprecated ObjectSizerImpl
> -
>
> Key: GEODE-266
> URL: https://issues.apache.org/jira/browse/GEODE-266
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>        Assignee: Avinash Dongre
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Remove the deprecated ObjectSizerImpl class. It can simply be replaced with 
> ObjectSizer.DEFAULT. It is used in some tests but should be easy to remove.



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

[jira] [Assigned] (GEODE-2723) remove "localCacheEnabled" dead code from PartitionedRegion

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-2723:
-

Assignee: Avinash Dongre

> remove "localCacheEnabled" dead code from PartitionedRegion
> ---
>
> Key: GEODE-2723
> URL: https://issues.apache.org/jira/browse/GEODE-2723
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Avinash Dongre
>
> The PartionedRegion class has a final field named "localCacheEnabled". It is 
> always false and never set to true. We have 5 methods that test for it being 
> true and do a bunch of stuff. This dead code should be removed.



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

Re: Review Request 58158: GEODE-2749: ignore bin/ and out/ which are commonly created by IDEs

[Avinash Dongre]

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


Ship it!




Ship It!

- Avinash Dongre


On April 3, 2017, 7:57 p.m., Kirk Lund wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/58158/
> ---
> 
> (Updated April 3, 2017, 7:57 p.m.)
> 
> 
> Review request for geode, Jinmei Liao, Jared Stewart, Ken Howe, and Patrick 
> Rhomberg.
> 
> 
> Bugs: GEODE-2749
> https://issues.apache.org/jira/browse/GEODE-2749
> 
> 
> Repository: geode
> 
> 
> Description
> ---
> 
> I installed new versions of Eclipse and IntelliJ and created geode projects 
> in both using the defaults for IDE output of compiled classes. They created 
> bin/ and out/ which were then failing rat and also showing up as untracked 
> files by git.
> 
> I added both to .gitignore and the ignore list in gradle/rat.gradle and 
> tested with git status and ./gradlew rat.
> 
> 
> Diffs
> -
> 
>   .gitignore 38c813196f5 
>   gradle/rat.gradle c97a9e9dc78 
> 
> 
> Diff: https://reviews.apache.org/r/58158/diff/1/
> 
> 
> Testing
> ---
> 
> precheckin in progress
> 
> 
> Thanks,
> 
> Kirk Lund
> 
>

[jira] [Commented] (GEODE-2145) A valid query in GFSH appears not to work from Java

[Avinash Dongre (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955527#comment-15955527
 ] 

Avinash Dongre commented on GEODE-2145:
---

I tried to reproduce this issue with following test, But I could not reproduce .

{code}
public class BugGeode2145DUnitTest extends LocatorTestBase {
  public BugGeode2145DUnitTest() {
super();
  }

  @Override
  public final void postSetUp() throws Exception {
disconnectAllFromDS();
  }

  @Override
  protected final void postTearDownLocatorTestBase() throws Exception {
disconnectAllFromDS();
  }

  @Test
  public void testOqlWithEntrySet() {
Host host = Host.getHost(0);
VM locator = host.getVM(0);
VM server1 = host.getVM(1);
VM client = host.getVM(3);

final int locatorPort = 
AvailablePort.getRandomAvailablePort(AvailablePort.SOCKET);
final String locatorHost = NetworkUtils.getServerHostName(host);
locator.invoke("Start Locator", () -> startLocator(locatorHost, 
locatorPort, ""));

String locString = getLocatorString(host, locatorPort);
server1.invoke("Start BridgeServer",
() -> startBridgeServer(locString));

client.invoke("create region and insert, query with entrySet", () -> {
  ClientCacheFactory ccf = new ClientCacheFactory();
  ccf.addPoolLocator(locatorHost, locatorPort);
  ClientCache cache = ccf.create();

  Region region = 
cache.createClientRegionFactory(ClientRegionShortcut.CACHING_PROXY).create(REGION_NAME);

  for (int i = 0; i < 10; i++) {
region.put(i, i * 100);
  }
  SelectResults results = (SelectResults) cache.getQueryService()
  .newQuery("select * from /" + REGION_NAME + ".entrySet").execute();
  assertEquals(10, results.asList().size());

  ClientCacheFactory.getAnyInstance().close();
});
server1.invoke("Stopping BridgeServer", () -> stopBridgeServer());
  }

  private void startBridgeServer(final String locString) throws IOException {
Properties props = new Properties();
props.setProperty(MCAST_PORT, "0");
props.setProperty(LOCATORS, locString);
DistributedSystem ds = getSystem(props);
Cache cache = CacheFactory.create(ds);
CacheServer server = cache.addCacheServer();
server.setPort(0);
server.start();
cache.createRegionFactory(RegionShortcut.PARTITION).create(REGION_NAME);
  }

  private void stopBridgeServer() {
CacheFactory.getAnyInstance().close();
  }
}
{code}



> A valid query in GFSH appears not to work from Java
> ---
>
> Key: GEODE-2145
> URL: https://issues.apache.org/jira/browse/GEODE-2145
> Project: Geode
>  Issue Type: Bug
>Reporter: Jared Stewart
>
> The following query works from gfsh:
> {code}
> gfsh> query --query="select * from /RegionA.entrySet"
> {code}
> but appears not work from a Java client:
> {code}
> Object result = queryService.newQuery("select * from 
> /RegionA.entrySet").execute();
> {code}
> resulting in this error:
> {code}
> Exception in thread "main" 
> org.apache.geode.cache.client.ServerOperationException: remote server on 
> pdx2-office-dhcp4(48651:loner):60244:8a112bad: 
> org.apache.geode.SerializationException: failed serializing object
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:675)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:772)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:603)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:165)
>   at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
>   at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:697)
>   at 
> org.apache.geode.cache.client.internal.QueryOp.execute(QueryOp.java:59)
>   at 
> org.apache.geode.cache.client.internal.ServerProxy.query(ServerProxy.java:65)
>   at 
> org.apache.geode.cache.query.internal.DefaultQuery.executeOnServer(DefaultQuery.java:440)
>   at 
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:316)
>   at 
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:298)
>   at com.jaredjstewart.ReadOnlyClient.main(ReadOnlyClient.java:58)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> su

Re: [VOTE] Apache Geode release - v1.1.1 RC2

[Avinash Dongre]

+1
Built from sources
Sanity check with gfsh

Thanks
Avinash


On Sat, Apr 1, 2017 at 3:28 AM, Bruce Schuchardt 
wrote:

> It seems to work fine once I remove that dependency.  I booted up a server
> and a pub/sub cluster and it all worked fine.
>
>
> Le 3/31/2017 à 1:56 PM, Anthony Baker a écrit :
>
>> On Mar 31, 2017, at 9:58 AM, Bruce Schuchardt 
>>> wrote:
>>>
>>> I don't want to give this a -1 but I'm trying to validate this build on
>>> Microsoft Windows 7 and am running into problems in geode-test.
>>>
>> I agree.  I checked this and found the build error on windows goes back
>> before v1.0.0-incubating.M2.  The develop branch doesn’t seem to exhibit
>> this problem.
>>
>> Anthony
>>
>>
>

[jira] [Commented] (GEODE-2734) Investigate/discuss message encoding

[Avinash Dongre (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949760#comment-15949760
 ] 

Avinash Dongre commented on GEODE-2734:
---

Thoughts/Comments  on http://www.grpc.io/

> Investigate/discuss message encoding
> 
>
> Key: GEODE-2734
> URL: https://issues.apache.org/jira/browse/GEODE-2734
> Project: Geode
>  Issue Type: Sub-task
>  Components: messaging
>Reporter: Brian Baynes
>
> Out of all the great ways to encode messages (Thrift, Protobuf, etc), which 
> should we use here?  Let's discuss and come to consensus.



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

Re: Build failed in Jenkins: Geode-nightly #762 - adongre, please read

[Avinash Dongre]

I am getting following error while running precheckin.

* Where:
Build file 
'/home/ampool/private/geode/java/geode/geode-old-versions/build.gradle'
line: 58

* What went wrong:
Execution failed for task ':geode-old-versions:createGeodeClasspathsFile'.
> Could not resolve all dependencies for configuration ':geode-old-versions:
test110Runtime'.
   > Could not download geode-cq.jar (org.apache.geode:geode-cq:1.1.0)
  > Could not get resource 'https://repo1.maven.org/
maven2/org/apache/geode/geode-cq/1.1.0/geode-cq-1.1.0.jar'.
 > Could not GET 'https://repo1.maven.org/
maven2/org/apache/geode/geode-cq/1.1.0/geode-cq-1.1.0.jar'. Received status
code 503 from server: Connection timed out



On Tue, Feb 28, 2017 at 11:06 PM, Avinash Dongre <adon...@apache.org> wrote:

> It is my mistake.
>
> I will revert back my changes for this Test and raise a PR.
>
> Thanks
> Avinash
>
>
> On Tue, Feb 28, 2017 at 10:26 PM, Bruce Schuchardt <bschucha...@pivotal.io
> > wrote:
>
>> ClientServerMiscBCDUnitTest is failing due to adongre's commit
>> yesterday.  A parameterized test was added to a superclass, causing
>> conflict with the subclass's parameterization of all the superclass's
>> methods
>>
>>
>> java.lang.Exception: Method testProxyRegionClientServerOp should have no
>> parameters
>>
>> at org.junit.runners.model.FrameworkMethod.validatePublicVoidNo
>> Arg(FrameworkMethod.java:76)
>> at org.junit.runners.ParentRunner.validatePublicVoidNoArgMethod
>> s(ParentRunner.java:155)
>> at org.junit.runners.BlockJUnit4ClassRunner.validateTestMethods
>> (BlockJUnit4ClassRunner.java:208)
>> at org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMet
>> hods(BlockJUnit4ClassRunner.java:188)
>> at org.junit.runners.BlockJUnit4ClassRunner.collectInitializati
>> onErrors(BlockJUnit4ClassRunner.java:128)
>> at org.junit.runners.ParentRunner.validate(ParentRunner.java:416)
>> at org.junit.runners.ParentRunner.(ParentRunner.java:84)
>> at org.junit.runners.BlockJUnit4ClassRunner.(BlockJUnit4C
>> lassRunner.java:65)
>> at org.junit.runners.parameterized.BlockJUnit4ClassRunnerWithPa
>> rameters.(BlockJUnit4ClassRunnerWithParameters.java:27)
>> at org.apache.geode.test.junit.runners.CategoryWithParameterize
>> dRunner.(CategoryWithParameterizedRunner.java:29)
>> at org.apache.geode.test.junit.runners.CategoryWithParameterize
>> dRunnerFactory.createRunnerForTestWithParameters(CategoryWit
>> hParameterizedRunnerFactory.java:40)
>> at org.junit.runners.Parameterized.createRunnersForParameters(P
>> arameterized.java:313)
>> at org.junit.runners.Parameterized.(Parameterized.java:248)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Native
>> ConstructorAccessorImpl.java:62)
>> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De
>> legatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(Ann
>> otatedBuilder.java:104)
>> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(
>> AnnotatedBuilder.java:86)
>> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(Run
>> nerBuilder.java:59)
>> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.r
>> unnerForClass(AllDefaultPossibilitiesBuilder.java:26)
>> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(Run
>> nerBuilder.java:59)
>> at org.junit.internal.requests.ClassRequest.getRunner(ClassRequ
>> est.java:33)
>> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs
>> (JUnit4IdeaTestRunner.java:49)
>> at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.star
>> tRunnerWithArgs(IdeaTestRunner.java:51)
>> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsA
>> ndStart(JUnitStarter.java:237)
>> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStart
>> er.java:70)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:62)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at com.intellij.rt.execution.application.AppMain.main(AppMain.j
>> ava:147)
>>
>> here is the commit:
>>
>> commit f2721dc812

Re: Build failed in Jenkins: Geode-nightly #762 - adongre, please read

[Avinash Dongre]

It is my mistake.

I will revert back my changes for this Test and raise a PR.

Thanks
Avinash


On Tue, Feb 28, 2017 at 10:26 PM, Bruce Schuchardt 
wrote:

> ClientServerMiscBCDUnitTest is failing due to adongre's commit yesterday.
> A parameterized test was added to a superclass, causing conflict with the
> subclass's parameterization of all the superclass's methods
>
>
> java.lang.Exception: Method testProxyRegionClientServerOp should have no
> parameters
>
> at org.junit.runners.model.FrameworkMethod.validatePublicVoidNo
> Arg(FrameworkMethod.java:76)
> at org.junit.runners.ParentRunner.validatePublicVoidNoArgMethod
> s(ParentRunner.java:155)
> at org.junit.runners.BlockJUnit4ClassRunner.validateTestMethods
> (BlockJUnit4ClassRunner.java:208)
> at org.junit.runners.BlockJUnit4ClassRunner.validateInstanceMet
> hods(BlockJUnit4ClassRunner.java:188)
> at org.junit.runners.BlockJUnit4ClassRunner.collectInitializati
> onErrors(BlockJUnit4ClassRunner.java:128)
> at org.junit.runners.ParentRunner.validate(ParentRunner.java:416)
> at org.junit.runners.ParentRunner.(ParentRunner.java:84)
> at org.junit.runners.BlockJUnit4ClassRunner.(BlockJUnit4C
> lassRunner.java:65)
> at org.junit.runners.parameterized.BlockJUnit4ClassRunnerWithPa
> rameters.(BlockJUnit4ClassRunnerWithParameters.java:27)
> at org.apache.geode.test.junit.runners.CategoryWithParameterize
> dRunner.(CategoryWithParameterizedRunner.java:29)
> at org.apache.geode.test.junit.runners.CategoryWithParameterize
> dRunnerFactory.createRunnerForTestWithParameters(CategoryWit
> hParameterizedRunnerFactory.java:40)
> at org.junit.runners.Parameterized.createRunnersForParameters(P
> arameterized.java:313)
> at org.junit.runners.Parameterized.(Parameterized.java:248)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Native
> ConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De
> legatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(Ann
> otatedBuilder.java:104)
> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(
> AnnotatedBuilder.java:86)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(Run
> nerBuilder.java:59)
> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.
> runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(Run
> nerBuilder.java:59)
> at org.junit.internal.requests.ClassRequest.getRunner(ClassRequ
> est.java:33)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs
> (JUnit4IdeaTestRunner.java:49)
> at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.star
> tRunnerWithArgs(IdeaTestRunner.java:51)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsA
> ndStart(JUnitStarter.java:237)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStart
> er.java:70)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
> ssorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
> thodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.
> java:147)
>
> here is the commit:
>
> commit f2721dc81256bcec84e855e9dc52d2f234e745da
> Author: adongre  
> Date:   Sat Feb 4 21:34:37 2017 +0530
>
> GEODE-1887: Now Size api goes through ServerProxy when cache is of
> type client and DataPolicy is Empty.
> Added a test for both PR and Replicated regions.
>
> GEODE-1887: Addressing review comments, refactor test based on the
> region type.
>
> GEODE-1887: Spotless fixes.
>
> GEODE-1887: Addressing Review Comments.
>
> GEODE-1887: Spotless
>
>
>
>
> Le 2/28/2017 à 8:35 AM, Apache Jenkins Server a écrit :
>
> See 
> 
>  
> 
>
> Changes:
>
> [adongre] GEODE-2428: Adding support of Serialization/deserialization of
>
> [adongre] GEODE-1887: Now Size api goes through ServerProxy when cache is of 
> type
>
> [ukohlmeyer] GEODE-2142: Removal of offending JSON.ORG code and license 
> information
>
> [ukohlmeyer] GEODE-2142: Removal of offending JSON.ORG code and license 
> information
>
> [ukohlmeyer] GEODE-2142: Adding JSON library from the
>
> [ukohlmeyer] GEODE-2142: Amending JSONObject.java with cyclicalDependency 
> management
>
> [ukohlmeyer] GEODE-2142: Refactoring of tests to work with new JSONObject 
> class.
>
> [ukohlmeyer] 

[jira] [Resolved] (GEODE-1995) remove ReliableMessageQueueFactory, ReliableMessageQueue, and getReliableMessageQueueFactory

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-1995.
---
   Resolution: Fixed
Fix Version/s: 1.2.0

> remove ReliableMessageQueueFactory, ReliableMessageQueue, and 
> getReliableMessageQueueFactory
> 
>
> Key: GEODE-1995
> URL: https://issues.apache.org/jira/browse/GEODE-1995
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Darrel Schneider
>    Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>
> ReliableMessageQueueFactory, ReliableMessageQueue, and 
> GemFireCacheImpl.getReliableMessageQueueFactory should all be removed. They 
> are internal and were never used. No tests exist for them.
> They are part of required Roles which is a deprecated feature.



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

[jira] [Updated] (GEODE-2428) Add support for LinkedHashMap in DataSerializer

[Avinash Dongre (JIRA)]

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

Avinash Dongre updated GEODE-2428:
--
Fix Version/s: 1.2.0

> Add support for LinkedHashMap in DataSerializer
> ---
>
> Key: GEODE-2428
> URL: https://issues.apache.org/jira/browse/GEODE-2428
> Project: Geode
>  Issue Type: Improvement
>    Reporter: Avinash Dongre
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>
> DataSerializer should also support serialization and de-serialization of 
> DataSerializer



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

[jira] [Resolved] (GEODE-2428) Add support for LinkedHashMap in DataSerializer

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-2428.
---
Resolution: Fixed

> Add support for LinkedHashMap in DataSerializer
> ---
>
> Key: GEODE-2428
> URL: https://issues.apache.org/jira/browse/GEODE-2428
> Project: Geode
>  Issue Type: Improvement
>    Reporter: Avinash Dongre
>        Assignee: Avinash Dongre
> Fix For: 1.2.0
>
>
> DataSerializer should also support serialization and de-serialization of 
> DataSerializer



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

Re: Could not create an instance of org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage .

[Avinash Dongre]

Please ignore. This was my merge issue.

Thanks
Avinash


On Thu, Feb 16, 2017 at 7:38 PM, Avinash Dongre <adon...@apache.org> wrote:

> Hi All,
>
> I am getting following exception in my test.
> My Test has 3 VMs + locator and I am doing some puts/gets and restarting.
> I see following exception when 1 node is shutdown and other node receive
> this message and then node which receive this message never shutdown.
>
> Any clue why this is happening ?
>
> I am running with rel/v1.1.0
>
> Thanks
> Avinash
>
>
>
> [severe 2017/02/16 18:56:14.532 IST   192.168.3.76(31930):32772 shared unordered uid=3 port=41938> tid=0x52] 
> Error deserializing message
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage
>  .
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
> at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:1003)
> at 
> org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2718)
> at 
> org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3607)
> at 
> org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1865)
> at org.apache.geode.internal.tcp.Connection.run(Connection.java:1726)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.geode.SerializationException: Could not create an 
> instance of  org.apache.geode.internal.cache.TXId .
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
> at org.apache.geode.internal.cache.TXId.createFromData(TXId.java:109)
> at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:966)
> at 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2836)
> at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2897)
> at 
> org.apache.geode.DataSerializer.readObjectArray(DataSerializer.java:1860)
> at 
> org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage.fromData(DLockRecoverGrantorProcessor.java:355)
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
> ... 6 more
> Caused by: org.apache.geode.SerializationException: Could not create an 
> instance of  
> org.apache.geode.distributed.internal.membership.InternalDistributedMember .
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
> at 
> org.apache.geode.internal.DSFIDFactory.readInternalDistributedMember(DSFIDFactory.java:1036)
> at org.apache.geode.internal.cache.TXId.fromData(TXId.java:104)
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
> ... 13 more
> Caused by: java.io.IOException: While reading an InetAddress
> at 
> org.apache.geode.DataSerializer.readInetAddress(DataSerializer.java:477)
> at 
> org.apache.geode.distributed.internal.membership.InternalDistributedMember.fromDataPre_GFE_9_0_0_0(InternalDistributedMember.java:961)
> at 
> org.apache.geode.distributed.internal.membership.InternalDistributedMember.fromData(InternalDistributedMember.java:948)
> at 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
> ... 16 more
> Caused by: java.net.UnknownHostException: addr is of illegal length
> at java.net.InetAddress.getByAddress(InetAddress.java:1042)
> at java.net.InetAddress.getByAddress(InetAddress.java:1439)
> at 
> org.apache.geode.DataSerializer.readInetAddress(DataSerializer.java:470)
> ... 19 more
>
> [warning 2017/02/16 18:56:29.520 IST   
> tid=0x12] 15 seconds have elapsed while waiting for replies: 
>  [192.168.3.76(31930):32772]> on 192.168.3.76(31924):32771 whose 
> current membership list is: [[192.168.3.76(31930):32772, 
> 192.168.3.76(31859:locator):32769, 192.168.3.76(31924):32771]]
>
> [info 2017/02/16 19:15:45.130 IST   
> tid=0x13] VM is exiting - shutting down distributed system
>
> [info 2017/02/16 19:15:45.198 IST   
> tid=0x3d] received leave request from 
> 192.168.3.76(31859:locator):32769 for 
> 192.168.3.76(31859:locator):32769
>
> [info 2017/02/16 19:15:45.198 IST   
> tid=0x3d] This member is becoming the membership coordinator with address 
> 192.168.3.76(31924):32771
>
> [info 2017/02/16 19:15:45.203 IST   
> tid=0x3d] ViewCreator starting on:192.168.3.76(31924):32771
>
>

Could not create an instance of org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage .

[Avinash Dongre]

Hi All,

I am getting following exception in my test.
My Test has 3 VMs + locator and I am doing some puts/gets and restarting.
I see following exception when 1 node is shutdown and other node receive
this message and then node which receive this message never shutdown.

Any clue why this is happening ?

I am running with rel/v1.1.0

Thanks
Avinash



[severe 2017/02/16 18:56:14.532 IST  :32772 shared unordered uid=3 port=41938>
tid=0x52] Error deserializing message
org.apache.geode.SerializationException: Could not create an instance
of  
org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage
.
at 
org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:1003)
at 
org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2718)
at 
org.apache.geode.internal.tcp.Connection.processNIOBuffer(Connection.java:3607)
at 
org.apache.geode.internal.tcp.Connection.runNioReader(Connection.java:1865)
at org.apache.geode.internal.tcp.Connection.run(Connection.java:1726)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.geode.SerializationException: Could not create
an instance of  org.apache.geode.internal.cache.TXId .
at 
org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
at org.apache.geode.internal.cache.TXId.createFromData(TXId.java:109)
at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:966)
at 
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2836)
at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2897)
at org.apache.geode.DataSerializer.readObjectArray(DataSerializer.java:1860)
at 
org.apache.geode.distributed.internal.locks.DLockRecoverGrantorProcessor$DLockRecoverGrantorReplyMessage.fromData(DLockRecoverGrantorProcessor.java:355)
at 
org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
... 6 more
Caused by: org.apache.geode.SerializationException: Could not create
an instance of
org.apache.geode.distributed.internal.membership.InternalDistributedMember
.
at 
org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2492)
at 
org.apache.geode.internal.DSFIDFactory.readInternalDistributedMember(DSFIDFactory.java:1036)
at org.apache.geode.internal.cache.TXId.fromData(TXId.java:104)
at 
org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
... 13 more
Caused by: java.io.IOException: While reading an InetAddress
at org.apache.geode.DataSerializer.readInetAddress(DataSerializer.java:477)
at 
org.apache.geode.distributed.internal.membership.InternalDistributedMember.fromDataPre_GFE_9_0_0_0(InternalDistributedMember.java:961)
at 
org.apache.geode.distributed.internal.membership.InternalDistributedMember.fromData(InternalDistributedMember.java:948)
at 
org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2477)
... 16 more
Caused by: java.net.UnknownHostException: addr is of illegal length
at java.net.InetAddress.getByAddress(InetAddress.java:1042)
at java.net.InetAddress.getByAddress(InetAddress.java:1439)
at org.apache.geode.DataSerializer.readInetAddress(DataSerializer.java:470)
... 19 more

[warning 2017/02/16 18:56:29.520 IST   tid=0x12] 15 seconds have elapsed while
waiting for replies: :32772]> on
192.168.3.76(31924):32771 whose current membership list is:
[[192.168.3.76(31930):32772,
192.168.3.76(31859:locator):32769,
192.168.3.76(31924):32771]]

[info 2017/02/16 19:15:45.130 IST  
tid=0x13] VM is exiting - shutting down distributed system

[info 2017/02/16 19:15:45.198 IST   tid=0x3d] received leave request from
192.168.3.76(31859:locator):32769 for
192.168.3.76(31859:locator):32769

[info 2017/02/16 19:15:45.198 IST   tid=0x3d] This member is becoming the membership
coordinator with address 192.168.3.76(31924):32771

[info 2017/02/16 19:15:45.203 IST   tid=0x3d] ViewCreator starting
on:192.168.3.76(31924):32771

[jira] [Commented] (GEODE-2441) Remove PDXAutoSerializer

[Avinash Dongre (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860957#comment-15860957
 ] 

Avinash Dongre commented on GEODE-2441:
---

Just want to understand why we are removing PDXAutoSerializer utility ?

> Remove PDXAutoSerializer 
> -
>
> Key: GEODE-2441
> URL: https://issues.apache.org/jira/browse/GEODE-2441
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ernest Burghardt
>
> Remove PDXAutoSerializer utility that generates PDX serialization C++ source 
> that you can include in your project to (de)serialize your C++ classes.



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

Re: PR Buckets are created during Get call for non-existing key

[Avinash Dongre]

Thanks Dan

Thanks
Avinash

On Mon, Feb 6, 2017 at 10:48 PM Dan Smith <dsm...@pivotal.io> wrote:

> Hi Avinash,
>
> Any time you try to use a bucket it will get created. It doesn't matter if
> you are trying to put or get values.
>
> -Dan
>
> On Sat, Feb 4, 2017 at 9:32 PM, Avinash Dongre <adon...@apache.org> wrote:
>
> > Hi,
> > In the following test, I have one PR, No buckets will be created
> initially.
> > But when I call get on non-existing-key, I see 1 bucket is created.
> >
> > Why bucket is getting created during get call when the Region is empty.
> >
> > @Test
> > public void testBucketCreatedDuringGet() {
> >   Properties props = new Properties();
> >   props.put("mcast-port", "0");
> >   props.put("locators", "");
> >
> >   Cache cache = new CacheFactory(props).create();
> >   PartitionedRegion pr = (PartitionedRegion)
> > cache.createRegionFactory(RegionShortcut.PARTITION).create("PR");
> >
> >   org.junit.Assert.assertEquals(0,
> > pr.getDataStore().getAllLocalBucketIds().size());
> >
> >   Object notExist = pr.get("NonExistingKey");
> >   org.junit.Assert.assertNull(notExist);
> >
> >   org.junit.Assert.assertEquals(0,
> > pr.getDataStore().getAllLocalBucketIds().size());
> >
> >   pr.destroyRegion();
> >   cache.close();
> >
> > }
> >
> > Thanks
> >
> > Avinash
> >
>

PR Buckets are created during Get call for non-existing key

[Avinash Dongre]

Hi,
In the following test, I have one PR, No buckets will be created initially.
But when I call get on non-existing-key, I see 1 bucket is created.

Why bucket is getting created during get call when the Region is empty.

@Test
public void testBucketCreatedDuringGet() {
  Properties props = new Properties();
  props.put("mcast-port", "0");
  props.put("locators", "");

  Cache cache = new CacheFactory(props).create();
  PartitionedRegion pr = (PartitionedRegion)
cache.createRegionFactory(RegionShortcut.PARTITION).create("PR");

  org.junit.Assert.assertEquals(0,
pr.getDataStore().getAllLocalBucketIds().size());

  Object notExist = pr.get("NonExistingKey");
  org.junit.Assert.assertNull(notExist);

  org.junit.Assert.assertEquals(0,
pr.getDataStore().getAllLocalBucketIds().size());

  pr.destroyRegion();
  cache.close();

}

Thanks

Avinash

[jira] [Assigned] (GEODE-2428) Add support for LinkedHashMap in DataSerializer

[Avinash Dongre (JIRA)]

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

Avinash Dongre reassigned GEODE-2428:
-

Assignee: Avinash Dongre

> Add support for LinkedHashMap in DataSerializer
> ---
>
> Key: GEODE-2428
> URL: https://issues.apache.org/jira/browse/GEODE-2428
> Project: Geode
>  Issue Type: Improvement
>    Reporter: Avinash Dongre
>        Assignee: Avinash Dongre
>
> DataSerializer should also support serialization and de-serialization of 
> DataSerializer



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

[jira] [Created] (GEODE-2428) Add support for LinkedHashMap in DataSerializer

[Avinash Dongre (JIRA)]

Avinash Dongre created GEODE-2428:
-

 Summary: Add support for LinkedHashMap in DataSerializer
 Key: GEODE-2428
 URL: https://issues.apache.org/jira/browse/GEODE-2428
 Project: Geode
  Issue Type: Improvement
Reporter: Avinash Dongre


DataSerializer should also support serialization and de-serialization of 
DataSerializer



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

Re: Native client build fails linking shared library?

[Avinash Dongre]

I have fixed and PR is https://github.com/apache/geode/pull/344

Thanks
Avinash


On Wed, Jan 18, 2017 at 10:58 AM, Dan Smith <dsm...@pivotal.io> wrote:

> Update - I found part of the problem - the c++ command that is constructed
> has -lz before /libxml2.a. If I put -lz at the end, it works. From man c++
>
> "Thus, foo.o -lz bar.o searches library z after file foo.o but before
> bar.o.  If bar.o refers to functions in z, those functions may not be
> loaded."
>
> I'm new to cmake so I'm not quite sure how it's constructing this command.
>
> -Dan
>
>
>
> On Tue, Jan 17, 2017 at 7:43 PM, Avinash Dongre <adon...@apache.org>
> wrote:
>
> > I also face the same problem on my Ubuntu box. I have libz installed. But
> > It looks like the way libxml is getting build in external is problem.
> Same
> > work fine on CentOS.
> >
> > When I enabled VERBOSE on for dependencies/libxml2, I do not see
> -lpthread
> > -lz -lm in the CCLD command. [1]
> >
> >
> > Thanks
> > Avinash
> >
> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396416
> >
> >
> > On Wed, Jan 18, 2017 at 9:09 AM, Vishal Rao <vishal...@gmail.com> wrote:
> >
> > > You might need the dev package of libz, something like libz-dev to be
> > > installed.
> > >
> > > On Wed, Jan 18, 2017 at 6:48 AM, Hitesh Khamesra <
> > > hitesh...@yahoo.com.invalid> wrote:
> > >
> > > > see if this link helps "http://stackoverflow.com/
> > > > questions/32036372/ubuntu-14-04-rails-missing-file"
> > > >
> > > >
> > > >   From: Dan Smith <dsm...@pivotal.io>
> > > >  To: dev@geode.apache.org
> > > >  Sent: Tuesday, January 17, 2017 5:04 PM
> > > >  Subject: Re: Native client build fails linking shared library?
> > > >
> > > > Here's the results of the VERBOSE make. I do see a -lz in the linker
> > > line.
> > > >
> > > > [ 28%] Linking CXX executable gfcppcache_unittests
> > > > cd /home/dan/MyStuff/Code/gemfire/native/cppcache/test &&
> > /usr/bin/cmake
> > > > -E cmake_link_script CMakeFiles/gfcppcache_unittests.dir/link.txt
> > > > --verbose=1
> > > > /usr/bin/c++   -g   -m64 CMakeFiles/gfcppcache_unittests.dir/
> > > ByteArrayFixture.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/ExpirationActionTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/PdxLocalReaderTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/DataInputTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/DataOutputTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/ByteArrayTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/NanoTimerTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/AutoDeleteTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/SharedPtrTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/DiskPolicyTypeTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/CacheXmlParserTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/SharedBaseTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/gfcppBannerTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/CacheableKeysTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/TcrMessage_unittest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/InterestResultPolicyTest.cpp.o
> > > > CMakeFiles/gfcppcache_unittests.dir/ByteArray.cpp.o  -o
> > > > gfcppcache_unittests -rdynamic ../src/libgfcppcache-static.a -lz
> > > > ../../dependencies/ACE/ACE-extern-prefix/lib/libACE.a -lpthread -ldl
> > > -lrt
> > > > ../../dependencies/libxml2/libxml2-extern-prefix/lib/libxml2.a
> > > > ../../dependencies/gtest/gtest-extern-prefix/src/gtest-
> > > extern-build//libgtest.a
> > > > ../../dependencies/gtest/gtest-extern-prefix/src/gtest-
> > > > extern-build//libgtest_main.a
> > > > ../../dependencies/libxml2/libxml2-extern-prefix/lib/
> > libxml2.a(xmlIO.o):
> > > > In function `xmlGzfileOpen_real':
> > > > xmlIO.c:(.text+0xf9d): undefined reference to `gzdopen'
> > > >
> > > > -Dan
> > > >
> > > > On Tue, Jan 17, 2017 at 4:43 PM, Jacob Barrett <jbarr...@pivotal.io>
> > > > wrote:
> > > >
> > > > Dan,
> > > >
> > > > Add VERBOSE=1 to your make command.
> > > >
> > > > make -j8 VERBOSE=1
> > >

Re: Native Namespace

[Avinash Dongre]

+1 for Apache.Geode.Client ( .net ) and apache::geode::client( C++ )

Thanks
Avinash


On Wed, Jan 18, 2017 at 3:17 AM, Jacob Barrett  wrote:

> Anthony,
>
> You make a good argument. Have fun converting all those namespaces for us
> in your free time. :)
>
> Apache.Geode.Client and apache::geode::client it is then...
>
> Anyone else want to chime in before we execute on this?
>
> -Jake
>
>
>
> On Tue, Jan 17, 2017 at 7:39 AM Anthony Baker  wrote:
>
> > Based on [1] [2] [3] it seems like the .NET convention would be:
> >
> > Apache.Geode.Client
> >
> > For cpp the conventions seem a lot more muddled [4] [5].  Even for Apache
> > projects [6] [7] [8] [9] there’s lots of variation.  This variant looks
> > good to me:
> >
> > apache::geode::client
> >
> > but I could be convinced otherwise.
> >
> > Anthony
> >
> > [1] https://msdn.microsoft.com/en-us/library/ms229026(v=vs.110).aspx
> > [2] https://msdn.microsoft.com/en-us/library/893ke618(v=vs.71).aspx
> > [3] http://stackoverflow.com/questions/918894/namespace-
> naming-conventions
> > [4] https://google.github.io/styleguide/cppguide.html#Namespace_Names
> > [5] https://wiki.openstack.org/wiki/CppCodingStandards#Namespace_Names
> > [6] https://thrift.apache.org/tutorial/cpp
> > [7] http://avro.apache.org/docs/1.6.1/api/cpp/html/namespaces.html
> > [8]
> > http://stackoverflow.com/questions/8765473/compiling-a-
> c-program-using-thrift-and-cassandra
> > [9] https://www.gridgain.com/sdk/1.7.2/cppdoc/namespaces.html
> >
> >
> > > On Jan 16, 2017, at 9:10 PM, Jacob Barrett 
> wrote:
> > >
> > > An upcoming change we need to decide on is the C++ and .NET namespace
> for
> > > the C++ and .NET clients.
> > >
> > > *C++*
> > > Current:
> > > *::gemfire*
> > > Thoughts:
> > > *::apache::geode::client*
> > > *::geode::client*
> > > I shy away from prefixing with *apache* since it requires extra blocks
> in
> > > C++:
> > > (formatted to Google C++ style guide)
> > > namespace apache {
> > > namespace geode {
> > > namespace client {
> > >  class Cache {...};
> > > } // namespace client
> > > } // namespace geode
> > > } // namespace apache
> > > vs.
> > > namespace geode {
> > > namespace client {
> > >  class Cache {...};
> > > } // namespace client
> > > } // namespace geode
> > > vs.
> > > namespace geode {
> > >  class Cache {...};
> > > } // namespace geode
> > >
> > > I shy away form just *geode* because it feels too short but I am not
> that
> > > opposed to it. The question is would we likely have anything else in
> C++
> > > under the *geode* namespace that is not the client?
> > >
> > > *.NET*
> > > Current:
> > > *GemStone.GemFire.Cache.Generic*
> > > Thoughts:
> > > *Apache.Geode.Client*
> > > *Geode.Client*
> > > I am not a fan of *Apache.Geode.Cache.Generic* because *Generic* is
> > legacy
> > > form the replacement of the non-generic versions of the API and *Cache*
> > > feels redundant. Feels odd to be working with
> > *Apache.Geode.Cache*.*Cache*
> > > objects.
> > > The same issues with the C++ namespaces apply here since our .NET
> client
> > is
> > > currently C++/CLI which suffers the same namespace block issues.
> > >
> > > It would feel good to have the namespaces be somewhat consistent
> between
> > > clients but it is not normal for namespaces in C++ or .NET to use the
> > > reverse domain style that Java uses. So *org::apache::geode::client /
> > > Org.Apache.Geode.Client* or some variant is off the table I think.
> > >
> > > Anyone have other thoughts?
> > >
> > > Thanks,
> > > Jake
> >
> >
>

Re: [ANNOUNCE] Donation of improved GemFire native client

[Avinash Dongre]

Thanks Jacob.
Build goes fine with this change.


Thanks
Avinash


On Tue, Jan 17, 2017 at 5:17 AM, Jacob Barrett <jbarr...@pivotal.io> wrote:

> Avinash,
>
> We just added some changes to the Geode dependency. You should be able to
> set cmake -DGEODE_ROOT=/path/to/apache-geode. Without that flag set it
> will
> look for Geode in:
>
>   /geode/bin
>   /apache-geode/bin
>   /usr/geode/bin
>   /usr/apache-geode/bin
>   /usr/local/geode/bin
>   /usr/local/apache-geode/bin
>   /opt/geode/bin
>   /opt/apache-geode/bin
>   /opt/local/geode/bin
>   /opt/local/apache-geode/bin
>
>
> -Jake
>
>
> On Sun, Jan 15, 2017 at 2:24 AM Avinash Dongre <adon...@apache.org> wrote:
>
> > This is great.
> >
> > Need to make following change to PASS the build.
> >
> >
> > diff --git a/src/tests/javaobject/CMakeLists.txt
> > b/src/tests/javaobject/CMakeLists.txt
> > index 4924e5c..7f85878 100644
> > --- a/src/tests/javaobject/CMakeLists.txt
> > +++ b/src/tests/javaobject/CMakeLists.txt
> > @@ -9,8 +9,8 @@ get_filename_component(JAVA_HOME ${JAVA_BIN} DIRECTORY)
> >
> >  # Update the class path.
> >  set(CMAKE_JAVA_INCLUDE_PATH ${JAVA_HOME}/lib/tools.jar)
> > -if (GEMFIRE_HOME)
> > -LIST(APPEND CMAKE_JAVA_INCLUDE_PATH
> > ${GEMFIRE_HOME}/lib/geode-core-9.0.0.jar)
> > +if (DEFINED ENV{GEMFIRE_HOME})
> > +LIST(APPEND CMAKE_JAVA_INCLUDE_PATH
> > $ENV{GEMFIRE_HOME}/lib/geode-core-1.0.0-incubating.jar)
> >  else()
> >  LIST(APPEND CMAKE_JAVA_INCLUDE_PATH
> > "/gemfire/lib/geode-core-9.0.0.jar")
> >  endif()
> >
> >
> > Also need to update the src/BUILDING.md for instruction to download geode
> > build from [1] and set GEMFIRE_HOME ( which I think should be changed to
> > GEODE_HOME )
> >
> >
>

Re: [ANNOUNCE] Donation of improved GemFire native client

[Avinash Dongre]

This is great.

Need to make following change to PASS the build.


diff --git a/src/tests/javaobject/CMakeLists.txt
b/src/tests/javaobject/CMakeLists.txt
index 4924e5c..7f85878 100644
--- a/src/tests/javaobject/CMakeLists.txt
+++ b/src/tests/javaobject/CMakeLists.txt
@@ -9,8 +9,8 @@ get_filename_component(JAVA_HOME ${JAVA_BIN} DIRECTORY)

 # Update the class path.
 set(CMAKE_JAVA_INCLUDE_PATH ${JAVA_HOME}/lib/tools.jar)
-if (GEMFIRE_HOME)
-LIST(APPEND CMAKE_JAVA_INCLUDE_PATH
${GEMFIRE_HOME}/lib/geode-core-9.0.0.jar)
+if (DEFINED ENV{GEMFIRE_HOME})
+LIST(APPEND CMAKE_JAVA_INCLUDE_PATH
$ENV{GEMFIRE_HOME}/lib/geode-core-1.0.0-incubating.jar)
 else()
 LIST(APPEND CMAKE_JAVA_INCLUDE_PATH "/gemfire/lib/geode-core-9.0.0.jar")
 endif()


Also need to update the src/BUILDING.md for instruction to download geode
build from [1] and set GEMFIRE_HOME ( which I think should be changed to
GEODE_HOME )

*OPTION 2*
Add Geode Jars as external dependency  and update CMakeFile accordingly to
download as done for other dependencies


Thanks
Avinash

[1]
http://www-eu.apache.org/dist/geode/1.0.0-incubating/apache-geode-1.0.0-incubating.tar.gz


On Sat, Jan 14, 2017 at 4:30 AM, Anthony Baker  wrote:

> I am pleased to announce the donation of improved GemFire client
> drivers to the Geode community. This source code donation includes a
> C++ client and a .NET client.  This new grant attempts to greatly
> improve the mergability of the code base making it friendlier to the
> community by providing an improved build system, better source code
> organization, and many additional fixes. We hope that it will be much
> more accessible for the project community and will lead to a much
> quicker integration into an overall codebase (unlike its predecessor
> [1]).”
>
> The C++ client allows an application to connect to a cluster using
> intelligent network routing for low latency reads and writes.  The C++
> client can additionally cache data locally and receive update
> notifications or register continuous queries.  The .NET client wraps
> the C++ libraries and enables .NET applications to be written for
> Geode.  Both of these clients are functionally equivalatent to the
> already donated Java client for Geode.
>
> The Software Grant Agreement for this code has been accepted by the
> ASF secretary.
>
> The donated code currently sits in a separate branch in the Geode
> repository named next-gen-native-client-software-grant [2] and is
> awaiting community review.  I encourage everyone in the Geode
> community to review this donation and provide feedback.  In particular
> your input on build improvements would be really helpful.  Once the
> community has reached a consensus we can determine next steps and how
> this code might get merged into the develop branch [3] so that all
> users can access these features.  Your suggestions are most welcome!
>
>
> Thanks,
> Anthony
>
> [1] http://mail-archives.apache.org/mod_mbox/geode-dev/201605.
> mbox/%3cCAEwge-ENhF4s_k5Y=h9-mNFANb777j8bNDe4U9jahPYim61pfg
> @mail.gmail.com%3e
> [2] https://git-wip-us.apache.org/repos/asf?p=geode.git;a=
> shortlog;h=refs/heads/next-gen-native-client-software-grant
> [3] https://issues.apache.org/jira/browse/GEODE-1416
>

[jira] [Commented] (GEODE-1510) Inaccurate size constants in GatewaySenderEventImpl.getSizeInBytes

[Avinash Dongre (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15798102#comment-15798102
 ] 

Avinash Dongre commented on GEODE-1510:
---

May be we can use 
https://github.com/apache/hbase/blob/master/hbase-common/src/main/java/org/apache/hadoop/hbase/util/ClassSize.java

> Inaccurate size constants in GatewaySenderEventImpl.getSizeInBytes
> --
>
> Key: GEODE-1510
> URL: https://issues.apache.org/jira/browse/GEODE-1510
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Dan Smith
>
> This method adds together a lot of magic numbers to produce a size for the 
> entry. The size is important because it is used for LRU eviction 
> calculations; if the size is under reported the queue may end up consuming 
> more memory than expected.
> The magic numbers used in this class do no appear to be correct for 64 bit 
> VMs, based on the comments. 
> This size method should be refactored to return an accurate size, preferably 
> one that is measured rather than relying on these constants. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Travis CI reporting checks failures but no issues on my local machine

[Avinash Dongre]

Hi,

I am getting geode-core:spotlessJavaCheck errors on travis-ci.

But When I ran ./gradlew clean build -Dskip.tests=true on my local machine
everything is fine.

https://travis-ci.org/apache/geode/builds/188749592

What I am missing here ?

Thanks
Avinash

[jira] [Resolved] (GEODE-165) Add build support for generating antlr classes from grammar

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-165.
--
Resolution: Fixed

> Add build support for generating antlr classes from grammar
> ---
>
> Key: GEODE-165
> URL: https://issues.apache.org/jira/browse/GEODE-165
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
>    Assignee: Avinash Dongre
>
> The OQL engine currently uses antlr to generate some parsing classes from 
> gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/oql.g
> These are the generated classes. They are currently checked into the source.
> OQLLexer.java
> OQLLexerTokenTypes.java
> OQLLexerTokenTypes.txt
> OQLParser.java
> They can be generated manually by running antlr.Tool on the provided grammar.
> cd gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/
> java -cp antlr.jar antlr.Tool oql.g
> We should add support to the gradle build to generate these classes.
> In my opinion we should also remove the checked in classes. With gradle we 
> can configure things so that the gradle eclipse target will generate these 
> classes and make them available to the IDE as well. Look at 
> gemfire-core/build.gradle for how we do this with the version properties file:
> sourceSets {
>   main {
> output.dir(generatedResources, builtBy: 'createVersionPropertiesFile')
>   }
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-165) Add build support for generating antlr classes from grammar

[Avinash Dongre (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15754075#comment-15754075
 ] 

Avinash Dongre commented on GEODE-165:
--

I made the changes and branch can be found here 
https://github.com/davinash/geode/tree/feature/GEODE-165

But I am getting spotlessJavaCheck error for the generated files.  ( OQLLexer, 
OQLParser, OQLLexerTokenTypes )

Do you know a ways to ignore these files from generated-src directory for 
spotless in gradle.

CC [~mbretl] [~upthewaterspout] [~amb]

> Add build support for generating antlr classes from grammar
> ---
>
> Key: GEODE-165
> URL: https://issues.apache.org/jira/browse/GEODE-165
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Dan Smith
>Assignee: Mark Bretl
>
> The OQL engine currently uses antlr to generate some parsing classes from 
> gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/oql.g
> These are the generated classes. They are currently checked into the source.
> OQLLexer.java
> OQLLexerTokenTypes.java
> OQLLexerTokenTypes.txt
> OQLParser.java
> They can be generated manually by running antlr.Tool on the provided grammar.
> cd gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/parse/
> java -cp antlr.jar antlr.Tool oql.g
> We should add support to the gradle build to generate these classes.
> In my opinion we should also remove the checked in classes. With gradle we 
> can configure things so that the gradle eclipse target will generate these 
> classes and make them available to the IDE as well. Look at 
> gemfire-core/build.gradle for how we do this with the version properties file:
> sourceSets {
>   main {
> output.dir(generatedResources, builtBy: 'createVersionPropertiesFile')
>   }
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Hidden system functions

[Avinash Dongre]

I think Function  should implement InternalEntity

Thanks
Avinash


On Thu, Dec 15, 2016 at 11:36 PM, Kirk Lund  wrote:

> Does anyone know off the top of their heads how to create an internal Geode
> Function that doesn't show up for the User?
>

[jira] [Resolved] (GEODE-2061) Remove PdxInstanceInputStream

[Avinash Dongre (JIRA)]

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

Avinash Dongre resolved GEODE-2061.
---
Resolution: Fixed

> Remove PdxInstanceInputStream
> -
>
> Key: GEODE-2061
> URL: https://issues.apache.org/jira/browse/GEODE-2061
> Project: Geode
>  Issue Type: Improvement
>  Components: serialization
>Reporter: Bruce Schuchardt
>    Assignee: Avinash Dongre
>
> This class should be removed and its uses replaced with its superclass 
> PdxInputStream.  None of the methods it contains differs from the superclass 
> implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Strange Performance Issue with Large number Region Creation

[Avinash Dongre]

Hi All,

Thanks @Mike. Unfortunately I have situation where-in I need to create
those many number of regions.

I need to understand why in StatisticsMonitor and StatMonitorHandler
List is used to store monitors, listeners and statisticIds  , is there any
particular reason for this.

When I replace the List to com.gemstone.gemfire.internal.concurrent.
ConcurrentHashSet
I see significant improvement in creating large number of region creation.
( from ~7hrs to ~26 minutes)


Thanks
Avinash


On Thu, Nov 17, 2016 at 3:27 AM, Michael Stolz <mst...@pivotal.io> wrote:

> I can't think of any reason why any use case could need 1500 Regions.
>
> Regions are heavyweight constructs more similar in nature to Unix mounts
> than Unix directories.
>
> We usually use simple naming conventions for keys to simulate directory
> structures.
>
> So I would recommend that you create 1 Region, and store 1500 named hash
> maps into it.
>
> Make sense?
>
> --
> Mike Stolz
> Principal Engineer - Gemfire Product Manager
> Mobile: 631-835-4771
> On Nov 16, 2016 11:15 AM, "Avinash Dongre" <adon...@apache.org> wrote:
>
> > Hi,
> >
> > I am seeing strange performance issue when I want to create large number
> of
> > regions.
> > Test I am doing with 1500 Regions.
> >
> > ~ 2 minutes for creating first 1130 regions
> > ~7 minutes for creating remaining 370 regions.
> >
> > Following is example code :
> >
> > Cache geodeCache = this.createCache();
> > final String REGION_NAME = "Region_Name";
> > for ( int i = 0; i < 1500; i++) {
> >   RegionFactory<Object, Object> rf =
> > geodeCache.createRegionFactory(RegionShortcut.PARTITION_
> > PERSISTENT_OVERFLOW);
> >   rf.setDiskSynchronous(true);
> >   rf.setEvictionAttributes(EvictionAttributes.
> createLIFOEntryAttributes(1,
> > EvictionAction.OVERFLOW_TO_DISK));
> >   Region<Object, Object> region = rf.create(REGION_NAME + "_" + i);
> > }
> > geodeCache.close();
> >
> >
> > If I remove following code from createVMRegion ( GemFireCacheImpl.java ),
> > then I could create Regions in 2 minutes.
> >
> > if (!rgn.isInternalRegion()) {
> >   system.handleResourceEvent(ResourceEvent.REGION_CREATE, rgn);
> > }
> >
> > Any help or pointers why this is happening ?
> >
> >
> > Thanks
> >
> > Avinash
> >
>