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.9.2] cluster replication issue for measurement name containing backslash #3704

Closed
beckettsean opened this issue Aug 17, 2015 · 0 comments
Closed

Comments

@beckettsean
Copy link
Contributor

From a note sent to the support team, recreating it here:


I am running on 3 nodes CENTOS 6.6 and i have created InfluxDB Cluster Configuration as very well exaplined in docs section. (i have installed InfluxDB 0.9.2 on all 3 nodes).

On the first node i created a database with: create database mydb which appeared on the other 3 nodes. I have inserted a measurement called cpu_load which also appeared on the other 3 nodes. All good and working as expected until now.

I have inserted another measurement called "cpu time" using the following line command: insert cpu\ time,hostname=server01 value=100. On this node i could succesfully query it and i had the following results:

> show series
name: cpu time
--------------
_key hostname
cpu\ time,hostname=server01 server01

Now when i tried to query it on the other nodes, i got a slightly different result:(pay attention to _key):

On 2nd and 3rd node:

> show series
name: cpu time
--------------
_key hostname
cpu\\ time,hostname=server01 server01

So my guess is that when we insert measurements containing spaces, the replication is not working very well - it seems to add one more backslash to measurement _key on the other nodes.


There are two bugs here: one is that the backslash gets duplicated when copied to the other nodes. The second is that the insert statement should never have created a measurement name with a backslash, it should have preserved the space. The second bug is fixed in 0.9.3 I believe, but the first is likely still valid.

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

1 participant