I have Kibana plugin installed in each ES node. Kibana is behind nginx reverse proxy because it's served from /kibana/ route. Elastic is protected with SearchGuard plugin.
Question: History for dev tools/console is reset with each login (after each login, history is empty). Now, I'm not sure if I'm missing something or that's expected behaviour when SearchGuard is in use? I remember that worked well before installing SearchGuard. Not sure if it's coincidence or it's indeed related. It's saving properly during one session.
Elastic version: 6.1.3
Thank you!
It's stored in local storage under sense:editor_state in Chrome.
If it's wiped out daily or the cache is cleared, so will your searches be.
use ?load_from= in your url and save your queries in a json file... be aware of CORS if you use a web app of your own.
Related
I have an app in android, ios and windows which works in offline mode. That is, content is stored in the local database. Now I am trying to implement elasticsearch on this app. Is it possible to search the data from local database when I am offline. Or, is there a way to access Elasticsearch without HTTP.
Please help me on this.
Answer is no, Since elasticsearch will be installed outside of your phone.
But one of the options could be FTS3. Its not as powerful as ES but could be solution.
In Weblogic 10.3.5, is there any way to expire an html file from cache without going through a server restart. I am supporting a server with frequent HTML changes and hoping to find a way not to restart the server each time the HTML is updated. Environment is supporting a PeopleSoft domain. Thanks.
There's a way indeed, the parameter "Resource Reload Check (in seconds)" which can be found on a web app setup is what you're looking for. I've setup this to 5(secondes) in order to have a periodic refresh on dynamic ressources generated by an application engine (an xml parsed by an xslt)
For some details here's doc of 12.1.2 but I confirm it exists also on 10.3.4 (so on your version too) : https://docs.oracle.com/middleware/1212/wls/WLACH/pagehelp/J2EEwebappwebappconfigurationtitle.html
My problem is that I do not think I am able to refresh the magento redis cache from the admin page. I realize that the problem could come from many sources, but my gut tells me it has something to do with the backend being on a separate server. My magento installation is as follows:
Magento CE 1.8
Backend server and NFS(media) on an Amazon AWS EC2 at
http://admin.example.com
Database on AWS RDS MySQL 2 app servers
(scalable to more) on AWS Elastic Beanstalk at http://www.example.com
(route53)
regular backend cache(database 0), Lesti-FPC(database 0), and
redis_session (database 1) on AWS elasticache redis
I originally had my Lesti-FPC configured to use database 2 on the redis cache. I thought it worked pretty well as far as I could tell, until I realized that I couldn't flush the cache at all from the admin System>Cache Management page. "Flush Magento Cache," "Flush Cache Storage," "disable", and "refresh" did nothing. I could only flush it by rebooting the redis node or going in with redis-cli and using redis commands.
I then tried configuring Lesti-FPC to use database 0 as described above. It worked better. Now, I could flush the FPC with "Flush Cache Storage," although the other options still didn't work. At the time, I assumed it was an issue specifically with Lesti-FPC. But anyway, using "Flush Cache Storage" was good enough for me at the time, especially once I discovered that I could flush the cache through code using
Mage::app()->getCacheInstance()->flush();
I just recently found out that the problem may not be specific to Lesti-FPC. While trying to fix the Lesti issue, I tried monitoring redis. I know nothing about redis or caching, but when I would try to refresh the FPC, I would see commands like:
“del” “zc:ti:403_FPC”
“srem” “zc:tags” “403_FPC”
But those tags never existed. Doing:
keys *FPC*
in redis would give me
“zc:ti:109_FPC”
but nothing with 403. SO this means that my fpc caches do not get invalidated like they're supposed to after product/category changes and reindexing. I got around this by manually flushing the cache after changes and running cron jobs to flush and prime the fpc every few hours.
But it made me suspicious. I tried refreshing the other caches from the admin, and I found that magento would always try to delete and read the 403 keys(some of which existed and some of which did not) but never any 109 keys (of which there are many).
My guess is that the 403 keys are specific to the admin server, and the 109 keys are specific to the app servers. The admin server, maybe because it is on a different subdomain, is not touching the app servers' cached stuff. But the app servers are able to find its own keys fine, as demonstrated by the fact that the FPC is working very well.
Does this make sense? Is there something I could do to fix this? Did I configure something incorrectly or is this a magento bug?
It turns out that the Zend cache prefix is the first three characters of an md5 hash of the path to your etc folder.
My app server has its document root at /var/www/html. The full path of /var/www/html/app/etc gives an id of 403. The app servers running on elastic beanstalk have their document roots at /var/app/current which is done automatically at deployment.
It seems pretty dumb. Why not a hash of the database address and database name or something? That would make more sense.
Anyway, I hope this helps someone.
Can elasticsearch reload its config without dropping requests?
similar to how nginx supports the SIGHUP signal.
As far as I know you cannot "reload" the config like you want. But I suppose you need some changes in your configuration and most of them can be done via API (that don't require restarting the service). I would take a look at these links:
Admin indices update settings
Admin cluster update settings
I am completely new to web development and I want to set up a database search client on a website I am making because I do not want to write my own inefficient MySQL query strings. My plan is to use Elastic Search for this and my main question is:
Once my site is on a dedicated server somewhere, how do I install Elastic Search to the server, and/or what should I look for in a server so that I will be able to use Elastic Search?
You'll need a JRE, that's about it as far just getting started.
See http://www.elasticsearch.org/guide/reference/setup/installation.html for more details.
You'll probably want to run it as a service, If your using Windows you can download installers here. https://github.com/rgl/elasticsearch-setup/downloads
Hit me up if you need any help.