"Upgrading" to 1.4 has been a clusterfuck for us. It's broken pretty much everything we rely on. I need to go back to 1.3, can I use the snapshot feature?
Will a snapshot taken on a 1.4 cluster restore to a separate 1.3 cluster ?
I'm really just interested in the data, I'd like to reapply my own mappings as the data is ingested into 1.3
Should I be looking at a third party script or will the snapshot/restore features of elastic search be adequate ?
"Upgrading" to 1.4 has been a clusterfuck for us. It's broken pretty much everything we rely on. I need to go back to 1.3, can I use the snapshot feature?
Will a snapshot taken on a 1.4 cluster restore to a separate 1.3 cluster ?
I'm really just interested in the data, I'd like to reapply my own mappings as the data is ingested into 1.3
Should I be looking at a third party script or will the snapshot/restore features of Elasticsearch be adequate ?
"Upgrading" to 1.4 has been a clusterfuck for us. It's broken pretty much
everything we rely on. I need to go back to 1.3, can I use the snapshot
feature?
Will a snapshot taken on a 1.4 cluster restore to a separate 1.3 cluster ?
I'm really just interested in the data, I'd like to reapply my own
mappings as the data is ingested into 1.3
Should I be looking at a third party script or will the snapshot/restore
features of Elasticsearch be adequate ?
I will be more than happy to hear about what went wrong for you with
upgrading?
Well Kibana 4 is unusable for us, the lack of auto refresh killed it for us.
Most of the time K4 simply doesn't work even for browsing small sets, I'd
say 2 times in 3 we get the 300000 ms timeout error, is there a solution to
this yet ?
And when we finally do get any results it's as slow as a pig on crutches.
I need to go back to my old K3 dashboards, but after fighting thru the CORS
"features", I find they're all blank. There's no errors, just no data and I
desperately need them.
I also need my old Packetbeat dashboards.
From my googling I think the quickest way to get them back is to downgrade
ES from 1.4 to 1.3, or am I wrong ?
So, I need a way to export the data from the indices to a new cluster. My
systems are in a secure environment, I can't use anything that needs to
connect out to the interrnet during compile / install time, so the node.js
/ npm stuff is locked out for me.
I tried the knapsack plugin but it doesn't seem to work installed into an
ES 1.4 cluster.
I'm a bit confused. Are you downgrading just because of Kibana compat
issues? seems to me like killing a fly with a bazooka.
Enabling CORS and using K3 dashboards seem like the better solution to me,
for now. K4 isn't even officially released yet. As for data disappearing,
I'm sure it wasn't and a relaxed debugging session can help you find that.
I will be more than happy to hear about what went wrong for you with
upgrading?
Well Kibana 4 is unusable for us, the lack of auto refresh killed it for
us.
Most of the time K4 simply doesn't work even for browsing small sets, I'd
say 2 times in 3 we get the 300000 ms timeout error, is there a solution to
this yet ?
And when we finally do get any results it's as slow as a pig on crutches.
I need to go back to my old K3 dashboards, but after fighting thru the
CORS "features", I find they're all blank. There's no errors, just no data
and I desperately need them.
I also need my old Packetbeat dashboards.
From my googling I think the quickest way to get them back is to downgrade
ES from 1.4 to 1.3, or am I wrong ?
So, I need a way to export the data from the indices to a new cluster. My
systems are in a secure environment, I can't use anything that needs to
connect out to the interrnet during compile / install time, so the node.js
/ npm stuff is locked out for me.
I tried the knapsack plugin but it doesn't seem to work installed into an
ES 1.4 cluster.
Well you say "just", but at the moment Kibana is our only view into the ES
cluster, so yes it's a dealbreaker for us.
After enabling CORS, and what an unexpected knock about of pure fun that
was, I still can't use the K3 dashboards, they're blank, no data, no errors
just empty dashboards
Data isn't disappearing, I can still see it via the "head" plugin
So what's the quickest way of being able to see my data via the K3 boards ?
Is it exporting out into a new cluster ? Or is there a way to make them
work with the ES 1.4 cluster ?
JJ
.On Wednesday, 3 December 2014 14:17:39 UTC-8, Itamar Syn-Hershko wrote:
I'm a bit confused. Are you downgrading just because of Kibana compat
issues? seems to me like killing a fly with a bazooka.
Enabling CORS and using K3 dashboards seem like the better solution to me,
for now. K4 isn't even officially released yet. As for data disappearing,
I'm sure it wasn't and a relaxed debugging session can help you find that.
On Thu, Dec 4, 2014 at 12:12 AM, Jack Judge <jackj...@gmail.com
<javascript:>> wrote:
I will be more than happy to hear about what went wrong for you with
upgrading?
Well Kibana 4 is unusable for us, the lack of auto refresh killed it for
us.
Most of the time K4 simply doesn't work even for browsing small sets, I'd
say 2 times in 3 we get the 300000 ms timeout error, is there a solution to
this yet ?
And when we finally do get any results it's as slow as a pig on crutches.
I need to go back to my old K3 dashboards, but after fighting thru the
CORS "features", I find they're all blank. There's no errors, just no data
and I desperately need them.
I also need my old Packetbeat dashboards.
From my googling I think the quickest way to get them back is to
downgrade ES from 1.4 to 1.3, or am I wrong ?
So, I need a way to export the data from the indices to a new cluster. My
systems are in a secure environment, I can't use anything that needs to
connect out to the interrnet during compile / install time, so the node.js
/ npm stuff is locked out for me.
I tried the knapsack plugin but it doesn't seem to work installed into an
ES 1.4 cluster.
I'm not aware of compat issues with K3 and ES 1.4 other than Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub . I'd check for
javascript errors, and try to see what's going on under the hood, really.
When you have more data about this, you can either quickly resolve, or open
a concrete bug
Well you say "just", but at the moment Kibana is our only view into the ES
cluster, so yes it's a dealbreaker for us.
After enabling CORS, and what an unexpected knock about of pure fun that
was, I still can't use the K3 dashboards, they're blank, no data, no errors
just empty dashboards
Data isn't disappearing, I can still see it via the "head" plugin
So what's the quickest way of being able to see my data via the K3 boards
? Is it exporting out into a new cluster ? Or is there a way to make them
work with the ES 1.4 cluster ?
JJ
.On Wednesday, 3 December 2014 14:17:39 UTC-8, Itamar Syn-Hershko wrote:
I'm a bit confused. Are you downgrading just because of Kibana compat
issues? seems to me like killing a fly with a bazooka.
Enabling CORS and using K3 dashboards seem like the better solution to
me, for now. K4 isn't even officially released yet. As for data
disappearing, I'm sure it wasn't and a relaxed debugging session can help
you find that.
I will be more than happy to hear about what went wrong for you with
upgrading?
Well Kibana 4 is unusable for us, the lack of auto refresh killed it for
us.
Most of the time K4 simply doesn't work even for browsing small sets,
I'd say 2 times in 3 we get the 300000 ms timeout error, is there a
solution to this yet ?
And when we finally do get any results it's as slow as a pig on crutches.
I need to go back to my old K3 dashboards, but after fighting thru the
CORS "features", I find they're all blank. There's no errors, just no data
and I desperately need them.
I also need my old Packetbeat dashboards.
From my googling I think the quickest way to get them back is to
downgrade ES from 1.4 to 1.3, or am I wrong ?
So, I need a way to export the data from the indices to a new cluster.
My systems are in a secure environment, I can't use anything that needs to
connect out to the interrnet during compile / install time, so the node.js
/ npm stuff is locked out for me.
I tried the knapsack plugin but it doesn't seem to work installed into
an ES 1.4 cluster.
Which google leads me to believe should open it up for anything. K3 is
fronted by apache and a bit more googling prompted me to add this to the
section of httpd.conf
Header set Access-Control-Allow-Origin "*"
Still getting the same errors
I'm at a loss to know what else to do now.
On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote:
I'm not aware of compat issues with K3 and ES 1.4 other than Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub . I'd check for
javascript errors, and try to see what's going on under the hood, really.
When you have more data about this, you can either quickly resolve, or open
a concrete bug
Classic CORS error - maybe * is blocked by ES. Haven't had to deal with
this myself (yet) so can't help you here. All in all just a small rough
edge to smooth, not a clusterfuck.
A quick solution would be to install K3 as a site plugin and use it
internally (don't expose it to the web)
Which google leads me to believe should open it up for anything. K3 is
fronted by apache and a bit more googling prompted me to add this to the
section of httpd.conf
Header set Access-Control-Allow-Origin "*"
Still getting the same errors
I'm at a loss to know what else to do now.
On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote:
I'm not aware of compat issues with K3 and ES 1.4 other than Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub . I'd check for
javascript errors, and try to see what's going on under the hood, really.
When you have more data about this, you can either quickly resolve, or open
a concrete bug
This was a clusterfuck and still is. The K3 dashboards are used by our
devs, network guys and management for a variety of tasks. When they stopped
working we lost sight of large parts of our operation.
Because of the lack of documentation and the time pressure, I don't have
the luxury of sitting down, picking up a coffee and learning all about
CORS, so yeah we've downgraded back to 1.3
Unless you know how to fix it, which I don't, then this is a clusterfuck,
it rendered our system useless to us.
On Thursday, 4 December 2014 07:40:47 UTC-8, Itamar Syn-Hershko wrote:
Classic CORS error - maybe * is blocked by ES. Haven't had to deal with
this myself (yet) so can't help you here. All in all just a small rough
edge to smooth, not a clusterfuck.
A quick solution would be to install K3 as a site plugin and use it
internally (don't expose it to the web)
Which google leads me to believe should open it up for anything. K3 is
fronted by apache and a bit more googling prompted me to add this to the
section of httpd.conf
Header set Access-Control-Allow-Origin "*"
Still getting the same errors
I'm at a loss to know what else to do now.
On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote:
I'm not aware of compat issues with K3 and ES 1.4 other than Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub . I'd check for
javascript errors, and try to see what's going on under the hood, really.
When you have more data about this, you can either quickly resolve, or open
a concrete bug
This was a clusterfuck and still is. The K3 dashboards are used by our
devs, network guys and management for a variety of tasks. When they stopped
working we lost sight of large parts of our operation.
Because of the lack of documentation and the time pressure, I don't have
the luxury of sitting down, picking up a coffee and learning all about
CORS, so yeah we've downgraded back to 1.3
Unless you know how to fix it, which I don't, then this is a clusterfuck,
it rendered our system useless to us.
On Thursday, 4 December 2014 07:40:47 UTC-8, Itamar Syn-Hershko wrote:
Classic CORS error - maybe * is blocked by ES. Haven't had to deal with
this myself (yet) so can't help you here. All in all just a small rough
edge to smooth, not a clusterfuck.
A quick solution would be to install K3 as a site plugin and use it
internally (don't expose it to the web)
Well you're right there's JS errors, CORS related;
XMLHttpRequest cannot load http://10.5.41.120:9200/
logstash-2014.12.04/_search. Request header field Content-Type is not
allowed by Access-Control-Allow-Headers.
In my elasticsearch.yml I've got this on all nodes,
Which google leads me to believe should open it up for anything. K3 is
fronted by apache and a bit more googling prompted me to add this to the
section of httpd.conf
Header set Access-Control-Allow-Origin "*"
Still getting the same errors
I'm at a loss to know what else to do now.
On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote:
I'm not aware of compat issues with K3 and ES 1.4 other than Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub . I'd check for
javascript errors, and try to see what's going on under the hood, really.
When you have more data about this, you can either quickly resolve, or open
a concrete bug
I know, I'm kicking myself for this. TBH my thinking was along the lines of
"new dashboards! - new kibana but that's okay it's works on it's own
server, K3 dashboards will still work - oh, ES update required, well new
kibana index needed so that explains that - oh fuck...what the hell is CORS
? can i back out ? why the fuck wasn't this highlighted in the release
notes, i mean in big glowing letters as in THIS WILL BREAK YOUR EXISTING
SETUP
Those were my thoughts, more or less.
On Thursday, 4 December 2014 16:24:09 UTC-8, Mark Walkom wrote:
This is why it's good to test before rolling out to critical platforms.
On 5 December 2014 at 09:29, Jack Judge <jackj...@gmail.com <javascript:>>
wrote:
Wrong in every fundamental aspect.
This was a clusterfuck and still is. The K3 dashboards are used by our
devs, network guys and management for a variety of tasks. When they stopped
working we lost sight of large parts of our operation.
Because of the lack of documentation and the time pressure, I don't have
the luxury of sitting down, picking up a coffee and learning all about
CORS, so yeah we've downgraded back to 1.3
Unless you know how to fix it, which I don't, then this is a clusterfuck,
it rendered our system useless to us.
On Thursday, 4 December 2014 07:40:47 UTC-8, Itamar Syn-Hershko wrote:
Classic CORS error - maybe * is blocked by ES. Haven't had to deal with
this myself (yet) so can't help you here. All in all just a small rough
edge to smooth, not a clusterfuck.
A quick solution would be to install K3 as a site plugin and use it
internally (don't expose it to the web)
Well you're right there's JS errors, CORS related;
XMLHttpRequest cannot load http://10.5.41.120:9200/
logstash-2014.12.04/_search. Request header field Content-Type is not
allowed by Access-Control-Allow-Headers.
In my elasticsearch.yml I've got this on all nodes,
Which google leads me to believe should open it up for anything. K3 is
fronted by apache and a bit more googling prompted me to add this to the
section of httpd.conf
Header set Access-Control-Allow-Origin "*"
Still getting the same errors
I'm at a loss to know what else to do now.
On Wednesday, 3 December 2014 15:48:28 UTC-8, Itamar Syn-Hershko wrote:
I'm not aware of compat issues with K3 and ES 1.4 other than Kibana 3 & Elasticsearch 1.4.0 beta 1 · Issue #1637 · elastic/kibana · GitHub . I'd check for
javascript errors, and try to see what's going on under the hood, really.
When you have more data about this, you can either quickly resolve, or open
a concrete bug
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
