magento 1.9 catalog search index cannot initialize the indexer process on localhost - magento-1.9

Can Magento 1.9 catalog search index invoke the indexer process on local host?

saving a product will invoke an update, if catalog search index is set to update on save

Related

Jhipster Entity and User data gone after MySQL runs out of memory

I have an issue with Jhipster crashing and losing all entity entries. I'm using a Jhipster in production with a mysql database server on Docker. Every day or so the mysql database crashes and I have to restart the Jhispter application. When it restarts all of the mysql data is gone and doesn't come back on the reload. This includes both entities and user login information. I think I need to load in the entity data again somehow, but I'm not sure how.
How would I go about reloading the Jhipster user and entity data once the server crashes?
I have both MySQL and JHispter running with docker-compose.

what does rake db:schema:cache:dump exactly do? is it safe to be ran in production?

Rails has an issue with big schemas where it becomes slower over time as the app grows, to fix this issue the schema_cache file was introduced and is enabled by default, it get updated with every migration.
We can create and update the file manually using rake db:schema:cache:dump.
Finally my questions:
What query does it actually run inside the db?
Does it lock the db while performing the query?
Finally is it safe to be ran in production?
Thank you
After logging my DB and running the command, it turns out it just runs
show full fields table_name
against all the tables in the schema.
The command can be executed in production and it creates a db/schema_cache.yml. Mainly it serializes data related to schema into this file. Generally in a prod environment with multiple servers, this file would be shared across to avoid db calls for
show full fields
This query is run by rails framework on boot of servers and with this file the requests would decline and the yml file would serve this.

Enable query service for couchbase

Sorry for very beginner question, just installed couchbase for the first time and when I want to load the "beer-sample" to try to run some n1ql scripts I get the following:
This cluster does not contain an index or query node. Sample data will be installed without creating indexes.
and when I click Query in the couchbase console:
No query nodes were found on this cluster.
How can I enable these two?
just installed couchbase for the first time
During installation, it should have prompted you to install certain services per node of the cluster.
It might be possible to add services afterwards of cluster setup, but since you have a fresh cluster anyway, I'd suggest just restarting from the beginning
Relevant documentation: https://docs.couchbase.com/server/current/manage/manage-nodes/create-cluster.html

Multiple MySQL catalogs on EMR/PrestoDB

I'm able to create a catalog called mysql on my EMR by using the presto-connector-mysql configuration options on EMR.
However, I'd like to connect to multiple mysql datasources. Adding a 2nd datasource to /etc/presto/conf/catalog and then doing a restart presto-server isn't quite right, because while I can query the mysql datasource correctly and the 2nd catalog shows up, querying a table there gives:
Query 20170407_040307_00008_qjgse failed: No nodes available to run query
Is there a way to reset the whole cluster? Do I need to install the new catalog on all the nodes?
You need to install the new catalog in /etc/presto/conf/catalog on all of the nodes, and then restart Presto. Then it should work fine for you.

Why does Cucumber drop tables if schema.rb is not present?

I have a Rails 4 app that uses an external DB I don't control. So there is no schema or migration. Anyway, I create a model and use db setting the table_name in the model.
When I run cucumber it drops the db tables!?
Any idea why and how to avoid it?
$ bundle exec cucumber
Running via Spring preloader in process 18865
.../db/schema.rb doesn't exist yet. Run `rake
db:migrate` to create it, then try again. If you do not intend to use a
database, you should instead alter
.../config/application.rb to limit the frameworks that
will be loaded.
After that the db is empty, no tables.
You should still be able to dump your schema locally if ActiveRecord is connecting to the db.
rake db:schema:dump