Closed yangfan1224 closed 6 years ago
Hi @yangfan1224 . Thanks for your issue report. I will try to re-create the issue here. What version of the Pilosa Java client are you using? A released one, or from the master branch or one of the PRs ?
I use java client 1.0.0 which build from the master code by myself. if you want to reproduce the bugs, besides the java client version, you should better set the replica param of cluster more than 1.
Yuce Tekol notifications@github.com 于 2018年8月15日周三 23:14写道:
Hi @yangfan1224 https://github.com/yangfan1224 . Thanks for your issue report. I will try to re-create the issue here. What version of the Pilosa Java client are you using? A released one, or from the master branch or one of the PRs ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pilosa/pilosa/issues/1598#issuecomment-413229780, or mute the thread https://github.com/notifications/unsubscribe-auth/ABwuvOGiauvRfCCA2lJWXk9_51AXYdcLks5uRDrvgaJpZM4V74U0 .
Thanks. I was able to reproduce the problem with both the Java client and a shell script. We are investigating the problem.
@yangfan1224 the latest code on master addresses this bug. Thanks for the bug report, and let us know if you still have problems with anything.
For bugs, please provide the following:
Expected behavior
I create a time type field, TimeQuantum is TimeQuantum.DAY, then write some simple data with different date, when I query data using Range API with specific date param, the query reuslt should be I write on the specific date.
Actual behavior
after writing data into pilosa, I can get correct result for some minutes, but if i go on querying, no matter the date param is , the result is all data write in different date views .
Steps to reproduce the behavior
to reproduce the behavior , i write a simple test code as follows, you can run it untill the bug produce.
Information about your environment (OS/architecture, CPU, RAM, cluster/solo, configuration, etc.)
OS/architecture CentOS7.4 linux-amd64 pilosa: 5 nodes cluster pilosa version: v1.0.2 or mater code until 13 Aug. configuration: data-dir = "/data01/pilosa/data" bind = "servicenode08:10101" verbose = true [gossip] port = 22000 seeds = "servicenode08:22000"
[cluster] replicas = 2 coordinator = true
For feature requests, please provide the following:
Description
during search on this issue, I foud that this bug only show on pilosa cluster, not a single node, and it can show correct results for about five to ten minutes, so i guess the bug is caused by data sync between cluster nodes.
Success criteria (What criteria will consider this ticket closeable?)