Re: The next release (v1.1.0)

[Anthony Baker]

Hi Dor,

I want to stress that the transition was from an Apache Incubator subproject to 
an Apache TLP.  The individual committers and PMC members in the Geode 
community will continue to drive the project forward.

Anthony

> On Nov 23, 2016, at 1:03 AM, Dor Ben Dov  wrote:
> 
> Anthony, 
> 
> Are you (all pivotal developers / architects) who are here in the community 
> will now leave once this being managed by
> Itself or are you continuing to contribute? 
> Regards,
> Dor
> 
> -Original Message-
> From: Anthony Baker [mailto:aba...@pivotal.io] 
> Sent: יום ג 22 נובמבר 2016 16:44
> To: geode 
> Subject: Re: The next release (v1.1.0)
> 
> Transitioning from an incubating project to a top-level project means we keep 
> doing exactly what we’ve been doing—except that now the project is 
> responsible for managing itself.  We will be transitioning a few resources 
> such as mailing lists and git repos to reflect that we are no longer an 
> incubator subproject.
> 
> See http://incubator.apache.org/guides/graduation.html.
> 
> Anthony
> 
>> On Nov 21, 2016, at 11:57 AM, Dor Ben Dov  wrote:
>> 
>> Anthony,
>> 
>> What are the actual implications of this transition to the tlp ? 
>> 
>> Regards,
>> Dor
>> 
>> -Original Message-
>> From: Anthony Baker [mailto:aba...@pivotal.io]
>> Sent: יום ב 21 נובמבר 2016 19:26
>> To: dev@geode.apache.org
>> Subject: The next release (v1.1.0)
>> 
>> Now that graduation is done (!!), we need to organize our next release.  I 
>> propose we focus on completing the transition to TLP and cleaning up 
>> “incubating" references.  The sequence would look something like this:
>> 
>> 1) Transition the git repo, mailing lists, etc.
>> 2) Update incubating references in source, docs, website, wiki, …
>> 3) Do a release.
>> 
>> Thoughts?
>> 
>> We need a release manager.  Any volunteers?
>> 
>> Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0.  
>> Can someone with JIRA karma help?
>> 
>> Anthony
>> 
>> 
>> This message and the information contained herein is proprietary and 
>> confidential and subject to the Amdocs policy statement, you may 
>> review at http://www.amdocs.com/email_disclaimer.asp
> 
> 
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp

Re: JSON License and Apache Projects

[Anthony Baker]

Thanks William!

I filed GEODE-2142 for tracking the legal requirement for remove JSON.

Anthony

> On Nov 24, 2016, at 4:38 PM, William Markito Oliveira 
>  wrote:
> 
> Interesting thread about json parsing libraries and licensing.  
> 
> Sent from my iPhone
> 
> Begin forwarded message:
> 
>> From: Ted Dunning 
>> Date: November 24, 2016 at 2:28:47 PM PST
>> To: "gene...@incubator.apache.org" 
>> Subject: Re: JSON License and Apache Projects
>> Reply-To: gene...@incubator.apache.org
>> 
>> Stephan,
>> 
>> What you suggest should work (if you add another dependency to provide the
>> needed classes).
>> 
>> You have to be careful, however, because your consumers may expect to get
>> the full json.org API.
>> 
>> I would suggest that exclusions like this should only be used while your
>> direct dependency still has the dependency on json.org. When they fix it,
>> you can drop the exclusion and all will be good.
>> 
>> 
>> 
>>> On Thu, Nov 24, 2016 at 2:21 AM, Stephan Ewen  wrote:
>>> 
>>> Just to be on the safe side:
>>> 
>>> If project X depends on another project Y that uses json.org (and thus
>>> project X has json.org as a transitive dependency) is it sufficient to
>>> exclude the transitive json.org dependency in the reference to project Y?
>>> 
>>> Something like that:
>>> 
>>> 
>>> org.apache.hive.hcatalog
>>> hcatalog-core
>>> 0.12.0
>>> 
>>>   
>>> org.json
>>> json
>>>   
>>> 
>>> 
>>> 
>>> Thanks,
>>> Stephan
>>> 
>>> 
>>> On Thu, Nov 24, 2016 at 10:00 AM, Jochen Theodorou 
>>> wrote:
>>> 
 is that library able to deal with the jdk9 module system?
 
 
> On 24.11.2016 02:16, James Bognar wrote:
> 
> Shameless plug for Apache Juneau that has a cleanroom implementation of
>>> a
> JSON serializer and parser in context of a common serialization API that
> includes a variety of serialization languages for POJOs.
> 
> On Wed, Nov 23, 2016 at 8:10 PM Ted Dunning 
> wrote:
> 
> The VP Legal for Apache has determined that the JSON processing library
>> from json.org  is not usable as
>>> a
>> dependency by Apache projects. This is because the license includes a
>> line
>> that places a field of use condition on downstream users in a way that
>>> is
>> not compatible with Apache's license.
>> 
>> This decision is, unfortunately, a change from the previous situation.
>> While the current decision is correct, it would have been nice if we
>>> had
>> had this decision originally.
>> 
>> As such, some existing projects may be impacted because they assumed
>>> that
>> the json.org dependency was OK to use.
>> 
>> Incubator projects that are currently using the json.org library have
>> several courses of action:
>> 
>> 1) just drop it. Some projects like Storm have demos that use twitter4j
>> which incorporates the problematic code. These demos aren't core and
>> could
>> just be dropped for a time.
>> 
>> 2) help dependencies move away from problem code. I have sent a pull
>> request to twitter4 j,
>>> for
>> example, that eliminates the problem. If they accept the pull, then all
>> would be good for the projects that use twitter4j (and thus json.org)
>> 
>> 3) replace the json.org artifact with a compatible one that is open
>> source.
>> I have created and published an artifact based on clean-room Android
>>> code
>>  that replicates the most
>> important
>> parts of the json.org code. This code is compatible, but lacks some
>> coverage. It also could lead to jar hell if used unjudiciously because
>>> it
>> uses the org.json package. Shading and exclusion in a pom might help.
>>> Or
>> not. Go with caution here.
>> 
>> 4) switch to safer alternatives such as Jackson. This requires code
>> changes, but is probably a good thing to do. This option is the one
>>> that
>> is
>> best in the long-term but is also the most expensive.
>> 
>> 
>> -- Forwarded message --
>> From: Jim Jagielski 
>> Date: Wed, Nov 23, 2016 at 6:10 AM
>> Subject: JSON License and Apache Projects
>> To: ASF Board 
>> 
>> 
>> (forwarded from legal-discuss@)
>> 
>> As some of you may know, recently the JSON License has been
>> moved to Category X (https://www.apache.org/legal/resolved#category-x
>>> ).
>> 
>> I understand that this has impacted some projects, especially
>> those in the midst of doing a release. I also understand that
>> up until now, really, there has been no real "outcry" over our
>> usage of it, especially from end-users and other consumers of
>> our projects which use it.
>> 
>> As compelling as that is, the fact is that the JSON license
>> itself is not OSI approved and is therefore no

[GitHub] incubator-geode issue #291: [GEODE-1122] Fixed Dependency on environment var...

[metatype]

Github user metatype commented on the issue:

https://github.com/apache/incubator-geode/pull/291
  
@davinash I think you merged `master` into your feature branch.  I suggest 
closing this PR and starting a new one.


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

[GitHub] incubator-geode issue #295: [GEODE-1984] #comment Fix Issue Make GatewaySend...

[metatype]

Github user metatype commented on the issue:

https://github.com/apache/incubator-geode/pull/295
  
@davinash I think you merged `master` into your feature branch.  I suggest 
closing this PR and starting a new one.


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

[GitHub] incubator-geode pull request #291: [GEODE-1122] Fixed Dependency on environm...

[davinash]

Github user davinash closed the pull request at:

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


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

[GitHub] incubator-geode pull request #295: [GEODE-1984] #comment Fix Issue Make Gate...

[davinash]

Github user davinash closed the pull request at:

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


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

Please update your podling status page

[John D. Ament]

Dear Geode PMC

Congratulations on becoming a top level project.  Please complete your
incubator graduation steps.  They can be found here:
http://incubator.apache.org/guides/graduation.html#unincubate

John

Re: Please update your podling status page

[Mark Bretl]

Hi John,

I am working on editing the documents in SVN, however, it seems I do not
have permission to check in. Would you be able to help me with that or can
you point me in the right direction?

Best Regards,

--Mark

On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
wrote:

> Dear Geode PMC
>
> Congratulations on becoming a top level project.  Please complete your
> incubator graduation steps.  They can be found here:
> http://incubator.apache.org/guides/graduation.html#unincubate
>
> John
>

Re: The next release (v1.1.0)

[Dor Ben Dov]

Hi Anthony

Thanks for the answer.

Dor

 Original Message 

Subject: Re: The next release (v1.1.0)

From: Anthony Baker 

Date: 25 בנוב' 2016, 16:44

To: dev@geode.apache.org

Hi Dor,

I want to stress that the transition was from an Apache Incubator subproject to 
an Apache TLP.  The individual committers and PMC members in the Geode 
community will continue to drive the project forward.

Anthony

> On Nov 23, 2016, at 1:03 AM, Dor Ben Dov  wrote:
>
> Anthony,
>
> Are you (all pivotal developers / architects) who are here in the community 
> will now leave once this being managed by
> Itself or are you continuing to contribute?
> Regards,
> Dor
>
> -Original Message-
> From: Anthony Baker [mailto:aba...@pivotal.io]
> Sent: יום ג 22 נובמבר 2016 16:44
> To: geode 
> Subject: Re: The next release (v1.1.0)
>
> Transitioning from an incubating project to a top-level project means we keep 
> doing exactly what we’ve been doing—except that now the project is 
> responsible for managing itself.  We will be transitioning a few resources 
> such as mailing lists and git repos to reflect that we are no longer an 
> incubator subproject.
>
> See http://incubator.apache.org/guides/graduation.html.
>
> Anthony
>
>> On Nov 21, 2016, at 11:57 AM, Dor Ben Dov  wrote:
>>
>> Anthony,
>>
>> What are the actual implications of this transition to the tlp ?
>>
>> Regards,
>> Dor
>>
>> -Original Message-
>> From: Anthony Baker [mailto:aba...@pivotal.io]
>> Sent: יום ב 21 נובמבר 2016 19:26
>> To: dev@geode.apache.org
>> Subject: The next release (v1.1.0)
>>
>> Now that graduation is done (!!), we need to organize our next release.  I 
>> propose we focus on completing the transition to TLP and cleaning up 
>> “incubating" references.  The sequence would look something like this:
>>
>> 1) Transition the git repo, mailing lists, etc.
>> 2) Update incubating references in source, docs, website, wiki, …
>> 3) Do a release.
>>
>> Thoughts?
>>
>> We need a release manager.  Any volunteers?
>>
>> Also, we need to rename the JIRA version from 1.1.0-incubating to 1.1.0.  
>> Can someone with JIRA karma help?
>>
>> Anthony
>>
>>
>> This message and the information contained herein is proprietary and
>> confidential and subject to the Amdocs policy statement, you may
>> review at http://www.amdocs.com/email_disclaimer.asp
>
>
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp

Re: Please update your podling status page

[John D. Ament]

Hi Mark,

I did check, you're in the incubator group so you have write access to the 
repo.  What do you get when you try to commit?

I'm in the hipchat room if you have time and can look at this in more real time.

John

On 2016-11-25 14:52 (-0500), Mark Bretl  wrote: 
> Hi John,
> 
> I am working on editing the documents in SVN, however, it seems I do not
> have permission to check in. Would you be able to help me with that or can
> you point me in the right direction?
> 
> Best Regards,
> 
> --Mark
> 
> On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
> wrote:
> 
> > Dear Geode PMC
> >
> > Congratulations on becoming a top level project.  Please complete your
> > incubator graduation steps.  They can be found here:
> > http://incubator.apache.org/guides/graduation.html#unincubate
> >
> > John
> >
> 

Re: Please update your podling status page

[John D. Ament]

To give a summary of what we're talking about on hipchat

- do a 'svn info' and check the URL.  It should be "URL: 
https://svn.apache.org/repos/asf/incubator/public/trunk";
- If its not (double check the http vs https) use svn relocate to change to 
this URL

John

On 2016-11-25 16:20 (-0500), "John D. Ament" wrote: 
> Hi Mark,
> 
> I did check, you're in the incubator group so you have write access to the 
> repo.\u2002\u2002What do you get when you try to commit?
> 
> I'm in the hipchat room if you have time and can look at this in more real 
> time.
> 
> John
> 
> On 2016-11-25 14:52 (-0500), Mark Bretl  wrote: 
> > Hi John,
> > 
> > I am working on editing the documents in SVN, however, it seems I do not
> > have permission to check in. Would you be able to help me with that or can
> > you point me in the right direction?
> > 
> > Best Regards,
> > 
> > --Mark
> > 
> > On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
> > wrote:
> > 
> > > Dear Geode PMC
> > >
> > > Congratulations on becoming a top level project.  Please complete your
> > > incubator graduation steps.  They can be found here:
> > > http://incubator.apache.org/guides/graduation.html#unincubate
> > >
> > > John
> > >
> > 
> 

Re: Please update your podling status page

[Mark Bretl]

Hi John,

Thanks for looking into it, I think it was the HTTP -> HTTPS issue. I have
checked-in the changes, anything I need to do to make them live on the
Incubator website?

Thanks again for your help,

--Mark

On Fri, Nov 25, 2016 at 1:30 PM, John D. Ament 
wrote:

> To give a summary of what we're talking about on hipchat
>
> - do a 'svn info' and check the URL.  It should be "URL:
> https://svn.apache.org/repos/asf/incubator/public/trunk";
> - If its not (double check the http vs https) use svn relocate to change
> to this URL
>
> John
>
> On 2016-11-25 16:20 (-0500), "John D. Ament" wrote:
> > Hi Mark,
> >
> > I did check, you're in the incubator group so you have write access to
> the repo.\u2002\u2002What do you get when you try to commit?
> >
> > I'm in the hipchat room if you have time and can look at this in more
> real time.
> >
> > John
> >
> > On 2016-11-25 14:52 (-0500), Mark Bretl  wrote:
> > > Hi John,
> > >
> > > I am working on editing the documents in SVN, however, it seems I do
> not
> > > have permission to check in. Would you be able to help me with that or
> can
> > > you point me in the right direction?
> > >
> > > Best Regards,
> > >
> > > --Mark
> > >
> > > On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
> > > wrote:
> > >
> > > > Dear Geode PMC
> > > >
> > > > Congratulations on becoming a top level project.  Please complete
> your
> > > > incubator graduation steps.  They can be found here:
> > > > http://incubator.apache.org/guides/graduation.html#unincubate
> > > >
> > > > John
> > > >
> > >
> >
>

Re: Please update your podling status page

[John D. Ament]

Hi Mark,

I published the website.  You're good to go now.

Thanks!

John

On 2016-11-25 16:34 (-0500), Mark Bretl  wrote: 
> Hi John,
> 
> Thanks for looking into it, I think it was the HTTP -> HTTPS issue. I have
> checked-in the changes, anything I need to do to make them live on the
> Incubator website?
> 
> Thanks again for your help,
> 
> --Mark
> 
> On Fri, Nov 25, 2016 at 1:30 PM, John D. Ament 
> wrote:
> 
> > To give a summary of what we're talking about on hipchat
> >
> > - do a 'svn info' and check the URL.  It should be "URL:
> > https://svn.apache.org/repos/asf/incubator/public/trunk";
> > - If its not (double check the http vs https) use svn relocate to change
> > to this URL
> >
> > John
> >
> > On 2016-11-25 16:20 (-0500), "John D. Ament" wrote:
> > > Hi Mark,
> > >
> > > I did check, you're in the incubator group so you have write access to
> > the repo.\u2002\u2002What do you get when you try to commit?
> > >
> > > I'm in the hipchat room if you have time and can look at this in more
> > real time.
> > >
> > > John
> > >
> > > On 2016-11-25 14:52 (-0500), Mark Bretl  wrote:
> > > > Hi John,
> > > >
> > > > I am working on editing the documents in SVN, however, it seems I do
> > not
> > > > have permission to check in. Would you be able to help me with that or
> > can
> > > > you point me in the right direction?
> > > >
> > > > Best Regards,
> > > >
> > > > --Mark
> > > >
> > > > On Fri, Nov 25, 2016 at 9:05 AM, John D. Ament 
> > > > wrote:
> > > >
> > > > > Dear Geode PMC
> > > > >
> > > > > Congratulations on becoming a top level project.  Please complete
> > your
> > > > > incubator graduation steps.  They can be found here:
> > > > > http://incubator.apache.org/guides/graduation.html#unincubate
> > > > >
> > > > > John
> > > > >
> > > >
> > >
> >
> 

Re: The next release (v1.1.0)

[Nitin Lamba]

I did some JIRA housekeeping today [1]:
- Closed 1.0.0-incubating.M3 sprint
- Created 1.1.0 sprint and moved JIRAs identified with 'Fix Versions' into
scope
- Created a new Quick Filter for CI Failures

Is there a separate thread for discussing 1.1.0 scope or should we start a
new one?

Thanks,
Nitin
[1]
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=92&view=planning.nodetail


On Fri, Nov 25, 2016 at 12:45 PM, Dor Ben Dov 
wrote:

> Hi Anthony
>
> Thanks for the answer.
>
> Dor
>
>  Original Message 
>
> Subject: Re: The next release (v1.1.0)
>
> From: Anthony Baker 
>
> Date: 25 בנוב' 2016, 16:44
>
> To: dev@geode.apache.org
>
> Hi Dor,
>
> I want to stress that the transition was from an Apache Incubator
> subproject to an Apache TLP.  The individual committers and PMC members in
> the Geode community will continue to drive the project forward.
>
> Anthony
>
> > On Nov 23, 2016, at 1:03 AM, Dor Ben Dov  wrote:
> >
> > Anthony,
> >
> > Are you (all pivotal developers / architects) who are here in the
> community will now leave once this being managed by
> > Itself or are you continuing to contribute?
> > Regards,
> > Dor
> >
> > -Original Message-
> > From: Anthony Baker [mailto:aba...@pivotal.io]
> > Sent: יום ג 22 נובמבר 2016 16:44
> > To: geode 
> > Subject: Re: The next release (v1.1.0)
> >
> > Transitioning from an incubating project to a top-level project means we
> keep doing exactly what we’ve been doing—except that now the project is
> responsible for managing itself.  We will be transitioning a few resources
> such as mailing lists and git repos to reflect that we are no longer an
> incubator subproject.
> >
> > See http://incubator.apache.org/guides/graduation.html.
> >
> > Anthony
> >
> >> On Nov 21, 2016, at 11:57 AM, Dor Ben Dov 
> wrote:
> >>
> >> Anthony,
> >>
> >> What are the actual implications of this transition to the tlp ?
> >>
> >> Regards,
> >> Dor
> >>
> >> -Original Message-
> >> From: Anthony Baker [mailto:aba...@pivotal.io]
> >> Sent: יום ב 21 נובמבר 2016 19:26
> >> To: dev@geode.apache.org
> >> Subject: The next release (v1.1.0)
> >>
> >> Now that graduation is done (!!), we need to organize our next
> release.  I propose we focus on completing the transition to TLP and
> cleaning up “incubating" references.  The sequence would look something
> like this:
> >>
> >> 1) Transition the git repo, mailing lists, etc.
> >> 2) Update incubating references in source, docs, website, wiki, …
> >> 3) Do a release.
> >>
> >> Thoughts?
> >>
> >> We need a release manager.  Any volunteers?
> >>
> >> Also, we need to rename the JIRA version from 1.1.0-incubating to
> 1.1.0.  Can someone with JIRA karma help?
> >>
> >> Anthony
> >>
> >>
> >> This message and the information contained herein is proprietary and
> >> confidential and subject to the Amdocs policy statement, you may
> >> review at http://www.amdocs.com/email_disclaimer.asp
> >
> >
> > This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> > you may review at http://www.amdocs.com/email_disclaimer.asp
>
>

[GitHub] incubator-geode pull request #296: GEODE-2109 : Calling submit on ExecutionS...

[deepakddixit]

GitHub user deepakddixit opened a pull request:

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

GEODE-2109 : Calling submit on ExecutionService can cause exceptions to be 
lost

Replaced submit call with execute.
Refactored GIITask calls from DiskStoreImpl. Async task like Creating KRF's 
through disk store are replaced with execute. The other call is kept with 
submit as we later check for whether delayed write is completed or not.
Added RejectedExecutionException to IgnoredException list as from these 
tests it may get occasionally thrown and as we moved to execute method of 
ExecutorService they will be logged.

All precheckin tests are passing except one 
org.apache.geode.management.internal.cli.commands.IndexCommandsDUnitTest.testCreateDestroyUpdatesSharedConfig
 which is marked as Flaky.

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

$ git pull https://github.com/deepakddixit/incubator-geode bugfix/GEODE-2109

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

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

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

This closes #296


commit 8c4aeaae23d242b9a4edfe328bd4046e5626914d
Author: Deepak Dixit 
Date:   2016-11-23T16:03:14Z

GEODE-2109: Replacing ExecutorService.submit calls with 
ExecutorService.execute call.
This will help in logging exceptions those come in the thread.

commit db213bb1d0982db12ffc5e8d2649cec8f69147c6
Author: Deepak Dixit 
Date:   2016-11-24T06:27:58Z

 GEODE-2109: Replacing ExecutorService.submit calls with 
ExecutorService.execute call for DiskStoreTask.

Refactored DiskStore task for delayed writes, we cannot replace expensive 
writes tasks submit call with execute as later we check if write call is 
completed or not.
 Replaced submit call by execute in case of DiskStore tasks like 
compactions, creating KRF's.

commit 478a714979ace2f187ebf336c0d5121a0a5c8940
Author: Deepak Dixit 
Date:   2016-11-24T12:21:54Z

 GEODE-2109: Replacing ExecutorService.submit calls with 
ExecutorService.execute call for DiskStoreTask.

Replaced submit call for GIITask and RemoveMember tasks. GIITask is used 
when adding member or starting managing activity when node becomes managing 
node. While adding member we can make the ExecutorService.execute call. Not 
changed call for GIITask when invoked from managing activity as possible 
exception is handled.

commit b501654a3718f3e15cc45b9bd757bfb558f664a1
Author: Deepak Dixit 
Date:   2016-11-24T16:27:38Z

 GEODE-2109: Replacing ExecutorService.submit calls with 
ExecutorService.execute call for DiskStoreTask.
Ignoring rejectedException as this can be thrown in case pool is shutting 
down.

commit 9e56037ac21768adde9c35c97bc8e0cb463042b7
Author: Deepak Dixit 
Date:   2016-11-24T17:17:53Z

 GEODE-2109: Replacing ExecutorService.submit calls with 
ExecutorService.execute call for DiskStoreTask.
Changing way creating GIITask when node becomes managing node.

commit 3b8273b7746f5b4af329c92c92fac07e6571cf05
Author: Deepak Dixit 
Date:   2016-11-25T05:15:26Z

 GEODE-2109: Replacing ExecutorService.submit calls with 
ExecutorService.execute call for DiskStoreTask.
Adding ignoredException for MemoryThresholdsDUnitTest.

commit 5cf0aac229c595b91436c4d327d43444120698b5
Author: Deepak Dixit 
Date:   2016-11-25T08:05:39Z

 GEODE-2109: Replacing ExecutorService.submit calls with 
ExecutorService.execute call for DiskStoreTask.
Adding ignoredException for EvictionStatsDUnitTest.

commit ed24011d0b1456b0247bd0254af252cae351eb07
Author: Deepak Dixit 
Date:   2016-11-26T04:02:26Z

 GEODE-2109: Replacing ExecutorService.submit calls with 
ExecutorService.execute call for DiskStoreTask.
Applying spotless checks.




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