Re: [DISCUSS] consistency of command result status

2017-11-09 Thread Patrick Rhomberg
I definitely favor consistency along (what seems to me to be) common-sense
divisions.  I personally feel like an OK status should only occur when the
command hits no hiccups that it can't resolve.

We introduced the ExitCode class this past summer with the intent of
unifying command exit status.  It was beyond the scope of the ticket at the
time and may well be beyond the scope of the issue here, but it could also
be worth discussing if this style of "third party member unreachable"
deserves its own exit code beyond NORMAL(0) and FATAL(1).

On Wed, Nov 8, 2017 at 1:48 PM, Jinmei Liao  wrote:

> We noticed some discrepancies of result status when executing commands that
> involves looking for a member/region/entry/gateway receiver/sender, namely
> any entities. If the command failed to find the entity specified by the
> command, it will output some messages like "xxx not found", but some
> command would report this message as ERROR result and others would report
> this as OK result. For example:
>
> gfsh>describe region --name=notExist
>
> Region : /notExist not found
>
>
> gfsh>describe member --name=notExist
>
> Member "notExist" not found
>
> The first command will show as ERROR status (in red), while the second
> command shows up as OK status (in black). We would like to propose changing
> these kind of "not found" messages as all ERROR (user error) status. This
> would involve some test changes as well.
>
> comments/suggestions?
>
> --
> Cheers
>
> Jinmei
>


Rename DM and DistributionManager

2017-11-09 Thread Kirk Lund
I'd like to do some renaming to use better class names including:

GEODE-3965: Rename DistributionManager to ClusterDistributionManager and DM
to DistributionManager

The results would be:

* interface = DistributionManager
* impl for cluster = ClusterDistributionManager
* impl for loner = LonerDistributionManager

Please let me know if anyone feels strongly against this rename.

Thanks!
Kirk


Re: Rename DM and DistributionManager

2017-11-09 Thread Darrel Schneider
+1

On Thu, Nov 9, 2017 at 12:18 PM, Kirk Lund  wrote:

> I'd like to do some renaming to use better class names including:
>
> GEODE-3965: Rename DistributionManager to ClusterDistributionManager and DM
> to DistributionManager
>
> The results would be:
>
> * interface = DistributionManager
> * impl for cluster = ClusterDistributionManager
> * impl for loner = LonerDistributionManager
>
> Please let me know if anyone feels strongly against this rename.
>
> Thanks!
> Kirk
>


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

2017-11-09 Thread Spring CI

---
Spring Data GemFire > Nightly-ApacheGeode > #735 was successful.
---
Scheduled
2189 tests in total.

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





--
This message is automatically generated by Atlassian Bamboo

[DRAFT] Geode Board Report November 2017

2017-11-09 Thread Joey McAllister
Hi folks,

Please review the below draft of our report to the board for this past quarter
and offer corrections. As Mark mentioned, we need to submit the draft ASAP,
preferably before the weekend. Please review and comment by 5p Pacific Time
tomorrow (i.e., about 24 hours from now).

I do have one question regarding the mailing list health: Does anyone have
any thoughts about the decline in email count to the Dev list? We have
about half the number of emails to the Dev list as we had in the previous
quarter, and that number also declined between the previous two reports. I
suspect that this might be related to the creation of the Issues email list
(and that the number has now stabilized), but I wanted to put it to the
community.

Thanks!
Joey

-

## Description:
- Apache Geode provides a database-like consistency model, reliable
transaction
  processing and a shared-nothing architecture to maintain low-latency
  performance with high-concurrency processing.

## Issues:
- There are no issues requiring board attention.

## Activity:
- Released Geode 1.3.0 with 371 resolved tickets, including the following
  improvements:
  - Finer-grained security
  - The ability to snapshot multiple regions simultaneously
  - New Geode examples:
- Putting multiple values at once
- Demonstrating Lucene indexing and searching

## Health report:
- We’re continuing to work on attracting new contributors and making it
easier
  to participate in the community.
- Mailing list activity is healthy.
- Work has started toward the next Geode 1.4.0 release, with a plan to
include
  the new client/server protocol.

## PMC changes:
- Currently 41 members
- New PMC members:
  - David Kimura was added to the PMC on Sun Sep 10 2017.
  - Galen O'Sullivan was added to the PMC on Mon Sep 25 2017.
  - Mike Stolz was added to the PMC on Sun Oct 29 2017.
  - Nick Reich was added to the PMC on Thu Oct 19 2017.
  - Patrick Rhomberg was added to the PMC on Tue Oct 31 2017.

## Committer base changes:
- Currently 86 committers.
- New committers:
  - David Kimura was added as a committer on Mon Sep 11 2017.
  - Galen O'Sullivan was added as a committer on Tue Sep 05 2017.
  - Mike Stolz was added as a committer on Sat Oct 21 2017.
  - Nick Reich was added as a committer on Sat Oct 14 2017.
  - Patrick Rhomberg was added as a committer on Wed Nov 01 2017.

## Releases:
- Most recent release was 1.3.0 on Tue Oct 31 2017. Geode 1.3.0 contains a
  number of bug fixes and improvements, including finer-grained security and
  the ability to snapshot multiple regions simultaneously.
  - Release notes:

https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.3.0
  - Release artifacts: http://geode.apache.org/releases/
  - Release documentation:
http://geode.apache.org/docs/guide/13/about_geode.html

## Mailing list activity:
- dev@geode.apache.org:
  - 175 subscribers (up 1 in the last 3 months):
  - 2030 emails sent to list (4170 in previous quarter)

- iss...@geode.apache.org:
  - 55 subscribers (down 1 in the last 3 months):
  - 4883 emails sent to list (3066 in previous quarter)

- u...@geode.apache.org:
  - 234 subscribers (up 2 in the last 3 months):
  - 236 emails sent to list (277 in previous quarter)

## JIRA activity:
- 547 JIRA tickets created in the last 3 months
- 422 JIRA tickets closed/resolved in the last 3 months


Errored: apache/geode#4764 (MessagePack - 5d39e4a)

2017-11-09 Thread Travis CI
Build Update for apache/geode
-

Build: #4764
Status: Errored

Duration: 6 minutes and 54 seconds
Commit: 5d39e4a (MessagePack)
Author: kohlmu-pivotal
Message: Getting closer to some level of madness

View the changeset: 
https://github.com/apache/geode/compare/cbf65e7b37c4^...5d39e4ab968b

View the full build log and details: 
https://travis-ci.org/apache/geode/builds/299935138?utm_source=email&utm_medium=notification

--

You can configure recipients for build notifications in your .travis.yml file. 
See https://docs.travis-ci.com/user/notifications



Broken: jinmeiliao/geode#80 (assert - fcb8bfa)

2017-11-09 Thread Travis CI
Build Update for jinmeiliao/geode
-

Build: #80
Status: Broken

Duration: 15 minutes and 31 seconds
Commit: fcb8bfa (assert)
Author: Jinmei Liao
Message: GEODE-3872: simplify the Command result Assert

View the changeset: 
https://github.com/jinmeiliao/geode/compare/4f13db8c8bf5...fcb8bfa6286e

View the full build log and details: 
https://travis-ci.org/jinmeiliao/geode/builds/300020321?utm_source=email&utm_medium=notification

--

You can configure recipients for build notifications in your .travis.yml file. 
See https://docs.travis-ci.com/user/notifications