Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Michael BlowMichael BlowReporter
Umang AgrawalUmang Agrawal(Deactivated)Is this a Regression?
NoTriage
UntriagedOperating System
Centos 64-bitStory Points
1Sprint
NonePriority
MajorInstabug
Open Instabug
Details
Details
Assignee
Michael Blow
Michael BlowReporter
Umang Agrawal
Umang Agrawal(Deactivated)Is this a Regression?
No
Triage
Untriaged
Operating System
Centos 64-bit
Story Points
1
Sprint
None
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created July 9, 2021 at 7:49 AM
Updated July 23, 2021 at 9:05 AM
Resolved July 22, 2021 at 1:18 AM
While trying to ingest data from a remote cluster (cluster version 7.1.0-1058), even after the ingestion has completed, the remaining mutation numbers are still seen on webUI and same can also be seen using the analytics/node/agg/stats/remaining API.
Steps to reproduce -
1. Have a remote cluster with 7.1.0 version.
2. Load travel-sample bucket on remote cluster.
3. Create a link to remote cluster from local analytics cluster (local cluster is in 6.6.3 version).
4. Create a remote dataset using the above link.
5. connect the remote link.
Observation -
1. When we connect the link, the initial mutation count is shown as 83129.
2. Ingestion gets completes.
3. Remaining mutation is still shown as 1103.