Task concurrency parameter in Presto configuration of EMR - configuration

In what EMR directory is located the Presto task.concurrency parameter?

Thanks for the help, I found that is located in etc/presto/conf/config.properties

Related

mySQL: Connection with Eclipse

I have a lots of problem with the connection between eclipse EE and mySQL. I need to create a web application so I need a DB. I downloaded mySQL ( and mySQL workbench ).
I go to connect eclipse to DB but I can't do it.
This is the sequence that I do:
Please give me some information, I need to solve this . Thanks you guys.
So setting up a JDBC connection in Eclipse can be much easier than your approach. You can instead, try this:
Right click on your Java class in the Package Explorer in the Eclipse workspace.
Go down the list that appears until you find Build Path and click Add External Archives.
Find the jar file called mysql-connector-java-version number.jar and open it. This should connect your JDBC to Eclipse!
Hope this helps!

Ejabberd MySQL bean files are not found

I am trying to install Ejabberd with mysql and followed this blog.
https://www.ejabberd.im/Using%20ejabberd%20with%20MySQL%20native%20driver
but I can't find any bean files for MySQL
https://www.ejabberd.im/doc/display/CONTRIBS/Yxa
mysql.beam
mysql_auth.beam
mysql_conn.beam
mysql_recv.beam
I have configured all the other things other than copying bean files.
The documentation you are referring to is obsolete. Use of MySQL with ejabberd is now fully integrated / packaged. If you build from source, you need to pass the proper --enable-mysql option. If using binary installer or packages from ProcessOne, the MySQL driver is already included.
What you need is to load schema into your database and configure "odbc" to use your MySQL database.

Mysql installation procedure in hadoop cluster

how to install & configure mysql in hadoop cluster (os centos) to access the created database in one node and accesing in other node.? can anyone post the step by step installation & confiuration procedure?
If you're looking for a distributed SQL type solution, i would suggest you look at Cloudera Impala, Apache Spark SQL, or the Amazon solution Redshift.
MySQL is not designed to be distributed horizontally but rather vertically.

Relationship between different hbase-site.xml for a Cloudera install

With a Cloudera install of HBase, I saw three places have config information :
/etc/hbase/conf/hbase-site.xml,
/usr/lib/hbase/conf/hbase-site.xml,
and /var/run/cloudera-scm-agent/process/*-hbase-MASTER
Which one exactly is in effect? Or maybe all of them do?
In all cases of hbase the /etc/hbase/conf/hbase-site.xml file is always read. The /usr/lib/hbase/conf/hbase-site.xml is a symlink to /etc/hbase/conf/hbase-site.xml so it is the same file.
Lastly, anything in /var/run/ is a runtime variable and in your case it is the Cloudera Manager Agent. The Manager Agents are responsible for the management console and logging amongst other tasks.
I hope that helps,
Pat
The config file used is /usr/lib/hbase/conf/hbase-site.xml.
Other files aren't symbolic links.
Since the same configuration information needs to be used for other processes like HMaster,RegionServer, /usr/lib/hbase/conf/hbase-site.xml file is synced at different locations while initializing/preprocessing of these daemons. Hence it is advised to make any configuration changes in /usr/lib/hbase/conf/hbase-site.xml file only.
Also you need to make the same changes to these file on all nodes in your cluster and restart the HBase daemons.
I hope these answer your question.
Per my search and learning, HBase actually has two types of hbase-site.xml files, one for HMaster/RegionServer, and the other for client.
In Cloudera's distribution, the hbase-site.xml file in folder /var/run/cloudera-scm-agent/process/*-hbase-MASTER is the config used by the running HMaster process. Similar is for RegionServer.
Yet the site.xml file under /usr/lib/hbase/conf/ and /etc/hbase/conf/, symlinked from one to the other (according to #apesa), is for client usage. If one starts HBase shell on an HMaster host or a RegionServer host, this client config file will be used so the shell application knows how to connect to the ZooKeeper quorum to obtain the running HBase service. If one wants to use the HBase service from a client host, then he needs to copy this client xml file to the client host.
For regular Apache installation of HBase, as was indicated in Sachin's answer, the same hbase-site.xml is used for both purposes, though the HMaster, the RegionServer, and the client processes will use only the options needed and ignore the rest.
From experimenting with the hbase binary version 1.2.0-cdh5.16.1, it appears to use the Java classpath to find the hbase-site.xml file to use, whether running as a server or a client shell. There is a configuration parameter (--config) you can pass to hbase to control the config directory used, which by default is ./conf (run hbase to view the documented help on this).
This observation is supported by other answers on this topic (e.g. Question 14327367).
Therefore, to answer your specific question, to determine which config file is used on your machine, run hbase classpath and find which of the 3 directories appears first in the classpath.

change innodb_log_file_size variable value for Amazon RDS MYSQL Linux server

we are using Amazon RDS linux server for MYSQL. what is the way to change my.cnf file variable values ??
i am trying to change innodb_log_file_size variable. Can you please update me which is the best way to change?
So please help me on this
Thank you in Advance
Create a new DB paramater group with your required values and attach to your RDS.
You cannot change that value in Aurora, the storage engine is different than rds mysql or standard mysql and optimized internally. No need to worry about changing it.
I'm facing similar issue where I need to change the value of global variable in my Amazon Aurora Serverless cluster.
As you can see in the above documentation screenshot the innodb_log_file_size is not a dynamic variable so it won't be available in the DB Parameter Group.
Values of these kind of non dynamic global variables can only be changed by modifying MySQL config files (my.cnf) or by modifying server startup command.
Since you are using Amazon RDS MySQL there users don't have access to config files so no you cannot modify the value of innodb_log_file_size global variable, This functionality is not available in Amazon RDS as of now.