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

xds: apply valid resources while NACKing update #8506

Merged
merged 2 commits into from Sep 12, 2021

Conversation

dapengzhang0
Copy link
Member

Implementing gRFC A46

@ejona86 ejona86 added the TODO:backport PR needs to be backported. Removed after backport complete label Sep 10, 2021
xds/src/main/java/io/grpc/xds/ClientXdsClient.java Outdated Show resolved Hide resolved
}

handleResourcesAccepted(ResourceType.CDS, parsedResources, versionInfo, nonce);
// CDS responses represents the state of the world, EDS resources not referenced in CDS
Copy link
Member

Choose a reason for hiding this comment

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

Why do we even need logic like this? If EDS is no longer needed then the subscriber will go away and we'll naturally stop watching it. I remember discussing this in the past, but maybe I don't remember the previous resolution.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, we had a very long debate with @voidzcy one/two years ago. There was very subtle reason that convinced me to accept this approach, but I can't recall now.

I'm keeping this behavior in this PR to implement the change, but therefore I have to add code like https://github.com/grpc/grpc-java/pull/8506/files/5fe2a6bc3dd52f2687a91903732c443567c0e6b1#diff-6b019eb1d3518381d336168847890513a235ea4974fcb3c76a2e9ace43f1d460R2036-R2052 which makes ClientXdsClient so strongly coupled with LdsUpdate and CdsUpdate's deeply nested fields, or with LDS/CDS config's semantic.

// Notify the watchers.
if (parsedResources.containsKey(resourceName)) {
subscriber.onData(parsedResources.get(resourceName), version, updateTime);
} else if (type == ResourceType.LDS || type == ResourceType.CDS) {
if (subscriber.data != null && invalidResources.contains(resourceName)) {
Copy link
Member

Choose a reason for hiding this comment

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

It seems this condition should move into the invalidResources.contains(resourceName) case above and then we combine the invalidResources.contains(resourceName into the if-else chain.

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure how to simplify this. The subscriber.onAbsent() below still need (the negation of) this condition. I grouped the logic regarding retainedResources and onAbsent() together because they are related.

Copy link
Member

Choose a reason for hiding this comment

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

I was thinking:

if (invalidResources.contains(resourceName)) {
  subscriber.onRejected(version, updateTime, errorDetail);
  if (subscriber.data != null) {
    if (type == ResourceType.LDS) {
      ...
      retainedResources.add(rdsName);
    } else if (type == ResourceType.CDS) {
      ...
      retainedResources.add(edsName);
    }
  }
} else if (parsedResources.containsKey(resourceName)) {
  subscriber.onData(parsedResources.get(resourceName), version, updateTime);
} else if (type == ResourceType.LDS || type == ResourceType.CDS) {
  subscriber.onAbsent();
}

But I can live with what's here.

// Notify the watchers.
if (parsedResources.containsKey(resourceName)) {
subscriber.onData(parsedResources.get(resourceName), version, updateTime);
} else if (type == ResourceType.LDS || type == ResourceType.CDS) {
if (subscriber.data != null && invalidResources.contains(resourceName)) {
Copy link
Member

Choose a reason for hiding this comment

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

I was thinking:

if (invalidResources.contains(resourceName)) {
  subscriber.onRejected(version, updateTime, errorDetail);
  if (subscriber.data != null) {
    if (type == ResourceType.LDS) {
      ...
      retainedResources.add(rdsName);
    } else if (type == ResourceType.CDS) {
      ...
      retainedResources.add(edsName);
    }
  }
} else if (parsedResources.containsKey(resourceName)) {
  subscriber.onData(parsedResources.get(resourceName), version, updateTime);
} else if (type == ResourceType.LDS || type == ResourceType.CDS) {
  subscriber.onAbsent();
}

But I can live with what's here.

@dapengzhang0 dapengzhang0 merged commit 7a65c74 into grpc:master Sep 12, 2021
@dapengzhang0 dapengzhang0 deleted the nack-and-apply branch September 12, 2021 04:57
dapengzhang0 added a commit to dapengzhang0/grpc-java that referenced this pull request Sep 13, 2021
@dapengzhang0 dapengzhang0 removed the TODO:backport PR needs to be backported. Removed after backport complete label Sep 13, 2021
dapengzhang0 added a commit that referenced this pull request Sep 13, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants