-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
K4 Beta2 to Beta3 upgrade issues #2497
Comments
I have problems after upgrade as well - just an empty page on http://logs:5601/#/undefined after I visit my site at http://logs:5601/ |
I ran into issue as well after upgrading to beta3 Segmented Fetch: SearchPhaseExecutionException[Failed to execute phase [query], all shards failed; shardFailures while it's working fine without any issue in kibana beta2. |
Same problem here |
Duplicate of #2377 |
Same here. @rashidkpc the global settings issue is just part of the problem, the other is that existing dashboards don't function anymore after the upgrade. I don't know if you want to support the upgrade or not. Did anyone find a way to edit the dashboard objects manually to fix this problem? |
Okay it's fairly easy to fix manually, just find the saved dashboard object (under Settings -> Objects) and in the kibanaSavedObjectMeta... field, turn the "filter" object into an array with the existing object as its only element. If that doesn't make sense, just create a new dashboard and look at how that field is structured. |
Yeah, we definitely don't guarantee object schemas across the betas, we will support upgrades after GA though. |
@tmandry Thanks for the hint, works like a charm. |
I also created this #2620 |
Not sure if we intend to provide an upgrade path from K4 beta2 to beta3.
The following are issues after upgrading from beta2 to beta3. The upgrade is done by taking a snapshot of the .kibana index, restoring it to another cluster and then associating beta3 to it so it will automatically pick up the existing .kibana index (from beta2).
Beta3 is brought up, the saved searches show up fine (and work) from the Discover screen.
The following is the underlying error:
The issue here is that the query sent by K4 Beta3 has an extra filter clause (1st bool clause below) and this extra clause is invalid, missing the
query
clause wrapper:If I then stop beta3, launch beta2 (associated to the same cluster, reading from the same .kibana index without doing anything else), the dashboard starts to work properly again.
The text was updated successfully, but these errors were encountered: