-
Notifications
You must be signed in to change notification settings - Fork 74
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
Unable get trends of Unique Users. #485
Comments
👋 Hi! Can you please check the logs from the |
Hi below is the log from web service.
|
Thank you for the additional info. Is this error coming from a brand new installation or did you do an upgrade from a previous version? Can you please also check the migration job logs? |
Sorry I meant the migration pod logs
…On Fri, 15 Jul 2022 at 05:42, yog27ray ***@***.***> wrote:
This is coming from a brand new installation. I am attaching the Async
Migrations page screenshot.
[image: Screenshot 2022-07-15 at 9 07 01 AM]
<https://user-images.githubusercontent.com/9247177/179145453-62d42838-98b6-44d4-899f-5e177a575742.png>
—
Reply to this email directly, view it on GitHub
<#485 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA6Z3GP5XF23XSOG6PW2C43VUDMZPANCNFSM53N7OF5A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This issue has 2238 words at 5 comments. Issues this long are hard to read or contribute to, and tend to take very long to reach a conclusion. Instead, why not:
Is this issue intended to be sprawling? Consider adding label |
Hi below are the logs from migration pod
|
@guidoiaquinti is anything else needed from my side? |
From a first look it seems your ClickHouse installation is missing a table I see you are running a sharded and replicated setup for ClickHouse. Did you added sharding and replicas after the initial un-sharded/un-replicated installation or did you start from scratch with this topology? cc @hazzadous |
@guidoiaquinti I tried multiple times installations from scratch but every time it ends up in the same situation. |
We'll try to repro and debug on our end. Thank you for your report! 🙇 |
I'll add this to my list of Support tickets to handle and will get around to looking hopefully today. |
I didn't get around to this last week. I'm unlikely to get around today either. @guidoiaquinti if you have a chance to repro... 🙏 Ok things that I think are important:
|
There is a problem only when I do a fresh deployment with sharding and replica. |
Got to know that the sharing upgrade worked. We’ll need to put some tests for the initial sharding |
@hazzadous after some time of upgrade now I am again getting the same error.
I will try again with only the replica configured without a shard. |
@hazzadous I tried with only replica configured and that is working perfectly fine. When I update the deployment with the shared config I again start getting the same error, and when I remove the shared the same deployment starts working fine again. |
Ok I think this feature isn’t fully baked yet 😞 is it an option to go unsharded for now until we have sorted this? |
@hazzadous for now I am not using the shared only replica. Will wait for the fix. |
I'm having exact same issue. Maybe related? |
While creating trends with unique users I am getting errors in api response. But when I change it from "unique users" to "Total users" everything is working fine. I even tried doing a fresh deployment but still facing the same issue.
Error in API
kubectl version
): v1.23.5-gke.1503helm list -n posthog
): 1.37.1values.yml
Screen.Recording.2022-07-13.at.2.39.41.PM.mp4
The text was updated successfully, but these errors were encountered: