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

[0.10.0] SHOW TAG KEYS doesn't work on partially-replicated cluster #5591

Closed
e-dard opened this issue Feb 9, 2016 · 2 comments
Closed

[0.10.0] SHOW TAG KEYS doesn't work on partially-replicated cluster #5591

e-dard opened this issue Feb 9, 2016 · 2 comments
Milestone

Comments

@e-dard
Copy link
Contributor

e-dard commented Feb 9, 2016

SHOW TAG KEYS does not work correctly when running on a partially replicated cluster. I've tested this on a 3-node cluster with a replication factor of 1.

Weirdly, even the node with the shard on it isn't able to return the tag keys.

Node 1:

> create database db
> use db
Using database db
> alter retention policy default on db REPLICATION 1
> insert cpu,tk=tv value=1
> show tag keys
ERR: write message type: write tcp [::1]:53109->[::1]:8288: use of closed network connection
> show measurements
name: measurements
------------------
name
cpu

>

Node 2 (after all commands on node 1 have completed):

> show tag keys
ERR: write message type: write tcp [::1]:53118->[::1]:8188: use of closed network connection
> show series
name: cpu
---------
_key        tk
cpu,tk=tv   tv

>

Node 3 (after all commands on node 1 have completed):

> show tag keys
ERR: write message type: write tcp [::1]:53193->[::1]:8288: use of closed network connection
> show series
> show measurements
name: measurements
------------------
name
cpu

>

Logs attached (no panics).

n1.txt
n2.txt
n3.txt

@rossmcdonald rossmcdonald added this to the 0.11.0 milestone Feb 9, 2016
@e-dard e-dard mentioned this issue Feb 10, 2016
8 tasks
@jsternberg
Copy link
Contributor

This should work as soon as #5811 gets merged since this command is already converted to the new query engine.

@jsternberg
Copy link
Contributor

This works now that remote execution works since #5811, #5842, and #5843 have been merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants