--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+unsubscribe@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/30b51744-635a-4a43-9ff4-b5998e59e517%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
This is Double.MAX_VALUE and probably means that the estimate was too large to correct via the algorithm we use. Is this reproducible? And do you think your "real" unique counts are larger than about 10^19?
Gian
On Wed, Feb 1, 2017 at 11:36 AM, Federico Nieves <federic...@gmail.com> wrote:
Hi!When doing a topN query, asking for hyperLogLog metric, sometimes we get values like these:1.7976931348623157E308The weird thing is that for many different values we get that number (and they should differ in normal cases). Is this an error on our environment? Or maybe a wrong format on the output? Can we specify the format in which we want to obtain the metric (integer, float, etc)?Thanks,
--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+unsubscribe@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/a23359d5-7531-433a-97ee-b2b2867e40c7%40googlegroups.com.
Gian
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/0b919c8a-b68b-4e56-87a7-99935e8d255f%40googlegroups.com.
Gian
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+unsubscribe@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/da281b03-8045-4e11-8aab-bd4a364ed612%40googlegroups.com.
Gian
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/815742b7-86e5-4bc1-8f60-86fbbe6cd6cf%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+unsubscribe@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/ef374f3e-5ca7-435e-94b9-637de7f12eb0%40googlegroups.com.
I wonder if this is a similar issue to https://github.com/druid-io/druid/issues/4199. Are you all ever seeing exceptions too or just weird results?
Gian
On Fri, May 19, 2017 at 8:43 AM, Federico Nieves <federic...@gmail.com> wrote:
Don't you get any logs on the historical server when it gets out from the cluster?No, we don't use AWS, we use physical dedicated servers with Samsung SSDs.Also I shared a script that checks for segment integrity between segments on deep-storage and segments present on historicals. But I made that using HDFS as deep storage, in your case you should change it to work with S3, but could be useful to double-check that segments are not corrupted.
On Friday, May 19, 2017 at 12:31:38 PM UTC-3, Jakub Liska wrote:Hi,thank you for suggestions, we have small 30-60MB segments and we don't use real time indexing, so reindexing should not be necessary at all :-/What instances are you using, isn't it i3 by any chance? With those NVMe SSD ?
--
You received this message because you are subscribed to the Google Groups "Druid User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+...@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to druid-user+unsubscribe@googlegroups.com.
To post to this group, send email to druid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/druid-user/1a668be3-48e3-4da5-86f3-f1a9e76ca297%40googlegroups.com.