InfoboxCloud cloud platform update: Jelastic 1.9.3
The InfoboxCloud Jelastic Cloud Platform will be updated to version 1.9.3 very soon. The Jelastic platform in InfoboxCloud allows, in one click, to receive Java, PHP and Ruby environments, necessary SQL and NoSQL databases, cache, VDS and more.
In this case, the user does not fall into absolute dependence on the platform provider. You can configure all the same applications on other servers, just in Jelastic this process is automated and you do not spend time setting up and maintaining the infrastructure, getting the necessary components for your software and services to work - save money.
In addition, the actual autoscaling allows you to use as many resources as the application needs at a particular point in time and not pay for the potential maximum of the required resources.
')
In this article we will consider what we are preparing for the update of the cloud platform InfoboxCloud Jelastic .
Garbage Collection (GC) is a type of automatic memory management. The garbage collector tries to clear the memory occupied by objects that will no longer be used by the executable program. As a result, the cost is reduced due to the release of unused resources.
On the Jelastic platform, a special garbage collection agent (Garbage Collector agent) is used along with standard Java Virtual Machine garbage collectors.
Jelastic GC agent is enabled by default for all newly created Java application servers.
It works with only two types of GC:
-XX: + UseParNewGC (if -Xmx <8000m)
-XX: + UseG1GC (if -Xmx> = 8000m)
These settings can be changed, but if you manually select another garbage collector, full GC will not be available.
By default, the garbage collection process will be performed every 15 minutes (starting at the start of the JVM) to free up unused memory. The launch period can be changed depending on your requirements. You can also switch to debug mode.
-javaagent: /var/lib/jelastic/java/jelastic-gc-agent.jar=debug=true,period=900
This solution is unique and originally developed by Jelastic engineers to improve the memory management of your application and as a result to reduce memory consumption.
Zend OPcache is now enabled by default and as a result, performance rises to 40%. Zend OPcache speeds up PHP execution by caching opcode and optimizations.
Apache and Nginx (php 5.3, 5.4, 5.5) include the OPcache extension, enabled via etc> php.ini:
zend_extension = / usr / lib64 / php / modules / opcache.so
Cache size and other OPcache settings can be configured via php.ini by changing the following parameters:
More detailed information
The number of PHP workers who process PHP requests is automatically increased on the Apache server, depending on the allocated number of cloudlets.
To test this feature, click Config on your Apache web server and go to conf> httpd.conf .
Find and remember the value of Max clients. After that, change the topology of your environment by increasing or decreasing the limit of the cloudlet on your server.
Return to conf> httpd.conf . You will see that the Max Clients value has been increased / decreased.
Note that this feature will be disabled if you remove the following line from the httpd.conf file:
# Jelastic autoconfiguration mark
mod_security is an Apache module that provides the ability to easily filter, check URL and Unicode, audit, prevent null byte attack ; limits the size of the loaded data, masks the details of the functioning of the server, etc.
This module is available in Jelastic by default and can be configured via conf.d> mod_security.conf .
In this file you can edit the default configuration or add your own settings.
For example, you can add additional ModSecurity rules. To do this, you just need to upload your rules to the modsecurity.d folder. They will be automatically activated via the Include modsecurity.d / *. Conf line in the conf.d> mod_security.conf .
Starting with this release, you have access to MyAdmin-jel.conf (for MariaDB and MySQL), phpPgAdmin (for PostgreSQL) and couchdb.conf (for CouchDB). These files are located in the conf.d folder.
These files can be edited to set the appropriate criteria for allowing / denying access by ip address or domain for an application working with a database at the Apache web server level.
When there is not enough RAM in your environment, processes with a high level of memory consumption are shot by the OOM killer to free up resources. The order for shutting down processes is specified in the OOM settings.
Now oom_score_adj is used to shoot the least important processes (httpd) and only last of all are the database processes (mysql).
Making backups is very important at any stage of the development process, ensuring the security and integrity of your data. Jelastic allows you to plan database backups and you can always restore the latest copy of your information in case of data loss. To do this, we provide a special script for database backup, which can be customized according to your requirements.
In this release, we improved the MongoDB database backup script. Now you can use it to backup multiple databases. Just specify the necessary settings as described in the instructions for backing up MongoDB databases .
4. Changes in the default database configuration
In this release, the following default database settings have been changed in php.ini:
upload_max_size = 1024MB
post_max_size = 1024MB
max_execution_time = 600
max_input_time = 600
This is a consequence of the ability to download large dumps. These changes are made for all new and previously created containers, except for containers that you manually configured.
When you perform any actions in the Jelastic control panel (for example, creating environments, deploying applications, building a project, restarting an application, etc.), you could encounter the problem of HTTP Transport Error occurring due to some problems with the Internet connection. As a result of breaking the connection, your actions completely stopped and you had to start all over again.
Now this situation is radically improved. When the connection is broken, it just goes to sleep the process that you initiated earlier and continues when the connection is restored. After that, the last request will be resumed and the process is completed without the need for additional configuration of anything.
Updated display of the history of billing - it became clearer.
Now, when saving configuration files in Jelastic, the option “Do not show the save confirmation dialog again” appeared. If you check this box, the configuration files will be saved automatically. Settings apply to all types of configuration files for all environments.
Tomcat 6 6.0.37
Tomcat 7 7.0.47
TomEE 1.5.2
Jetty 6 6.1.26
GlassFish 3 3.1.2.2
Java 6 1.6.0_45
Java 7 1.7.0_45
MariaDB 5.5.34 / 10.0.6
MongoDB 2.4.8
MySQL 5.5.34
PostgreSQL 8 8.4.18
PostgreSQL 9 9.3.1
CouchDB 1.5.0
nginx 1.4.3
Maven 3.0.5
Centos 6 6.4
Memcached 1.4.15
Apache 2.2.15-29
NGINX PHP 1.4.3
PHP 5.3 5.3.27
PHP 5.4 5.4.21
PHP 5.5 5.5.5
Successful use of the cloud platform InfoboxCloud .
In this case, the user does not fall into absolute dependence on the platform provider. You can configure all the same applications on other servers, just in Jelastic this process is automated and you do not spend time setting up and maintaining the infrastructure, getting the necessary components for your software and services to work - save money.
In addition, the actual autoscaling allows you to use as many resources as the application needs at a particular point in time and not pay for the potential maximum of the required resources.
')
In this article we will consider what we are preparing for the update of the cloud platform InfoboxCloud Jelastic .
Improvements in scalability and performance
Java
Jelastic GC Agent
Garbage Collection (GC) is a type of automatic memory management. The garbage collector tries to clear the memory occupied by objects that will no longer be used by the executable program. As a result, the cost is reduced due to the release of unused resources.
On the Jelastic platform, a special garbage collection agent (Garbage Collector agent) is used along with standard Java Virtual Machine garbage collectors.
Jelastic GC agent is enabled by default for all newly created Java application servers.
It works with only two types of GC:
-XX: + UseParNewGC (if -Xmx <8000m)
-XX: + UseG1GC (if -Xmx> = 8000m)
These settings can be changed, but if you manually select another garbage collector, full GC will not be available.
By default, the garbage collection process will be performed every 15 minutes (starting at the start of the JVM) to free up unused memory. The launch period can be changed depending on your requirements. You can also switch to debug mode.
-javaagent: /var/lib/jelastic/java/jelastic-gc-agent.jar=debug=true,period=900
This solution is unique and originally developed by Jelastic engineers to improve the memory management of your application and as a result to reduce memory consumption.
Php
1. Zend OPcache
Zend OPcache is now enabled by default and as a result, performance rises to 40%. Zend OPcache speeds up PHP execution by caching opcode and optimizations.
Apache and Nginx (php 5.3, 5.4, 5.5) include the OPcache extension, enabled via etc> php.ini:
zend_extension = / usr / lib64 / php / modules / opcache.so
Cache size and other OPcache settings can be configured via php.ini by changing the following parameters:
- opcache.enable = 1
enable / disable OPcache extension
- opcache.memory_consumption = 64
setting the size of the used RAM
- opcache.interned_strings_buffer = 8
The size of the RAM used to store internal strings (for example, classnames)
- opcache.max_accelerated_files = 4000
maximum number of cached files
- opcache.revalidate_freq = 60
file check frequency by change time
- opcache.fast_shutdown = 1
Enabling / disabling the fast completion of the accelerated code sequence The quick completion of the sequence does not release each allocated block, but allows Zend Engine Memory Management to do its work.
- opcache.enable_cli = 1
enable / disable OPcache for CLI version of PHP
More detailed information
2. Automatic change of the number of workers
The number of PHP workers who process PHP requests is automatically increased on the Apache server, depending on the allocated number of cloudlets.
To test this feature, click Config on your Apache web server and go to conf> httpd.conf .
Find and remember the value of Max clients. After that, change the topology of your environment by increasing or decreasing the limit of the cloudlet on your server.
Return to conf> httpd.conf . You will see that the Max Clients value has been increased / decreased.
Note that this feature will be disabled if you remove the following line from the httpd.conf file:
# Jelastic autoconfiguration mark
3. Manual mod_security settings
mod_security is an Apache module that provides the ability to easily filter, check URL and Unicode, audit, prevent null byte attack ; limits the size of the loaded data, masks the details of the functioning of the server, etc.
This module is available in Jelastic by default and can be configured via conf.d> mod_security.conf .
In this file you can edit the default configuration or add your own settings.
For example, you can add additional ModSecurity rules. To do this, you just need to upload your rules to the modsecurity.d folder. They will be automatically activated via the Include modsecurity.d / *. Conf line in the conf.d> mod_security.conf .
Database Improvements
1. Editable MyAdmin-jel.conf, phpPgAdmin and couchdb.conf files
Starting with this release, you have access to MyAdmin-jel.conf (for MariaDB and MySQL), phpPgAdmin (for PostgreSQL) and couchdb.conf (for CouchDB). These files are located in the conf.d folder.
These files can be edited to set the appropriate criteria for allowing / denying access by ip address or domain for an application working with a database at the Apache web server level.
2. Shooting processes to free up memory
When there is not enough RAM in your environment, processes with a high level of memory consumption are shot by the OOM killer to free up resources. The order for shutting down processes is specified in the OOM settings.
Now oom_score_adj is used to shoot the least important processes (httpd) and only last of all are the database processes (mysql).
3. Backup several MongoDB databases
Making backups is very important at any stage of the development process, ensuring the security and integrity of your data. Jelastic allows you to plan database backups and you can always restore the latest copy of your information in case of data loss. To do this, we provide a special script for database backup, which can be customized according to your requirements.
In this release, we improved the MongoDB database backup script. Now you can use it to backup multiple databases. Just specify the necessary settings as described in the instructions for backing up MongoDB databases .
4. Changes in the default database configuration
In this release, the following default database settings have been changed in php.ini:
upload_max_size = 1024MB
post_max_size = 1024MB
max_execution_time = 600
max_input_time = 600
This is a consequence of the ability to download large dumps. These changes are made for all new and previously created containers, except for containers that you manually configured.
HTTP Transport Error
When you perform any actions in the Jelastic control panel (for example, creating environments, deploying applications, building a project, restarting an application, etc.), you could encounter the problem of HTTP Transport Error occurring due to some problems with the Internet connection. As a result of breaking the connection, your actions completely stopped and you had to start all over again.
Now this situation is radically improved. When the connection is broken, it just goes to sleep the process that you initiated earlier and continues when the connection is restored. After that, the last request will be resumed and the process is completed without the need for additional configuration of anything.
Other improvements
Updated display of the history of billing - it became clearer.
Now, when saving configuration files in Jelastic, the option “Do not show the save confirmation dialog again” appeared. If you check this box, the configuration files will be saved automatically. Settings apply to all types of configuration files for all environments.
Software stack versions in Jelastic 1.9.3
Tomcat 6 6.0.37
Tomcat 7 7.0.47
TomEE 1.5.2
Jetty 6 6.1.26
GlassFish 3 3.1.2.2
Java 6 1.6.0_45
Java 7 1.7.0_45
MariaDB 5.5.34 / 10.0.6
MongoDB 2.4.8
MySQL 5.5.34
PostgreSQL 8 8.4.18
PostgreSQL 9 9.3.1
CouchDB 1.5.0
nginx 1.4.3
Maven 3.0.5
Centos 6 6.4
Memcached 1.4.15
Apache 2.2.15-29
NGINX PHP 1.4.3
PHP 5.3 5.3.27
PHP 5.4 5.4.21
PHP 5.5 5.5.5
Successful use of the cloud platform InfoboxCloud .
Source: https://habr.com/ru/post/215245/
All Articles