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.5-rc2]The datas shared with three machines in cluster are Inconsistent, "show shards" has only two onwers #4800

Closed
guaiguaihw opened this issue Nov 15, 2015 · 5 comments

Comments

@guaiguaihw
Copy link

I update influxdb to 0.9.5-rc2 with three machines, but the last one does not have any datas.
My output information is below:
image
image
when I want to "show measurements" ,error occurs:
image

@guaiguaihw
Copy link
Author

My configure file is below:

[meta]
dir = "/data1/influxdb/meta"
hostname = "10.222.11.70"
bind-address = ":8088"
retention-autocreate = true
election-timeout = "1s"
heartbeat-timeout = "1s"
leader-lease-timeout = "500ms"
commit-timeout = "50ms"
cluster-tracing = false
peers = ["10.222.12.134:8088", "10.222.11.81:8088", "10.222.11.70:8088"]

[data]
dir = "/data1/influxdb/data"
max-wal-size = 104857600 # Maximum size the WAL can reach before a flush. Defaults to 100MB.
wal-flush-interval = "10m" # Maximum time data can sit in WAL before a flush.
wal-partition-flush-delay = "2s" # The delay time between each WAL partition being flushed.

These are the WAL settings for the storage engine >= 0.9.3

wal-dir = "/data1/influxdb/wal"
wal-enable-logging = true

[hinted-handoff]
enabled = true
dir = "/data1/influxdb/hh"
max-size = 1073741824
max-age = "168h"
retry-rate-limit = 0

[cluster]
shard-writer-timeout = "10s" # The time within which a shard must respond to write.
write-timeout = "5s" # The time within which a write operation must complete on the cluster.

[retention]
enabled = true
check-interval = "30m"

[shard-precreation]
enabled = true
check-interval = "10m"
advance-period = "30m"

[monitor]
store-enabled = true # Whether to record statistics internally.
store-database = "_internal" # The destination database for recorded statistics
store-interval = "10s" # The interval at which to record statistics

[admin]
enabled = true
bind-address = ":8081"
https-enabled = false
https-certificate = "/etc/ssl/influxdb.pem"

[http]
enabled = true
bind-address = ":8080"
auth-enabled = false
log-enabled = true
write-tracing = false
pprof-enabled = false
https-enabled = false
https-certificate = "/etc/ssl/influxdb.pem"

[continuous_queries]
log-enabled = true
enabled = true
recompute-previous-n = 2
recompute-no-older-than = "10m"
compute-runs-per-interval = 10
compute-no-more-than = "2m"
~/influxdb/conf/influxdb.conf

@guaiguaihw
Copy link
Author

I also confuse that my log shows datas has been written into influxdb:
image
but nothing left in my directory, there are all dropped???
image

@sergzin
Copy link

sergzin commented Nov 15, 2015

Try to set replication factor equal to number of nodes in cluster.

@otoolep
Copy link
Contributor

otoolep commented Nov 15, 2015

@guaiguaihw - what replication factor are you using for the target retention policy?

@dgnorton -- the marshaling error looks like the issue you were looking at.

@beckettsean
Copy link
Contributor

closing as duplicate of #4550.

@guaiguaihw thanks for the report, please add any additional details to #4550, and if possible, copy/paste the text from the terminal rather than screenshots.

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

4 participants