Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GEODE-6174: more error handling in LocatorClusterConfigurationService #3134

Merged
merged 7 commits into from Jan 31, 2019

Conversation

jinmeiliao
Copy link
Member

  • fail early if cluster persistence serivce is not enabled
  • creating the region twice will result in status code 409
  • if region creation is partially failed on members, do not update cluster configuration.

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

  • Has your PR been rebased against the latest commit within the target branch (typically develop)?

  • Is your initial contribution a single, squashed commit?

  • Does gradlew build run cleanly?

  • Have you written or updated unit tests to verify your changes?

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

* fail early if cluster persistence serivce is not enabled
* creating the region twice will result in status code 409
* if region creation is partially failed on members, do not update cluster configuration.
@jinmeiliao
Copy link
Member Author

@Petahhh @onichols-pivotal

Copy link
Contributor

@jdeppe-pivotal jdeppe-pivotal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once the log statement has been removed.

@@ -79,6 +79,7 @@ public void createsRegion() throws Exception {

@Test
public void createsAPartitionedRegionByDefault() throws Exception {
IgnoredException.addIgnoredException("cache element orders already exists.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should not be dumping exceptions like this into the log. We should not even need to log anything.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree

"successfully persisted config for " + finalGroup);
} catch (Exception e) {
String message = "failed to update cluster config for " + finalGroup;
logger.error(message, e);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto my comment about logging exceptions from above. This can be removed.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we are catching an exception here, if we don't log here, we might lose the stack trace.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh right. Sorry, I thought this was the cause of the IgnoredException.

@jinmeiliao jinmeiliao merged commit 9c35fc7 into apache:develop Jan 31, 2019
@jinmeiliao jinmeiliao deleted the type2 branch January 31, 2019 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants