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.
207/2430 · 243
English Latvian
Error while parsing the XML of RRDtool dump Kļūda, parsējot RRDtool izgāztuves XML
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) noņemts no RRD faila
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) pievieno RRD failam
Website does not have write access to %s, may be unable to create/update RRDs Vietnei nav rakstīšanas piekļuves %s, iespējams, nevar izveidot/atjaunināt RRD
(Custom) (Pielāgots)
Failed to open data file, poller may not have run yet Neizdevās atvērt datu failu, iespējams, aptaujātajs vēl nav palaists
RRA Folder RRA mape
Root ROOT - uz objektu orientēta bibliotēku kopa mērogojamu datu analīzei
Unknown RRDtool Error Nezināma RRDtool kļūda
Attempting to Create Graph from Non-Template Mēģinājums izveidot grafiku no neveidnes
Attempting to Create Graph from Removed Graph Template Mēģinājums izveidot grafiku no noņemtās diagrammas veidnes
Created: %s Izveidots: %s
ERROR: Whitelist Validation Failed. Check Data Input Method KĻŪDA: baltā saraksta validācija neizdevās. Pārbaudiet datu ievades metodi
Graph Not created for %s due to bad data Grafiks nav izveidots priekš
NOTE: Graph not added for Data Query %s and index %s due to Data Source verification failure
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+ un MariaDB 10.0+ ir lieliski laidieni, un to izvēle ir ļoti laba. Noteikti izmantojiet jaunāko versiju, kas novērš ilgstošu zema līmeņa tīkla problēmu, kas izraisīja daudzas uzticamības problēmas.
It is STRONGLY recommended that you enable InnoDB in any %s version greater than 5.5.3. Ir stingri ieteicams iespējot InnoDB jebkurā %s versijā, kas ir vecāka par 5.5.3.
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. Izmantojot Cacti citās valodās, nevis angļu valodā, ir svarīgi izmantot utf8mb4_unicode_ci salīdzināšanas veidu, jo dažas rakstzīmes aizņem vairāk nekā vienu baitu.
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. Izmantojot Cacti citās valodās, nevis angļu valodā, ir svarīgi izmantot rakstzīmju kopu utf8mb4, jo dažas rakstzīmes aizņem vairāk nekā vienu baitu.
It is recommended that you enable InnoDB in any %s version greater than 5.1. Ieteicams iespējot InnoDB jebkurā %s versijā, kas ir vecāka par 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. Atkarībā no pieteikšanās reižu skaita un mugurkaula datu savācēja izmantošanas, %s būs nepieciešami daudzi savienojumi. Mugurkaula aprēķins ir šāds: total_connections = total_processes * (total_threads + script_servers + 1), tad jums ir jāatstāj brīva vieta lietotāju savienojumiem, kas mainīsies atkarībā no vienlaicīgo pieteikšanās kontu skaita.
Keeping the table cache larger means less file open/close operations when using innodb_file_per_table. Ja tiek saglabāta lielāka tabulas kešatmiņa, tad, izmantojot innodb_file_per_table, failu atvēršanas/aizvēršanas operāciju skaits ir mazāks.
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. Izmantojot attālās aptaujas iespējas, liels datu apjoms tiks sinhronizēts no galvenā servera uz attālajiem aptaujātājiem. Tāpēc saglabājiet šo vērtību 16 miljoni vai vairāk.
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. Ja izmantojat Cacti Performance Booster un izvēlaties atmiņas krātuves dzinēju, jums ir jābūt uzmanīgiem, lai izskalotu Performance Booster buferi, pirms sistēmā beigsies vieta atmiņas tabulā. Tas tiek darīts divos veidos, vispirms samazinot izvades kolonnas izmēru līdz pareizajam izmēram. Šī kolonna atrodas tabulās poller_output un poller_output_boost. Otra lieta, ko varat darīt, ir piešķirt vairāk atmiņas atmiņas tabulām. Mēs esam patvaļīgi izvēlējušies ieteicamo sistēmas atmiņas vērtību — 10%%, taču, ja izmantojat SSD disku diskus vai jums ir mazāka sistēma, varat ignorēt šo ieteikumu vai izvēlēties citu krātuves programmu. Varat redzēt paredzamo Performance Booster tabulu patēriņu sadaļā Console -> System Utilities -> View Boost Status.
When executing subqueries, having a larger temporary table size, keep those temporary tables in memory. Izpildot apakšvaicājumus, kuriem ir lielāks pagaidu tabulas izmērs, saglabājiet šīs pagaidu tabulas atmiņā.
If this number is negative, reduce the innodb_buffer_pool_size until the join_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the systems memory if the database is separate from the Cacti web server. However, try to not go below the default of 262,144. 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 database is hosted on the Cacti web server and less if you intend to have very large RRDfiles or hundreds of thousands to millions long term.
If this number is negative, reduce the innodb_buffer_pool_size until the sort_buffer_size turns positive, but allocate approximately from between 25%-50% of memory to the innodb_buffer_pool_size if the database is hosted on the Cacti server, or upto 80% of the system memory if the database is separate from the Cacti web server. However, try to not go below the default setting of 2,097,152. A sort buffer performs sorts for some queries using ORDER BY or GROUP BY. Configuring sort_buffer_size decides how much memory will be allocated for sort queries. The sort_buffer_size may need to be adjusted from the default if the workload requires a significant number of sort queries. The sort_buffer_size is defined on a per-session variable. Use the same equation as that of the join_buffer_size to determine the per connection possible 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. Izmantojot InnoDB krātuvi, ir svarīgi saglabāt tabulas vietas atsevišķi. Tas padara tabulu pārvaldību vienkāršāku ilgstošiem %s lietotājiem. Ja pašlaik izmantojat šo funkciju, varat migrēt uz katra faila krātuvi, iespējojot līdzekli un pēc tam izpildot paziņojumu par izmaiņām visās InnoDB tabulās.
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. Izmantojot innodb_file_per_table, ir svarīgi iestatīt innodb_file_format uz Barracuda. Šis iestatījums ļaus izmantot garākus indeksus, kas ir svarīgi noteiktām kaktusu tabulām.
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. Ja jūsu tabulām ir ļoti lieli indeksi, jums ir jādarbojas ar Barracuda innodb_file_format un innodb_large_prefiksu, kas ir vienāds ar 1. Ja to neizdarīsit, spraudņi var nespēt pareizi izveidot tabulas.
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. If you database is very large or remote, you can consider increasing this size. If remote, it can by as high as 80% of the systems memory. However, cautions must be taken to reduce the swapiness of the system, or to remove swap to keep the system from swapping. InnoDB sistēmas atmiņā glabās pēc iespējas vairāk tabulu un indeksu. Tāpēc innodb_buffer_pool ir jāpadara pietiekami liels, lai tajā saglabātu pēc iespējas vairāk tabulu un indeksu. Pārbaudot direktorijas /var/lib/mysql/cacti lielumu, varēsiet noteikt šo vērtību. Mēs iesakām 25%% no jūsu sistēmas kopējās atmiņas, taču jūsu prasības atšķirsies atkarībā no sistēmas lieluma.
Component Translation Difference to current string
This translation Propagated Translated Cacti/core
The following string has the same context and source.
Propagated Translated Cacti/core (v1.2.x)

Loading…

No matching activity found.

Browse all component changes

Glossary

English Latvian
No related strings found in the glossary.

String information

Source string location
lib/utility.php:961
String age
2 years ago
Source string age
3 years ago
Translation file
locales/po/lv-LV.po, string 4078