##
http.cors.allow-origin: /http?:\/\/localhost(:[0-9]+)?/
http.cors.enabled: true
On Monday, December 8, 2014 11:44:16 AM UTC-8, Tony Su wrote:
Trying to enter the correct setting in elasticsearch.yml.
Although the first block below added to elasticsearch.yml
Trying to enter the correct setting in elasticsearch.yml.
Although the first block below added to elasticsearch.yml does what it
wants, it disables CORS security altogether.
Am trying to enable only localhost. The ES documentation is not clear how
to define enabled domain(s) only
As follows,
Thx.
Will give those settings a go.
Tony
On Tuesday, November 18, 2014 3:08:51 PM UTC-8, Mark Walkom wrote:
Regarding the CORS errors, see
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-http.html#_settings_2
On 19 November 2014 09:45, Tony Su tony
Attempting to work my way through the article at
http://www.elasticsearch.org/blog/data-visualization-elasticsearch-aggregations/
Although the blog article was written for ES 1.0, I am attempting to run on
current stable ES 1.4.
Skimming the commands, I don't see anything I think should be an
You need to describe any network troubleshooting steps you've tried (like
telnet or curl commands) that verify network connectivity to open ports
with an active service responding.
It might also be helpful to understand how you're doing your network
configuration, particularly is you're using
Running in a VMware VM
ES 1.3 from the official repo
On an openSUSE box using the CentOS RPM as follows
zypper ar http://packages.elasticsearch.org/elasticsearch/1.3/centos
Elasticsearch_1.3_repository
openJDK 1.7
*# systemctl status*
elasticsearch.service - Starts and stops a single
Resolved the problem.
Although openJDK1.7 was installed, for some reason the system was
configured with openJDK 1.5.
Installed Oracle SE JDK 1.7 and no problems.
Tony
On Friday, August 1, 2014 8:40:02 AM UTC-7, Tony Su wrote:
Running in a VMware VM
ES 1.3 from the official repo
Prahy,
Although I don't know the solution,
It does look like using a RegEx in your query is causing an overflow of a byte
length limit.
Accordingly, I suspect if you can find the setting for that, it should solve
your problem.
Tony
--
You received this message because you are subscribed to
If it's not obvious, Mark's comment is exactly what you need to do,
Replace in the logstash output
elasticsearch
with
elasticsearch_http
This and other things you may want to know if you're running the logstash
tutorials are included in a wiki I posted
, February 25, 2014 10:21:29 AM UTC-5, Tony Su wrote:
One other issue.
I have never been able to deploy an elasticsearch.yml which names the
cluster node the same as the machine hostname despite the suggestions in
another thread. It just won't work, and based on another thread I strongly
the same way that it all starts on a production server.
Brian
On Tuesday, February 25, 2014 10:21:29 AM UTC-5, Tony Su wrote:
One other issue.
I have never been able to deploy an elasticsearch.yml which names the
cluster node the same as the machine hostname despite the suggestions
, our elasticsearch.yml file and other server configs
are maintained by Puppet and because we don't touch the installed config we
never have any problems with overwriting on a reinstallation.
Brian
On Monday, February 17, 2014 5:14:46 PM UTC-5, Tony Su wrote:
What?!
Removing and re
One other issue.
I have never been able to deploy an elasticsearch.yml which names the
cluster node the same as the machine hostname despite the suggestions in
another thread. It just won't work, and based on another thread I strongly
suspect the underlying Java code implements single quotes
Update:
After shutting down the cluster and restarting, the problem resolved
itself. Both shards which refused to initialize earlier were able to
initialize on restart.
Maybe the lesson to be learned is that assuming that when the snapshot were
made, integrity was verified(I hope so!)
for
them,
but I think the backup restore way would be more suitable for my case.
Thank you very much,
Attila
On 02/19/2014 04:50 PM, Tony Su wrote: Hi,
My testing has done a little bit of what you're describing...
- FWIW and I don't know why, when I re-insert the data from
I also fwas totally confused with the logstash demos after doing them with
mixed results.
The thing to understand is that each tutorial stands on its own and doesn't
really build on another.
Also, the harder you look at the detail of each tutorial there is a lot of
useful information packed in
Am testing on a lab cluster
5 nodes.
Repository name = Snapshots
Immediately after creating the snapshots, listing the snapshots returned
the snapshots and the indices they contained.
Now, am attempting to restore the snapshots to an empty cluster.
The new cluster looks good from the
by a new install.
Tony
On Wednesday, February 19, 2014 12:06:19 AM UTC-8, Norberto Meijome wrote:
Agreed is bad form to force reinstall.but surely you would have your
yml in a code/cfg repository?
On 18/02/2014 9:14 AM, Tony Su tony...@gmail.com javascript: wrote:
What?!
Removing and re
Cool.
Still not knowing whether the act of registering a snapshot repository
pointing to a populated directory might initialize/wipe the location, I
made a copy before registering again.
After registering the repository, I queried for existing snapshots and all
looks well, so it looks like
if there is a better solution to fixing a single index
that refuses to initialize.
TIA,
Tony
On Friday, February 21, 2014 4:56:13 PM UTC-8, Tony Su wrote:
Cool.
Still not knowing whether the act of registering a snapshot repository
pointing to a populated directory might initialize/wipe
Hi Terry,
Just a comment on your linefeeds and tabs problem...
My guess is that you're working on Windows. Plenty of text editors on
Windows insert invisible characters that can screw things up.
But, I've found that the opposite is true in the *NIX world, few text
editors do that sort of
To clearly differentiate the Kibana from what it may be monitoring,
Maybe deploy Kibana on a completely separate machine?
That way, anything related to deploying Kibana can be isolated and studied.
Local sensors (eg Marvel) and other processes not strictly part of Kibana
but may be invoked by
Hi, great idea.
But, you seem to need to add/modify the following...
- The default page only describes generic info about Azure apps, nothing
about your app.
- You need to describe minimal client machine requirements. I don't know if
anything more is required besides Visual Studio and Azure
HI Steven,
Although I'm not part of the ES team, because I have an old ES 0.90.10
node on CentOS 6.5 I wanted to upgrade to 1.0 anyway, I went ahead and more
or less replicated what you did...
The original ES 0.90.10 was installed from the downloaded RPM (because no
repos existed then).
Added
Hi,
My testing has done a little bit of what you're describing...
- FWIW and I don't know why, when I re-insert the data from scratch instead
of upgrading a cluster, I'm seeing substantial improvements in node general
health. They seem faster, less latencies related to indexing (I assume
I was wondering which backup/restore method you intended to use.
Snapshot/restore requires 1.0.
If you intend to upgrade your 0.9.x cluster to 1.0 first, it looks like
possibly a really good option (I intend to start testing snapshot/restore
sometime soon. I've already created snapshots and am
I've been curious about what I've been seeing and experimenting with...
- There seems to be no set rule whether to use double-quotes or single
quotes, they seem to work interchangeably for all commands using curl or
http. Or, more expectedly can be omitted altogether if the string contains
no
IMO based on what I've done and observed:
- Should not matter whether you use the IP address or FQDN in a URL as long
as the FQDN maps to the same IP address. So, Geovanie's problem with this
is likely a HOSTNAME mapping problem where the HOSTNAME is correct.
- I don't know that the SSH
I have found 3 ways of launching Kibana 3
1. If you're just setting up a Demo, you can launch an embedded version
without d/l and installing any files if you're using Logstash, just append
-- web to the end of the Logstash statement,
eg java -jar logstash -f configfile -- web
Then, just
Robert,
I think the (n/2)+1 formula should always work, and work reliably if
applied to
discovery.zen.minimum_master_nodes
It's absolutely impossible to establish a quorum and elect a new leader if
50% of total nodes. When and if quorum is established, the conditions to
elect a new leader in
On my testing (5 virtual nodes on a single box), I've been observing pretty
much the same.
I've tried pointing logstash to different nodes in the cluster and getting
approx. the same performance.
My main objective was to determine if by inserting the data into the
cluster on different nodes
Thx for the complete answer.
Tony
On Tuesday, February 18, 2014 11:44:22 AM UTC-8, InquiringMind wrote:
Tony,
(1) Your first question seems to be about the curl command. If so, then it
follows shell script rules. In most Unix shell scripts, double-quotes
preserve spaces and such,
Bytes and Mega?
Thx,
Tony
On Tuesday, February 18, 2014 1:26:06 PM UTC-8, Tony Su wrote:
Thx for the complete answer.
Tony
On Tuesday, February 18, 2014 11:44:22 AM UTC-8, InquiringMind wrote:
Tony,
(1) Your first question seems to be about the curl command. If so
The following has bearing on understanding what happens to the data store
when Replicas are increased or decreased.
Reading about re-sizing the cluster, I've read
- Changing the number of shards requires re-indexing, so it's highly
recommended to allocate a number of shards consistent with
Hi, I just read online an article which although doesn't describe your
scenario exactly, might be helpful
http://blog.qbox.io/launching-and-scaling-elasticsearch
My guess is that you're simply setting up two boxes with the following
configuration
index.number_of_shards: 1
At least for the RPM repo, it's still pushing RC2
After refreshing the repo data and doing an update, I expected the new
package (GA) to be pushed automatically for install.
From my system just now
Information for package elasticsearch:
--
Repository:
What?!
Removing and re-installing the ES package either removes the original or
over-writes the existing elasticsearch.yml
The is contrary to conventional packaging from what I've generally seen.
Typically, when a package is removed, the configuration fie is left alone
and must be removed
Looks like what I saw when I first upgraded my cluster to 1.0.
If you're using Logstash indexer.conf, you need to change the output from
elasticsearch to elasticsearch_http
The exact change is described in my wiki
http://en.opensuse.org/User:Tsu2/elasticsearch_1.0#The_Tutorials
HTH,
Tony
This is some of the test cluster's configuration(not necessarily relevant)
*Physical configuration:*
Nodes deployed virtually on a single machine
All nodes are Master and Data eligible, Master sometimes moves around and
data is distributed to all.
Node1 - Apps = 4GB RAM - 20GB storage -
Node2 -
Hello,
I've updated the info on my page which contains fairly old info (approx. ES
0.90.3)
*https://en.opensuse.org/User:Tsu2/Install_and_Intro_Logstash-Elasticsearch-Kibana*https://en.opensuse.org/User:Tsu2/Install_and_Intro_Logstash-Elasticsearch-Kibana
to
On Friday, February 14, 2014 4:06:06 AM UTC-8, Binh Ly wrote:
May I ask which OS you are running ES on?
IIRC Docker is a management tool for LXC.
So, it does pique the thoughts...
Where should marvel be pulling stats in an LXC deployment? It's not fully
isolated like other virtualization
I haven't thought of automating, but it seems to me that it should be easy
to address manually.
Haven't looked to see I this can be done in Marvel, but in
elasticsearch-head and elasticsearch-hq both display the indices.
Since data is indexed by data, you can select the indexes you wish and
is the project page
https://github.com/spring-projects/spring-data-elasticsearch
On Wednesday, 12 February 2014 23:02:33 UTC, Tony Su wrote:
Nosing around,
I think the Spring Project is listing you as an Incubator Community
Project (unless there is someone else doing something similar
After looking at Marvel since the day it was released,
I don't see Marvel as a replacement for Kibana 3, Marvel is a very attractive
implementation based on Kibana 3.
And, don't overlook that Marvel is free only for running 5 nodes. If you're
running more nodes, there is a cost (although very
IMO evaluating this issue starts with applying the CAP Theorem which in
summary states that networked clusters with multiple nodes can offer only 2
of the following 3 desirable objectives
Consistency
Availability
Partition tolerance (data distributed across nodes).
ES clearly does the
Hello,
Would like to ask if there is any update/change to using an Elasticsearch
logo since this Q was originally asked a year ago.
BTW - I notice that the current Elasticsearch website doesn't even display
a logo...
Tony
On Sunday, March 25, 2012 4:48:27 AM UTC-7, kimchy wrote:
Go
Josh,
Your experience about recovering in only about 10 minutes is very interesting.
Because my little 5-node cluster/15GB data/3500 indices is taking about an hour
to recover and i know the bottleneck is the disk subsystem I'm currently on,
Am curious
- What is the total size data in your
Update:
Whereas my previous tries to optimize for recovery failed miserably, the
gateway.recover_after_nodes setting in elasticsearch.yml worked... To a
point.
I noticed
- No ES node was responsive at all after nodes were brought online until the
quorum was met.
- It can take a long time for
Cool.
Thx all.
Tony
On Tuesday, February 11, 2014 10:38:18 AM UTC-8, Binh Ly wrote:
Tony,
What you are seeing with the shard recovery is normal - but doesn't mean
it couldn't use more improvement in the future. For now you can throttle
the recovery using a combination of settings (but
Dashboard is displayed, not the My Custom
Dashboard.
Maybe a permissions issue making it not possible to write changes?
Marvel was installed exactly as described as an ES plugin.
Tony
On Sunday, February 9, 2014 12:08:18 PM UTC-8, Tony Su wrote:
Thx for clarification
Although others might be able to comment,
IMO you need to provide more information, eg
Virtualization technology
What else is running in each node.
So, for comparison, this is my lab setup. I've been testing with approx.
1GB data that has created up to 15GB of additional metadata. I've been
, or there is likely a bug.(Or, I might
fundamentally misunderstand what disabling shard re-allocation is supposed
to do).
Maybe I'll re-test on a 0.90 cluster to see if it behaves differently...
Tony
On Friday, February 7, 2014 4:29:57 PM UTC-8, Tony Su wrote:
Hi Ivan,
Thx.
Yes, I
Hi Doru,
Based on what I've seen (but of course may be criticized by others)
I don't know if there is a sufficient reason to not use the REST API and
use something else instead.
What is your concern? Network traffic? AFAIK if localhost is bound to lo or
something similar, that isn't an issue.
Thx for clarification.
But, tried to save entire dashboard without a new name and settings were not
saved.
Will try to save with new name later today.
Tony
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and
Without changing a firewall setting on the IP address you're trying to
connect to? Or changing to a port that is already open?
IMO it has to be open, there is no alternative. Someone may opine
differently, but from what I've seen Kibana does not support a transport
other than IP (like pipes).
Although I'm running on a different VMware product, I've run other things
than ES on VMware before.
IMO is a good platform, no unusual issues.
Just the usual things...
If the VM was created on a different machine, then you may need to verify
no partition alignment issues.
In my current ES
],
attributes : {
max_local_storage_nodes : 1,
master : true
},
process : {
refresh_interval : 1000,
id : 9642,
max_file_descriptors : 4096,
mlockall : true
}
}
}
}
Le lundi 3 février 2014 22:31:12 UTC+1, Tony Su a écrit
, 2014 4:22:58 PM UTC-8, Tony Su wrote:
Hi Mark,
I've done all that to no effect.
FYI if it makes a diff,
I'm running on a distro that uses systemd, so in theory when the Service
is started, it's supposed to create a cgroup in which the new process is
run, and if there are any processes
First,
I'd like to say that how you've configured Marvel is a real education
looking at this new Kibana.
Q's about the Indices panel
- The current default configuration allows displaying 20 of 121 indices
Am I correct that the only way to display more indices is to simply modify
the height of
and should be reported.
On Monday, February 3, 2014 11:15:24 PM UTC+1, Tony Su wrote:
Thx for the input.
Nope, ES is being shutdown normally usually by simply stopping the
configured ES service, and only after it fully completes executing a
shutdown.
Tony
On Monday, February 3
:16:04 PM UTC+1, Tony Su wrote:
In this screenshot,
*https://github.com/putztzu/Misc_images/blob/master/marvel_only.png*https://github.com/putztzu/Misc_images/blob/master/marvel_only.png
The Free Disk Space is displayed in red.
Does this red color mean something, eg a warning of some kind
Just a reminder to whomever...
I'm noticing that the comments in elasticsearch.yml that reference or point
to URLs that worked in 1.0 may no longer work.
eg
Node Discovery (and viewing health)
http://localhost:9200/_cluster/nodes
I'm not sure but I think it should be changed to
Unless I'm missing something in the docs or these forums,
I've surprisingly found that if a node fails to join the cluster, it's not
sufficient to simply restart ES on the machine. I would have thought that
restarting ES thereby re-reading its config files should be sufficient to
announce its
Hi,
I understand you probably meant to post this to one of my other threads
https://groups.google.com/forum/#!topic/elasticsearch/dC48AAeL544
Interesting late development.
Too bad it sounds like what IBM is developing will be available only on IBM
servers, but it's understandable.
Unless
memory and IO bound and
not CPU.
Cheers,
Ivan
On Tue, Feb 4, 2014 at 9:17 AM, Tony Su tony...@gmail.com
javascript:wrote:
:)
I don't even know if there is a way to run a JRE on GPU computing (I
haven't looked, either).
My current exposure has generally given me the impression all
Hi Jack,
Although I'm a bit new to this, too...
1. You should take a look at your ES log files. Depending on how you
installed and are running ES, the log files could be in different places.
If I were to guess though, you should look in the following directory
/var/log/elasticsearch/
2. One
? It could be
the process isn't properly closing when requested.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com javascript:
web: www.campaignmonitor.com
On 5 February 2014 04:22, Tony Su tony...@gmail.com javascript: wrote:
Unless I'm missing
If data is re-loaded which is identical in every way to data which already
exists in ES,
Is new metadata created that simply over-writes existing (zero net effect)?
Or is duplicate, unique metadata created?
Or, maybe since identical data is found to already exist, although the
update API was
Hi,
Your post looks somewhat similar to something I posted a few days ago.
Am unclear why you may be stuck with 2 nodes running different versions of
ES.
They both need to be the same version to function as a cluster.
Your output says your upgraded node is ES 0.90.10 (not 0.90.9).
Surely you
Thx for the input.
Nope, ES is being shutdown normally usually by simply stopping the
configured ES service, and only after it fully completes executing a
shutdown.
Tony
On Monday, February 3, 2014 2:09:08 PM UTC-8, InquiringMind wrote:
Tony,
You're not doing a kill -9 during
A thought
Have you installed the Marvel plugin at least on the local machine?
By default the marvel website is configured to interrogate localhost.
Tony
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from this group and stop
+1, Tony Su wrote:
Deployed in a VMware environment.
Data is being consumed and is successful from source to ES
source logstash shipper(and parser) redis logstash es cluster
ES Cluster
All openSUSE 13.1
Machine 1 - 4GB ram - 16GB HDD - openSUSE/LXDE -ES -Logstash - netcat
Machine 2
Thx, I'll give that a try.
Since your fix merely specifies the http transport, does this mean that
elasticsearch intends to support protocols other than http?
Thx,
Tony
On Thursday, January 30, 2014 2:26:42 PM UTC-8, Tony Su wrote:
Not sure why. the indexer.conf from the 10min tutorial
Unfortunately, adding/specifying http in the Logstash Indexer.conf still
does not work communicating to ES 1.0 RC1.
Output follows, first the stdout error reported by Logstash followed by
indexer.conf contents
tony@Marvel-openSUSE:~/Working java -jar logstash-1.3.3-flatjar.jar agent
-f
Yup.
I can't believe I didn't read that right.
Is working now.
Thx,
Tony
On Friday, January 31, 2014 9:36:31 AM UTC-8, Binh Ly wrote:
Tony, can you please confirm, the output should be elasticsearch_http,
with underscore in between.
--
You received this message because you are
, Tony Su wrote:
Well, of course none of that is true...
Unless you include the mounted share which includes the raw data which
is being input into the system.
So, I guess that's where the anomaly exists...
I doubt that the source where the raw data is coming from should be
considered
Hello,
Have posted a screenshot of Marvel on my demo cluster
https://github.com/putztzu/Misc_images/blob/master/marvel_only.png
FYI Configuration
All nodes running on openSUSE 13.1/openjdk1.7
(On a single machine running VMware)
ES-Marvel-openSUSE
Deployed in a VMware environment.
Data is being consumed and is successful from source to ES
source logstash shipper(and parser) redis logstash es cluster
ES Cluster
All openSUSE 13.1
Machine 1 - 4GB ram - 16GB HDD - openSUSE/LXDE -ES -Logstash - netcat
Machine 2 - 1.5GB RAM -16GB HDD
Hello Jorg,
I was not aware of this page, but after skimming the page it is not what I
need in this situation.
The majority of the commands on this page are invoked as attributes of
systemctl which is the command line tool to inspect, modify and manage
systemd in a running system.
I'm not sure
defining your
environment variable in /etc/profile.local
Cheers,
On Monday, December 23, 2013 9:52:40 PM UTC, Tony Su wrote:
After considering this post,
I successfully created an environmental variable by adding to the bash
profile file (actually on the openSUSE I'm running, I created
After posting my last, I noticed that auto-correct modified systemd to
system
Should read
I noticed that a number of similar -Des commands are implemented in the
systemd Unit file referencing variables.
Tony
On Monday, December 23, 2013 2:19:46 PM UTC-8, Tony Su wrote:
Additional minor
Thx jorg, unfortunately your suggestions only configure actual strings, like my
original example I'm hoping to automatically retrieve and insert the hostname
of the machine. BTW if your suggestion is used in a config I've determined the
./bin/elasticsearch should be omitted.
Karol,
That looks
System:
Java openJDK 1.7
elasticsearch 0.90.7
Following some old instructions, I modified
/etc/sysconfig/elasticsearch
ES_JAVA_OPTS=-Des.node.name=$(name -n cut -d'.' -f1)
But, that crashes the elasticsearch service on start.
I've tried the entry both with and without the double-quotes.
83 matches
Mail list logo
