Translation

English
MySQL 5.6+ and MariaDB 10.0+ are great releases, and are very good versions to choose. Make sure you run the very latest release though which fixes a long standing low level networking issue that was causing spine many issues with reliability.
215/2430 · 243
English Spanish
Error while parsing the XML of RRDtool dump Error mientras se analizaba el XML volcado de rrdtool
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) removed from RRD file RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) eliminados de archivo RRD
RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) adding to RRD file RRA (CF=%s, ROWS=%d, PDP_PER_ROW=%d, XFF=%1.2f) agregando a archivo RRD
Website does not have write access to %s, may be unable to create/update RRDs El sitio web no tiene acceso de escritura a %s, puede ser incapaz de crear/actualizar RRDs
(Custom) (Personalizado)
Failed to open data file, poller may not have run yet Error al abrir el archivo de datos, es posible que el sondeo no se haya ejecutado todavía
RRA Folder Carpeta RRA
Root Raiz
Unknown RRDtool Error Error de rrdtool desconocido
Attempting to Create Graph from Non-Template Crear Aggregate desde plantilla
Attempting to Create Graph from Removed Graph Template Intentar crear un gráfico a partir de una plantilla de gráfico eliminada
Created: %s Creado(s): %s
ERROR: Whitelist Validation Failed. Check Data Input Method ERROR: falló la validación de la whitelist. Comprueba el método de entrada de datos
Graph Not created for %s due to bad data Gráfico no creado para %s debido a datos incorrectos
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure NOTA: Gráfico no añadido para la consulta de datos %s y el índice %s debido a un error de verificación de la fuente de datos
MySQL 5.6+ and MariaDB 10.0+ are great releases, and are very good versions to choose. Make sure you run the very latest release though which fixes a long standing low level networking issue that was causing spine many issues with reliability. MySQL 5.6+ y MariaDB 10.0+ son muy buenas versiones para elegir. Asegúrese de usar las últimas versiones ya que resuelven antiguos problemas de red de bajo nivel que causaban a Spine muchos problemas de estabilidad.
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3. Se recomienda que habilites InnoDB en cualquier %s versión superior a 5.1.
When using Cacti with languages other than English, it is important to use the utf8mb4_unicode_ci collation type as some characters take more than a single byte. Cuando use Cacti con otros idiomas que no sean Inglés, es importante usar el tipo de colación utf8mb4_unicode_ci ya que algunos caracteres usan más de un simple Byte.
When using Cacti with languages other than English, it is important to use the utf8mb4 character set as some characters take more than a single byte. Cuando use Cacti con otros idiomas que no sean Inglés, es importante usar el tipo de colación utf8mb4 ya que algunos caracteres usan más de un simple Byte.
It is recommended that you enable InnoDB in any %s version greater than 5.1. Se recomienda que habilites InnoDB en cualquier %s versión superior a 5.1.
Depending on the number of logins and use of spine data collector, %s will need many connections. The calculation for spine is: total_connections = total_processes * (total_threads + script_servers + 1), then you must leave headroom for user connections, which will change depending on the number of concurrent login accounts. Dependiendo en el número de logins y el uso de Spine como recolector de datos, %s necesitará muchas conexiones. El cálculo para Spine es: total_connections = total_processes * (total_threads + script_servers + 1), entonces debes dejar lugar para las conexiones de inicio de sesión de usuarios, que cambiará dependiendo del número de sesiones simultáneas.
Keeping the table cache larger means less file open/close operations when using innodb_file_per_table. Mantener tablas de cache grande significa menos operaciones de abrir/cerrar archivos cuando usas innodb_file_per_table.
With Remote polling capabilities, large amounts of data will be synced from the main server to the remote pollers. Therefore, keep this value at or above 16M. Con funcionalidades de sondeo remoto, grandes cantidades de datos serán sincronizados desde el servidor principal a las sondas remotas. Por lo tanto configure este valor en 16M o superior.
If using the Cacti Performance Booster and choosing a memory storage engine, you have to be careful to flush your Performance Booster buffer before the system runs out of memory table space. This is done two ways, first reducing the size of your output column to just the right size. This column is in the tables poller_output, and poller_output_boost. The second thing you can do is allocate more memory to memory tables. We have arbitrarily chosen a recommended value of 10%% of system memory, but if you are using SSD disk drives, or have a smaller system, you may ignore this recommendation or choose a different storage engine. You may see the expected consumption of the Performance Booster tables under Console -> System Utilities -> View Boost Status.
When executing subqueries, having a larger temporary table size, keep those temporary tables in memory. Cuando se ejecutan sub consultas, teniendo una tabla temporal de gran tamaño, conserva esas tablas temporales en memoria.
When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file. As this is a per connection memory allocation, care must be taken not to increase it too high. The sum of the join_buffer_size + sort_buffer_size + read_buffer_size + read_rnd_buffer_size + thread_stack + binlog_cache_size + Core MySQL/MariaDB memory should be below 80%. If the recommendation is negative, you must decrease this and or the sort_buffer_size until the recommendation fits within the allowable memory.
When using InnoDB storage it is important to keep your table spaces separate. This makes managing the tables simpler for long time users of %s. If you are running with this currently off, you can migrate to the per file storage by enabling the feature, and then running an alter statement on all InnoDB tables. Cuando use almacenamiento InnoDB es importante conservar el espacio de sus tablas separado. Esto hace que manejar las tablas sea más simple a largo plazo para usuarios de %s. Si se está ejecutando sin esto actualmente, puede migrar al almacenamiento por archivo habilitando la funcionalidad, y luego ejecutando una instrucción ALTER a todas las tablas InnoDB.
When using innodb_file_per_table, it is important to set the innodb_file_format to Barracuda. This setting will allow longer indexes important for certain Cacti tables. Cuando se utiliza el archivo_de_innodb_por_tabla, es importante establecer el formato_de_archivo_de_innodb en Barracuda. Esta configuración permitirá índices más largos, importantes para ciertas tablas de Cacti.
If your tables have very large indexes, you must operate with the Barracuda innodb_file_format and the innodb_large_prefix equal to 1. Failure to do this may result in plugins that can not properly create tables. Si sus tablas tienen índices muy grandes, debe operar con Barracuda innodb_file_format y innodb_large_prefix igual a 1. Si no lo hace, es posible que los complementos no puedan crear tablas correctamente.
InnoDB will hold as much tables and indexes in system memory as is possible. Therefore, you should make the innodb_buffer_pool large enough to hold as much of the tables and index in memory. Checking the size of the /var/lib/mysql/cacti directory will help in determining this value. We are recommending 25%% of your systems total memory, but your requirements will vary depending on your systems size.
This settings should remain ON unless your Cacti instances is running on either ZFS or FusionI/O which both have internal journaling to accomodate abrupt system crashes. However, if you have very good power, and your systems rarely go down and you have backups, turning this setting to OFF can net you almost a 50% increase in database performance. Esta configuración debe permanecer ENCENDIDA a menos que sus instancias de Cacti se estén ejecutando en ZFS o FusionI / O, que tienen registros internos para adaptarse a fallas abruptas del sistema. Sin embargo, si tiene muy buena energía, y sus sistemas rara vez fallan y tiene copias de seguridad, desactivar esta configuración puede generar un aumento de casi un 50% en el rendimiento de la base de datos.
Component Translation Difference to current string
This translation Propagated Translated Cacti/core (v1.2.x)
The following string has the same context and source.
Propagated Translated Cacti/core

Loading…

No matching activity found.

Browse all component changes

Glossary

English Spanish
No related strings found in the glossary.

String information

Source string location
lib/utility.php:954
String age
2 years ago
Source string age
3 years ago
Translation file
locales/po/es-ES.po, string 3713