Skip to content
This repository has been archived by the owner on Aug 23, 2023. It is now read-only.

Better document priority ready state #1223

Merged
merged 4 commits into from
Feb 12, 2019

Conversation

Dieterbe
Copy link
Contributor

No description provided.

@Dieterbe Dieterbe force-pushed the better-document-priority-ready-state branch from 9c9578f to 0bccd24 Compare February 12, 2019 11:30
docs/clustering.md Outdated Show resolved Hide resolved
docs/clustering.md Outdated Show resolved Hide resolved
woodsaj and others added 2 commits February 12, 2019 14:25
Co-Authored-By: Dieterbe <dieter@plaetinck.be>
Co-Authored-By: Dieterbe <dieter@plaetinck.be>
Copy link
Member

@woodsaj woodsaj left a comment

Choose a reason for hiding this comment

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

lgtm

@Dieterbe Dieterbe added this to the vnext milestone Feb 12, 2019
@Dieterbe Dieterbe merged commit d02ac35 into master Feb 12, 2019
@DanCech
Copy link
Contributor

DanCech commented Feb 12, 2019

This could use a description of what kafka-mdm-in | estimate of consumer lag actually means. Also gossiped is the correct spelling, not gossipped.

@Dieterbe
Copy link
Contributor Author

@DanCech can you clarify? that's the syntax for a table row. should i elaborate on how we do the estimation? i consider that an implementation detail

@Dieterbe Dieterbe deleted the better-document-priority-ready-state branch March 27, 2019 21:08
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.

3 participants