{"id":34842,"date":"2019-10-31T22:00:43","date_gmt":"2019-10-31T19:00:43","guid":{"rendered":"https:\/\/prohoster.info\/blog\/ot-ezhednevnyh-avarij-k-stabilnosti-informatica-10-glazami-admina\/"},"modified":"2019-10-31T22:00:43","modified_gmt":"2019-10-31T19:00:43","slug":"ot-ezhednevnyh-avarij-k-stabilnosti-informatica-10-glazami-admina","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ot-ezhednevnyh-avarij-k-stabilnosti-informatica-10-glazami-admina","title":{"rendered":"Nga aksidentet e p\u00ebrditshme n\u00eb stabilitet: Informatica 10 nga syt\u00eb e adminit","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Nga<\/a><\/noindex><\/p>\n

Komponenta ETL e magazinit t\u00eb dh\u00ebnash shpesh mbetet n\u00eb hije t\u00eb vet\u00eb magazin\u00ebs dhe i kushtohet m\u00eb pak v\u00ebmendje se sa baz\u00ebs kryesore t\u00eb t\u00eb dh\u00ebnave ose komponentit t\u00eb p\u00ebrpar\u00ebm, BI, p\u00ebrgatitjes s\u00eb raporteve. Megjithat\u00eb, nga pik\u00ebpamja mekanike t\u00eb mbushjes s\u00eb magazin\u00ebs me t\u00eb dh\u00ebna, ETL luan nj\u00eb rol ky\u00e7 dhe k\u00ebrkon ashtu si\u00e7 \u00ebsht\u00eb administratori m\u00eb shum\u00eb v\u00ebmendje se komponent\u00ebt e tjer\u00eb. Un\u00eb quhem Aleksand\u00ebr, tani administroj ETL n\u00eb Rostelecom, dhe n\u00eb k\u00ebt\u00eb artikull do t\u00eb p\u00ebrpiqem t\u00eb ndaj pak nga ajo q\u00eb ndodhet p\u00ebrball\u00eb nj\u00eb administratori t\u00eb nj\u00eb prej sistemeve ETL m\u00eb t\u00eb njohura n\u00eb nj\u00eb magazin\u00eb t\u00eb madhe t\u00eb dh\u00ebnash t\u00eb kompanis\u00eb Rostelecom.
\n<\/a><\/noindex>
\nN\u00ebse t\u00eb nderuar lexues jan\u00eb tashm\u00eb t\u00eb njohur n\u00eb p\u00ebrgjith\u00ebsi me projektin ton\u00eb t\u00eb magazin\u00ebs s\u00eb t\u00eb dh\u00ebnave dhe me produktin Informatica PowerCenter, at\u00ebher\u00eb mund t\u00eb kaloni menj\u00ebher\u00eb n\u00eb seksionin tjet\u00ebr.<\/p>\n

Para disa vjet\u00ebsh n\u00eb Rostelecom, lindi dhe u realizua ideja p\u00ebr nj\u00eb magazin\u00eb t\u00eb vetme korporative t\u00eb t\u00eb dh\u00ebnave. Nj\u00eb seri magazinash, q\u00eb zgjidhin detyra t\u00eb ve\u00e7anta, ishin krijuar tashm\u00eb, por numri i skenar\u00ebve po rritej, shpenzimet p\u00ebr mb\u00ebshtetje gjithashtu po rriteshin, dhe ishte e qart\u00eb se e ardhmja \u00ebsht\u00eb centralizimi. Arkitektonikisht, kjo magazin\u00eb p\u00ebrb\u00ebhet nga disa nivele, e realizuar n\u00eb Hadoop dhe GreenPlum, databaza ndihm\u00ebse, mekanizmat ETL dhe BI.<\/p>\n

Megjithat\u00eb, p\u00ebr shkak t\u00eb numrit t\u00eb madh t\u00eb burimeve t\u00eb dh\u00ebnash, t\u00eb shp\u00ebrndara gjeografikisht dhe heterogjene, u krijua nj\u00eb mekaniz\u00ebm i ve\u00e7ant\u00eb p\u00ebr shkarkimin e t\u00eb dh\u00ebnave, puna e t\u00eb cilit menaxhohet nga Informatica. Si rezultat, paketat me t\u00eb dh\u00ebna ndodhen n\u00eb zon\u00ebn nd\u00ebrfyese t\u00eb Hadoop, pasi fillojn\u00eb proceset e ngarkimit t\u00eb t\u00eb dh\u00ebnave n\u00ebp\u00ebr nivelet e magazin\u00ebs, n\u00eb Hadoop dhe GreenPlum, dhe ato menaxhohen nga mekanizmi i quajtur mekanizmi i administrat\u00ebs ETL, i realizuar n\u00eb Informatica. K\u00ebshtu, sistemi Informatica \u00ebsht\u00eb nj\u00eb nga elementet ky\u00e7e q\u00eb sigurojn\u00eb funksionimin e magazin\u00ebs.<\/p>\n

M\u00eb n\u00eb detaje p\u00ebr magazin\u00ebn ton\u00eb do t\u00eb flitet n\u00eb nj\u00eb nga postimet e ardhshme.<\/p>\n

Informatica PowerCenter\/Big Data Management konsiderohet aktualisht si softueri lider n\u00eb fush\u00ebn e mjeteve p\u00ebr integrimin e t\u00eb dh\u00ebnave. Ky \u00ebsht\u00eb nj\u00eb produkt i kompanis\u00eb amerikane Informatica, e cila \u00ebsht\u00eb nj\u00eb nga lojtar\u00ebt m\u00eb t\u00eb fort\u00eb n\u00eb ETL (Extract Transform Load), menaxhimin e cil\u00ebsis\u00eb s\u00eb t\u00eb dh\u00ebnave, MDM (Master Data Management), ILM (Information Lifecycle Management) dhe t\u00eb tjera.<\/p>\n

PowerCenter q\u00eb p\u00ebrdorim \u00ebsht\u00eb nj\u00eb server i integruar i aplikacioneve Tomcat, n\u00eb t\u00eb cilin funksionojn\u00eb aplikacionet Informatica q\u00eb realizojn\u00eb sh\u00ebrbimet e saj: <\/p>\n

Domain<\/b>, n\u00eb thelb, kjo \u00ebsht\u00eb baza p\u00ebr t\u00eb gjitha gj\u00ebrat e tjera, brenda domenit funksionojn\u00eb sh\u00ebrbime, p\u00ebrdorues, komponente GRID.<\/p>\n

Administrator Console<\/b>, nj\u00eb mjet web p\u00ebr menaxhim dhe monitorim, p\u00ebrve\u00e7 klientit Informatica Developer, \u00ebsht\u00eb mjeti kryesor p\u00ebr bashk\u00ebveprimin me produktin<\/p>\n

MRS, Model Repository Service<\/b>, nj\u00eb depo e metadatat, \u00ebsht\u00eb nj\u00eb shtres\u00eb nd\u00ebrmjet baz\u00ebs ku metadatat ruhen fizikisht dhe klientit Informatica Developer, ku zhvillohet. Repository-t ruajn\u00eb si p\u00ebrshkrimin e t\u00eb dh\u00ebnave ashtu edhe informacione t\u00eb tjera, p\u00ebrfshir\u00eb p\u00ebr disa sh\u00ebrbime t\u00eb tjera t\u00eb Informatica, p\u00ebr shembull, orarin e ekzekutimit t\u00eb detyrave (Schedules) ose t\u00eb dh\u00ebnat p\u00ebr monitorim, si dhe setet e parametrave t\u00eb aplikacioneve, t\u00eb cilat p\u00ebrfundojn\u00eb duke lejuar p\u00ebrdorimin e nj\u00ebjtit aplikacion p\u00ebr pun\u00eb me burime dhe destinacione t\u00eb ndryshme t\u00eb t\u00eb dh\u00ebnave.<\/p>\n

DIS, Data Integration Service<\/b>, ky \u00ebsht\u00eb sh\u00ebrbimi ku ndodhin proceset funksionale kryesore, ku aplikacionet punojn\u00eb dhe ndodhin ekzekutimet e Workflows (p\u00ebrshkrimet e sekuencave t\u00eb mappings dhe nd\u00ebrveprimin e tyre) dhe Mappings (transformimet, blloqet ku ndodhin vet\u00eb transformimet, p\u00ebrpunimi i t\u00eb dh\u00ebnave).<\/p>\n

Konfigurimi i GRID<\/b> \u2013 n\u00eb thelb, nj\u00eb variant i nd\u00ebrtimit t\u00eb nj\u00eb kompleksi duke p\u00ebrdorur disa server\u00eb, kur ngarkesa e nisur nga DIS shp\u00ebrndahet n\u00eb node (dmth server\u00eb q\u00eb b\u00ebjn\u00eb pjes\u00eb n\u00eb domen). N\u00eb rastin e k\u00ebtij varianti, p\u00ebrve\u00e7 shp\u00ebrndarjes s\u00eb ngarkes\u00ebs n\u00eb DIS p\u00ebrmes nj\u00eb shtrese t\u00eb m\u00ebtejshme abstraksioni GRID, q\u00eb bashkon disa node, ku punon DIS n\u00eb vend t\u00eb pun\u00ebs p\u00ebr nj\u00eb nod t\u00eb caktuar, gjithashtu mund t\u00eb krijohen kopje rezerv\u00eb shtes\u00eb t\u00eb MRS. Madje mund t\u00eb realizohet nj\u00eb disponueshm\u00ebri e lart\u00eb, kur k\u00ebrkesat e jashtme mund t\u00eb realizohen p\u00ebrmes nodded rezerv\u00eb n\u00eb rast t\u00eb d\u00ebshtimit t\u00eb nodit kryesor. Prej k\u00ebtij varianti t\u00eb nd\u00ebrtimit ne p\u00ebr momentin jemi t\u00eb anuluar.<\/p>\n

\"Nga
\nInformatica PowerCenter, n\u00eb m\u00ebnyr\u00eb skematike<\/i><\/p>\n

N\u00eb fazat e para t\u00eb pun\u00ebs n\u00eb zinxhirin e furnizimit t\u00eb t\u00eb dh\u00ebnave, rregullisht shfaqeshin probleme, disa prej tyre fal\u00eb pun\u00ebs jo t\u00eb q\u00ebndrueshme t\u00eb Informatica n\u00eb at\u00eb koh\u00eb. Un\u00eb kam p\u00ebr q\u00ebllim t\u00eb ndajem disa nga momentet m\u00eb t\u00eb paharrueshme t\u00eb k\u00ebsaj saga - m\u00ebsimi i Informatica 10.<\/p>\n

\"Nga
\nLogotip i m\u00ebparsh\u00ebm i Informatica<\/i><\/p>\n

Fusha e p\u00ebrgjegj\u00ebsive tona p\u00ebrfshin gjithashtu mjedise t\u00eb tjera t\u00eb Informatica, ku ka specifika t\u00eb veta p\u00ebr shkak t\u00eb ngarkes\u00ebs tjet\u00ebr, por deri tani do t\u00eb p\u00ebrmend nj\u00eb m\u00ebnyr\u00eb se si Informatica \u00ebsht\u00eb zhvilluar si komponent ETL i vet\u00eb depozit\u00ebs s\u00eb t\u00eb dh\u00ebnave.<\/p>\n

Si ndodhi kjo<\/h2>\n

\nN\u00eb vitin 2016, kur ne filluam t\u00eb ishim p\u00ebrgjegj\u00ebs p\u00ebr funksionimin e Informatica, ajo tashm\u00eb kishte arritur versionin 10.0, dhe p\u00ebr koleg\u00ebt me mendime optimiste, q\u00eb mor\u00ebn vendimin p\u00ebr t\u00eb p\u00ebrdorur nj\u00eb zgjidhje serioze t\u00eb produktit me nj\u00eb version minor .0, gjith\u00e7ka dukej e qart\u00eb - duhet t\u00eb p\u00ebrdoret versioni i ri! Nga pik\u00ebpamja e burimeve harduerike, gjith\u00e7ka ishte shk\u00eblqyer n\u00eb at\u00eb moment.<\/p>\n

Q\u00eb nga pranvera e vitit 2016, funksionimin e Informatica e kishte nj\u00eb kontraktues, dhe sipas fjal\u00ebve t\u00eb pak p\u00ebrdoruesve t\u00eb sistemit, \"ajo punonte disa her\u00eb n\u00eb jav\u00eb\". K\u00ebtu duhet t\u00eb sqaroj se depozita ishte de facto n\u00eb faz\u00ebn e PoC, nuk kishte administrator\u00eb n\u00eb ekip dhe sistemi binte vazhdimisht p\u00ebr arsye t\u00eb ndryshme, pas s\u00eb cil\u00ebs inxhinieri i kontraktuesit e ringjallte at\u00eb p\u00ebrs\u00ebri.<\/p>\n

N\u00eb vjesht\u00eb n\u00eb ekip u shfaq\u00ebn tre administrator\u00eb, t\u00eb cil\u00ebt ndan\u00eb p\u00ebrgjegj\u00ebsit\u00eb midis tyre dhe filloi t\u00eb nd\u00ebrtohej nj\u00eb pun\u00eb normale p\u00ebr operimin e sistemeve n\u00eb projekt, duke p\u00ebrfshir\u00eb Informatica. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb p\u00ebrmendet se ky produkt nuk \u00ebsht\u00eb i p\u00ebrhapur gjer\u00ebsisht dhe nuk ka nj\u00eb komunitet t\u00eb madh, ku mund t\u00eb gjejm\u00eb p\u00ebrgjigje p\u00ebr \u00e7far\u00ebdo pyetje dhe t\u00eb zgjidhim \u00e7far\u00ebdo problemi. Prandaj, mb\u00ebshtetje teknike e plot\u00eb nga partneri rus i Informatica ishte shum\u00eb e r\u00ebnd\u00ebsishme, me ndihm\u00ebn e t\u00eb cilit u korrigjuan t\u00eb gjitha gabimet tona dhe ato t\u00eb Informatica 10, q\u00eb ishte ende e re.<\/p>\n

Gj\u00ebja e par\u00eb q\u00eb na duhej t\u00eb b\u00ebnim p\u00ebr zhvilluesit e ekipit ton\u00eb dhe kontraktuesin - t\u00eb stabilizojm\u00eb funksionimin e vet\u00eb Informatica, p\u00ebr t\u00eb arritur funksionalitetin e web-konsol\u00ebs s\u00eb administrat\u00ebs (Informatica Administrator).<\/p>\n

\"Nga
\nK\u00ebshtu, shpesh takonim zhvilluesit e Informatica.<\/i><\/p>\n

Duke l\u00ebn\u00eb anash vet\u00eb procesin e zbardhjes s\u00eb arsyeve, arsyeja kryesore e r\u00ebnieve ishte skema e bashk\u00ebpunimit t\u00eb softuerit Informatica me baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb depozit\u00ebs, e cila ndodhej n\u00eb nj\u00eb server relativisht t\u00eb larg\u00ebt, n\u00eb lidhje me peizazhin rrjetor. Kjo shkaktonte vonesa dhe d\u00ebmtonte funksionimin e mekanizmave q\u00eb siguronin kontrollin e gjendjes s\u00eb domain-it Informatica. Pas disa optimizimeve t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave, ndryshimeve t\u00eb parametrave t\u00eb Informatica, q\u00eb e b\u00ebn\u00eb at\u00eb m\u00eb tolerant ndaj vonesave t\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave, si dhe p\u00ebrdit\u00ebsimit t\u00eb versionit t\u00eb Informatica n\u00eb 10.1 dhe zhvendosjes s\u00eb baz\u00ebs s\u00eb t\u00eb dh\u00ebnave nga serveri i m\u00ebparsh\u00ebm n\u00eb nj\u00eb server m\u00eb t\u00eb af\u00ebrt me Informatica, problemi humbi aktualitetin dhe qysh at\u00ebher\u00eb nuk kemi v\u00ebrejtur r\u00ebnie t\u00eb k\u00ebtij lloji.<\/p>\n

\"Nga
\nNj\u00eb nga p\u00ebrpjekjet p\u00ebr t\u00eb arritur funksionimin e Informatica Monitor<\/i><\/p>\n

Situata me konsol\u00ebn e administrat\u00ebs gjithashtu ishte kritike. Pasi po zhvillohej aktivisht n\u00eb nj\u00eb mjedis q\u00eb supozohej se ishte produktiv, koleg\u00ebt kishin nevoj\u00eb t\u00eb analizojn\u00eb pun\u00ebn e mappings, workflow 'n\u00eb l\u00ebvizje'. N\u00eb Informatica t\u00eb re, n\u00eb Sh\u00ebrbimin e Integrimit t\u00eb T\u00eb Dh\u00ebnave nuk ka nj\u00eb mjet t\u00eb ve\u00e7ant\u00eb p\u00ebr t\u00eb till\u00eb monitorim, por n\u00eb web-konsol\u00ebn e administrat\u00ebs \u00ebsht\u00eb shfaqur nj\u00eb seksion monitorimi (Informatica Administrator Monitor), ku mund t\u00eb v\u00ebreni pun\u00ebn e aplikacioneve, workflow dhe mappings, nisjet, logjet. Periodikisht konsola b\u00ebhej krejt\u00ebsisht e pa akses, ose informatat p\u00ebr proceset aktuale n\u00eb DIS nuk rifreshoheshin, ose shfaqeshin gabime gjat\u00eb ngarkimit t\u00eb faqeve.<\/p>\n

\"Nga
\nP\u00ebrzgjedhja e parametrave java p\u00ebr stabilizimin e pun\u00ebs<\/i><\/p>\n

Korrigjimi i problemit po b\u00ebhej n\u00eb shum\u00eb m\u00ebnyra, eksperimentet p\u00ebr ndryshimin e parametrave u zhvilluan, logjet u mblodh\u00ebn, jstack u d\u00ebrgua n\u00eb mb\u00ebshtetje, n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb po b\u00ebhej k\u00ebrkimi aktiv n\u00eb Google dhe thjesht u b\u00eb v\u00ebzhgim.<\/p>\n

S\u00eb pari, u krijua nj\u00eb MRS e ve\u00e7ant\u00eb p\u00ebr monitorim, si\u00e7 doli m\u00eb von\u00eb, kjo ishte nj\u00eb nga konsumator\u00ebt kryesor\u00eb t\u00eb burimeve n\u00eb mjediset tona, pasi nisjet e mappings ndodhin shum\u00eb intensivisht. U ndryshuan parametrat q\u00eb lidhen me java heap, si dhe nj\u00eb s\u00ebr\u00eb t\u00eb tjerave.
\nSi rezultat, n\u00eb p\u00ebrdit\u00ebsimin e ardhsh\u00ebm t\u00eb Informatica 10.1.1, arrit\u00ebm t\u00eb stabilizojm\u00eb funksionimin e konsol\u00ebs dhe monitorit, zhvilluesit filluan t\u00eb punojn\u00eb m\u00eb efikasht, dhe proceset e rregullta b\u00ebheshin gjithnj\u00eb e m\u00eb t\u00eb rregullta.<\/p>\n

Eksperienca e bashk\u00ebveprimit mes zhvillimit dhe administrimit mund t\u00eb jet\u00eb interesante. Pyetja e kuptimit t\u00eb p\u00ebrbashk\u00ebt, se si funksionon gjith\u00e7ka, \u00e7far\u00eb mund t\u00eb b\u00ebhet dhe \u00e7far\u00eb nuk mund t\u00eb b\u00ebhet, p\u00ebrher\u00eb \u00ebsht\u00eb e r\u00ebnd\u00ebsishme kur p\u00ebrdoren sisteme komplekse. Prandaj, mund t\u00eb rekomandohet q\u00eb s\u00eb pari t\u00eb trajnohet ekipi i administruesve se si duhet t\u00eb administrohet softueri, dhe ekipi i zhvilluesve se si duhet t\u00eb shkruhet kodi dhe t\u00eb vizatohen proceset n\u00eb sistem, dhe vet\u00ebm pastaj t\u2019i d\u00ebrgoni ata t\u00eb punojn\u00eb p\u00ebr rezultate. Kjo \u00ebsht\u00eb me t\u00eb v\u00ebrtet\u00eb e r\u00ebnd\u00ebsishme kur koha nuk \u00ebsht\u00eb nj\u00eb burim i pafund. Shum\u00eb probleme mund t\u00eb zgjidhen madje edhe me nj\u00eb p\u00ebrzgjedhje rast\u00ebsore t\u00eb mund\u00ebsive, por her\u00eb pas here disa k\u00ebrkojn\u00eb njohuri a priori - rasti yn\u00eb konfirmon r\u00ebnd\u00ebsin\u00eb e kuptimit t\u00eb k\u00ebsaj aksiome.<\/p>\n

P\u00ebr shembull, gjat\u00eb p\u00ebrpjekjes p\u00ebr t\u00eb aktivizuar versionimin n\u00eb MRS (si\u00e7 doli, ishte e nevojshme nj\u00eb version tjet\u00ebr t\u00eb SVN), pas nj\u00eb kohe ne e zbuluam me shqet\u00ebsim se koha e rinisjes s\u00eb sistemit ishte rritur n\u00eb disa dhjet\u00ebra minuta. Duke dal\u00eb n\u00eb shkakun e vones\u00ebs n\u00eb fillim dhe duke \u00e7aktivizuar versionimin, e b\u00ebm\u00eb s\u00ebrish mir\u00eb.<\/p>\n

Nga pengesat e dukshme q\u00eb lidhen me Informatica, mund t\u00eb p\u00ebrmendim luft\u00ebn epike me rritjen e rrjedhave java. N\u00eb nj\u00eb moment, erdhi koha p\u00ebr replikimin, pra p\u00ebr t\u00eb p\u00ebrhapur proceset e vendosura n\u00eb nj\u00eb num\u00ebr t\u00eb madh sistemesh burimore. Gjat\u00eb k\u00ebsaj, doli se jo t\u00eb gjitha proceset n\u00eb 10.1.1 funksiononin mir\u00eb, dhe pas nj\u00eb kohe DIS b\u00ebhej jo funksional. Zbuloheshin dhjet\u00ebra mij\u00ebra rrjedha, numri i t\u00eb cilave rritej ve\u00e7an\u00ebrisht gjat\u00eb procedur\u00ebs s\u00eb shp\u00ebrndarjes s\u00eb aplikacioneve. Her\u00eb pas here duhej t\u00eb b\u00ebjm\u00eb rinisje disa her\u00eb n\u00eb dit\u00eb p\u00ebr t\u00eb rikthyer funksionalitetin.<\/p>\n

K\u00ebtu duhet fal\u00ebnderuar mb\u00ebshtetjen, gjith\u00e7ka u lokalizua dhe u rregullua relativisht shpejt me ndihm\u00ebn e EBF (Rregullimi i Jasht\u00ebzakonsh\u00ebm t\u00eb Gabimeve) - pas k\u00ebsaj t\u00eb gjith\u00ebve iu ndie se instrumenti me t\u00eb v\u00ebrtet\u00eb funksionon.<\/p>\n

P\u00ebrfundimisht funksionon!<\/h2>\n

\nN\u00eb momentin e fillimit t\u00eb pun\u00ebs n\u00eb modin e synuar, Informatica dukej si m\u00eb posht\u00eb. Versioni Informatica 10.1.1HF1 (HF1 \u00ebsht\u00eb HotFix1, nd\u00ebrtimi i furnizuesit nga kompleksi i EBF-ve) me EBF shtes\u00eb t\u00eb instaluara, q\u00eb rregullojn\u00eb problemet tona me shkall\u00ebzimin dhe disa t\u00eb tjera, n\u00eb nj\u00eb server nga tre q\u00eb ishin pjes\u00eb e GRID-it, 20 b\u00ebrthama x86_64 dhe ruajtje n\u00eb nj\u00eb sasi t\u00eb madhe t\u00eb ngadalt\u00eb t\u00eb disqeve lokale - kjo konfigurimi i serverit<\/a> p\u00ebr klasterin Hadoop. N\u00eb nj\u00eb server tjet\u00ebr t\u00eb ngjash\u00ebm \u2014 Baza e t\u00eb Dh\u00ebnave Oracle me t\u00eb cil\u00ebn punon dhe domeni Informatica dhe mekanizmi menaxhues ETL. T\u00eb gjitha k\u00ebto monitorohen me mjete standarde monitorimi, t\u00eb p\u00ebrdorura nga ekipi (Zabbix + Grafana), nga dy an\u00eb \u2014 si Informatica me sh\u00ebrbimet e saj, ashtu edhe proceset e ngarkes\u00ebs q\u00eb i drejtohen asaj. Tani p\u00ebr tani, si performanca ashtu edhe stabiliteti i pun\u00ebs, pa marr parasysh faktor\u00ebt e jasht\u00ebm, varen nga konfigurimet q\u00eb kufizojn\u00eb ngarkes\u00ebn.<\/p>\n

Ve\u00e7mas mund t\u00eb flasim p\u00ebr GRID-in. Mjedisi u nd\u00ebrtua mbi tre node, me mund\u00ebsi p\u00ebr balancimin e ngarkes\u00ebs. Megjithat\u00eb, gjat\u00eb testimit u zbulua se p\u00ebr shkak t\u00eb problemeve n\u00eb nd\u00ebrveprimin mes instanceve t\u00eb aplikacioneve tona, nj\u00eb konfigurim i till\u00eb nuk funksiononte si\u00e7 pritej, dhe p\u00ebrkoh\u00ebsisht u vendos t\u00eb hiqet dor\u00eb nga ky skem\u00eb nd\u00ebrtimi, duke \u00e7uar jasht\u00eb domenit dy nga tre node. Sidoqoft\u00eb, skema mbeti e nj\u00ebjta, dhe tani \u00ebsht\u00eb pik\u00ebrisht nj\u00eb sh\u00ebrbim GRID, por i shnd\u00ebrruar n\u00eb nj\u00eb node.<\/p>\n

Aktualisht mbetet nj\u00eb v\u00ebshtir\u00ebsi e lidhur me r\u00ebnien e performanc\u00ebs gjat\u00eb pastrimit t\u00eb rregullt t\u00eb skem\u00ebs s\u00eb monitorit \u2014 kur proceset po ndodhin n\u00eb m\u00ebnyr\u00eb t\u00eb sinkronizuar dhe pastrimi \u00ebsht\u00eb n\u00eb zhvillim, mund t\u00eb ndodhin d\u00ebshtime n\u00eb pun\u00ebn e mekanizmit menaxhues ETL. Kjo aktualisht zgjidhet n\u00eb m\u00ebnyr\u00eb \"t\u00eb p\u00ebrkohshme\" \u2014 me pastrimin manual t\u00eb skem\u00ebs s\u00eb monitorit, me humbjen e t\u00eb dh\u00ebnave t\u00eb m\u00ebparshme. Kjo nuk \u00ebsht\u00eb shum\u00eb kritike p\u00ebr produktivitetin, gjat\u00eb funksionimit normal, por akoma po k\u00ebrkohet nj\u00eb zgjidhje t\u00eb duhur.<\/p>\n

Nga kjo situat\u00eb rrjedh edhe nj\u00eb problem tjet\u00ebr \u2014 her\u00eb pas here ndodhin nj\u00ebsit\u00eb e shumta t\u00eb mekanizmit ton\u00eb menaxhues.<\/p>\n

\"Nga
\nNj\u00ebsit\u00eb e shumta t\u00eb aplikacionit, q\u00eb \u00e7ojn\u00eb n\u00eb prishjen e mekanizmit<\/i><\/p>\n

Gjat\u00eb nisjes sipas orarit n\u00eb momentet me ngarkes\u00eb t\u00eb madhe n\u00eb sistem, nganj\u00ebher\u00eb ndodhin situata t\u00eb tilla q\u00eb \u00e7ojn\u00eb n\u00eb prishjen e mekanizmit. Deri tani problemi zgjidhet manualisht, dhe po k\u00ebrkohet nj\u00eb zgjidhje t\u00eb p\u00ebrhershme.<\/p>\n

N\u00eb p\u00ebrgjith\u00ebsi, mund t\u00eb p\u00ebrmblidhet se, n\u00eb kushte t\u00eb ngarkes\u00ebs s\u00eb madhe, \u00ebsht\u00eb shum\u00eb e r\u00ebnd\u00ebsishme t\u00eb ofrosh burime t\u00eb p\u00ebrshtatshme p\u00ebr t\u00eb, kjo p\u00ebrfshin burimet harduerike p\u00ebr vet\u00eb Informatica, si dhe p\u00ebr depozit\u00ebn e saj DB, si dhe sigurimin e konfigurimeve optimale p\u00ebr to. P\u00ebr m\u00eb tep\u00ebr, ngeli i hapur pyetja se cila skem\u00eb vendosjeje t\u00eb DB \u00ebsht\u00eb m\u00eb e mir\u00eb - n\u00eb nj\u00eb host t\u00eb ve\u00e7ant\u00eb, apo n\u00eb t\u00eb nj\u00ebjtin ku punon programi Informatica. Nga nj\u00ebra an\u00eb, n\u00eb nj\u00eb server do t\u00eb ishte m\u00eb lir\u00eb dhe duke u kombinuar, praktiikisht zgjidhet problemi i mundsh\u00ebm me nd\u00ebrveprimin rrjetor, nga ana tjet\u00ebr \u2014 ngarkesa n\u00eb host nga DB shtohet me ngarkes\u00ebn nga Informatica.<\/p>\n

Si n\u00eb \u00e7do produkt t\u00eb r\u00ebnd\u00ebsish\u00ebm, n\u00eb Informatica ka dhe momente komike.
\nNj\u00eb her\u00eb, duke analizuar ndonj\u00eb aksident, vura re se n\u00eb logot MRS ishte sh\u00ebnuar pazakonisht koha e ngjarjeve.<\/p>\n

\"Nga
\nDualizmi temporal n\u00eb logot MRS 'sip\u00ebr dizajnit'<\/i><\/p>\n

Doli se koh\u00ebt sh\u00ebnohen n\u00eb formatin 12-or\u00ebsh, pa sh\u00ebnimin AM\/PM, pra para ose pas mesdit\u00ebs. Madje ishte hapur nj\u00eb k\u00ebrkes\u00eb p\u00ebr k\u00ebt\u00eb \u00e7\u00ebshtje dhe u mor nj\u00eb p\u00ebrgjigje zyrtare - k\u00ebshtu ishte menduar, n\u00eb logun MRS sh\u00ebnohen pik\u00ebrisht n\u00eb k\u00ebt\u00eb format. Dometh\u00ebn\u00eb, ndonj\u00ebher\u00eb ka mbetur nj\u00eb mister n\u00eb lidhje me or\u00ebn e shfaqjes s\u00eb ndonj\u00eb ERROR-i...<\/p>\n

T\u00eb synosh p\u00ebr t\u00eb mir\u00ebn<\/h2>\n

\nSot Informatica \u00ebsht\u00eb nj\u00eb mjet mjaft i q\u00ebndruesh\u00ebm, i p\u00ebrshtatsh\u00ebm p\u00ebr administratorin dhe p\u00ebrdoruesit, jasht\u00ebzakonisht i fuqish\u00ebm p\u00ebr mund\u00ebsit\u00eb dhe potencialin aktual. Ai tejkalon disa her\u00eb funksionalisht nevojat tona dhe de facto p\u00ebrdoret tani n\u00eb projekt n\u00eb nj\u00eb m\u00ebnyr\u00eb jo t\u00eb zakonshme dhe tipike. V\u00ebshtir\u00ebsit\u00eb lidhen pjes\u00ebrisht me m\u00ebnyr\u00ebn si funksionojn\u00eb mekanizmat - specifikisht \u00ebsht\u00eb se p\u00ebr nj\u00eb periudh\u00eb t\u00eb shkurt\u00ebr kohore aktivizohen nj\u00eb num\u00ebr i madh kanalesh q\u00eb p\u00ebrdit\u00ebsojn\u00eb intensivisht parametrat e setit dhe punojn\u00eb me DB-n\u00eb e depozit\u00ebs, nd\u00ebrkoh\u00eb q\u00eb burimet harduerike t\u00eb serverit shfryt\u00ebzohen praktikisht plot\u00ebsisht n\u00eb CPU. <\/p>\n

Tani jemi af\u00ebr kalimit n\u00eb Informatica 10.2.1 ose 10.2.2, n\u00eb t\u00eb cilat jan\u00eb rishikuar disa mekanizma t\u00eb brendsh\u00ebm, dhe mb\u00ebshtetja premton se do t\u00eb mungojn\u00eb disa nga problemet e tanishme q\u00eb kemi me performanc\u00ebn dhe funksionimin. Po ashtu, nga pik\u00ebpamja harduerike pritet t\u00eb kemi server\u00eb me konfigurimin optimal p\u00ebr ne, duke marr\u00eb parasysh rezervat p\u00ebr periudh\u00ebn n\u00eb vijim p\u00ebr shkak t\u00eb rritjes dhe zhvillimit t\u00eb depozitave.<\/p>\n

Natyrisht, do t\u00eb ket\u00eb testime, verifikime t\u00eb p\u00ebrputhshm\u00ebris\u00eb, dhe ndoshta, ndryshime arkitekturore n\u00eb lidhje me HA GRID. Zhvillimi brenda Informatica do t\u00eb vazhdoj\u00eb, pasi n\u00eb nj\u00eb perspektiv\u00eb afatshkurt\u00ebr nuk mund t\u00eb vendosim di\u00e7ka p\u00ebr t\u00eb z\u00ebvend\u00ebsuar sistemin.
\nDhe ata q\u00eb n\u00eb t\u00eb ardhmen do t\u00eb jen\u00eb p\u00ebrgjegj\u00ebs p\u00ebr k\u00ebt\u00eb sistem, patjet\u00ebr q\u00eb do t\u00eb arrijn\u00eb ta \u00e7ojn\u00eb at\u00eb n\u00eb nivelet e k\u00ebrkuara t\u00eb besueshm\u00ebris\u00eb dhe performanc\u00ebs q\u00eb k\u00ebrkojn\u00eb klient\u00ebt.<\/p>\n

Artikulli \u00ebsht\u00eb p\u00ebrgatitur nga ekipi i menaxhimit t\u00eb t\u00eb dh\u00ebnave t\u00eb \"Rostelecom\".<\/i><\/p>\n

\"Nga
\nLogoja aktuale e Informatica<\/i>
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

ETL-\u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u0430 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430 \u0434\u0430\u043d\u043d\u044b\u0445 \u0447\u0430\u0441\u0442\u043e \u043e\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u0432 \u0442\u0435\u043d\u0438 \u0441\u0430\u043c\u043e\u0433\u043e \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430 \u0438 \u0435\u0439 \u0443\u0434\u0435\u043b\u044f\u0435\u0442\u0441\u044f \u043c\u0435\u043d\u044c\u0448\u0435 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u044f, \u0447\u0435\u043c \u0433\u043b\u0430\u0432\u043d\u043e\u0439 \u0431\u0430\u0437\u0435 \u0434\u0430\u043d\u043d\u044b\u0445 \u0438\u043b\u0438 \u0444\u0440\u043e\u043d\u0442-\u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u0435, BI, \u0444\u043e\u0440\u043c\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438 \u043e\u0442\u0447\u0451\u0442\u043e\u0432. \u041f\u0440\u0438 \u044d\u0442\u043e\u043c \u0441 \u0442\u043e\u0447\u043a\u0438 \u0437\u0440\u0435\u043d\u0438\u044f \u043c\u0435\u0445\u0430\u043d\u0438\u043a\u0438 \u043d\u0430\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430 \u0434\u0430\u043d\u043d\u044b\u043c\u0438, ETL \u0438\u0433\u0440\u0430\u0435\u0442 \u043a\u043b\u044e\u0447\u0435\u0432\u0443\u044e \u0440\u043e\u043b\u044c \u0438 \u0442\u0440\u0435\u0431\u0443\u0435\u0442 \u043d\u0435 \u043c\u0435\u043d\u044c\u0448\u0435 \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u044f \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u043e\u0432, \u0447\u0435\u043c \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0435 \u043a\u043e\u043c\u043f\u043e\u043d\u0435\u043d\u0442\u044b. \u041c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 \u0410\u043b\u0435\u043a\u0441\u0430\u043d\u0434\u0440, \u0441\u0435\u0439\u0447\u0430\u0441 \u044f \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u0443\u044e ETL \u0432 \u0420\u043e\u0441\u0442\u0435\u043b\u0435\u043a\u043e\u043c\u0435, \u0438 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26234,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-34842","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Nga emergjencat e p\u00ebrditshme n\u00eb stabilitet: Informatica 10 sipas adminit | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ot-ezhednevnyh-avarij-k-stabilnosti-informatica-10-glazami-admina","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041e\u0442 \u0435\u0436\u0435\u0434\u043d\u0435\u0432\u043d\u044b\u0445 \u0430\u0432\u0430\u0440\u0438\u0439 \u043a \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u043e\u0441\u0442\u0438: Informatica 10 \u0433\u043b\u0430\u0437\u0430\u043c\u0438 \u0430\u0434\u043c\u0438\u043d\u0430 | ProHoster","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ot-ezhednevnyh-avarij-k-stabilnosti-informatica-10-glazami-admina","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:00:43+00:00","article:modified_time":"2019-10-31T19:00:43+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"34842","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-02-08 21:32:10","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:14:05","updated":"2026-02-08 21:32:10","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/34842","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=34842"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/34842\/revisions"}],"predecessor-version":[{"id":158197,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/34842\/revisions\/158197"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/26234"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=34842"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=34842"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=34842"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}