{"id":100516,"date":"2021-06-14T16:22:58","date_gmt":"2021-06-14T14:22:58","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-rqlite-6-0-raspredelyonnoj-otkazoustojchivoj-subd-na-osnove-sqlite"},"modified":"2021-06-14T16:22:58","modified_gmt":"2021-06-14T14:22:58","slug":"vypusk-rqlite-6-0-raspredelyonnoj-otkazoustojchivoj-subd-na-osnove-sqlite","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/news\/vypusk-rqlite-6-0-raspredelyonnoj-otkazoustojchivoj-subd-na-osnove-sqlite","title":{"rendered":"Publikimi i rqlite 6.0, nj\u00eb DBMS e shp\u00ebrndar\u00eb dhe tolerante ndaj d\u00ebshtimeve, e bazuar n\u00eb SQLite","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Rqlite 6.0, nj\u00eb sistem menaxhimi t\u00eb t\u00eb dh\u00ebnave t\u00eb shp\u00ebrndara, \u00ebsht\u00eb publikuar, i cili p\u00ebrdor SQLite si motor ruajtjeje dhe mund\u00ebson funksionimin e nj\u00eb klasteri t\u00eb ruajtesh t\u00eb sinkronizuara me nj\u00ebra-tjetr\u00ebn. Rqlite ve\u00e7ohet p\u00ebr thjesht\u00ebsin\u00eb e instalimit, shp\u00ebrndarjes dhe mb\u00ebshtetjes s\u00eb nj\u00eb ruajtjeje t\u00eb shp\u00ebrndar\u00eb t\u00eb q\u00ebndrueshme, e cila \u00ebsht\u00eb e ngjashme me etcd dhe Consul, por p\u00ebrdor nj\u00eb model relacional t\u00eb pun\u00ebs me t\u00eb dh\u00ebna n\u00eb vend t\u00eb formatit \u00e7el\u00ebs\/vler\u00eb. Kodi i projektit \u00ebsht\u00eb shkruar n\u00eb gjuh\u00ebn Go dhe shp\u00ebrndahet n\u00ebn licenc\u00ebn MIT. <\/p>\n
P\u00ebr t\u00eb mb\u00ebshtetur t\u00eb gjith\u00eb nodet n\u00eb nj\u00eb gjendje t\u00eb sinkronizuar, p\u00ebrdoret algoritmi i arritjes s\u00eb konsensusit Raft. Rqlite p\u00ebrdor bibliotek\u00ebn origjinale SQLite dhe driver-in e zakonsh\u00ebm go-sqlite3, mbi t\u00eb cilat funksionon nj\u00eb shtres\u00eb q\u00eb p\u00ebrpunon k\u00ebrkesat e klient\u00ebve, kryen replikimin n\u00eb nodet e tjera dhe ndjek arritjen e konsensusit mbi zgjedhjen e nodit lider. <\/p>\n
Ndryshimet n\u00eb DB mund t\u00eb b\u00ebhen vet\u00ebm nga nodi q\u00eb \u00ebsht\u00eb zgjedhur si lider, por lidhjet me operacionet e shkrimit mund t\u00eb drejtohen gjithashtu edhe n\u00eb nodet e tjera t\u00eb klasterit, t\u00eb cilat do t\u00eb kthejn\u00eb adres\u00ebn e liderit p\u00ebr t\u00eb rip\u00ebrs\u00ebritur k\u00ebrkes\u00ebn (n\u00eb versionin e ardhsh\u00ebm premtohet q\u00eb t\u00eb shtohet kalimi automatik i k\u00ebrkesave tek lideri). Fokusimi kryesor \u00ebsht\u00eb n\u00eb q\u00ebndrueshm\u00ebri, prandaj sistemi i menaxhimit t\u00eb t\u00eb dh\u00ebnave \u00ebsht\u00eb n\u00eb skalim vet\u00ebm p\u00ebr operacionet e leximit, nd\u00ebrsa operacionet e shkrimit jan\u00eb pika e dob\u00ebt. \u00cbsht\u00eb e mundur t\u00eb fillosh nj\u00eb klaster rqlite nga nj\u00eb nod i vet\u00ebm dhe kjo zgjidhje mund t\u00eb p\u00ebrdoret p\u00ebr t\u00eb organizuar aksesin n\u00eb SQLite p\u00ebrmes HTTP pa ofruar q\u00ebndrueshm\u00ebri. <\/p>\n
T\u00eb dh\u00ebnat SQLite n\u00eb \u00e7do nod ruhen jo n\u00eb skedar, por n\u00eb memorie. N\u00eb nivelin e shtres\u00ebs me implementimin e protokollit Raft, mbahet nj\u00eb regist\u00ebr i t\u00eb gjith\u00eb komandueseve SQLite, t\u00eb cilat \u00e7ojn\u00eb n\u00eb ndryshimin e DB. Ky regist\u00ebr p\u00ebrdoret n\u00eb replikim (replikim n\u00eb nivelin e riprodhimit t\u00eb k\u00ebrkesave n\u00eb nodet e tjera), fillimin e nj\u00eb nodi t\u00eb ri ose rikuperimin pas humbjes s\u00eb lidhjes. P\u00ebr t\u00eb reduktuar madh\u00ebsin\u00eb e regjistrit, aplikohet paketimi automatik, i cili nisi pas nj\u00eb numri t\u00eb caktuar ndryshimesh dhe rezulton n\u00eb ruajtjen n\u00eb disk t\u00eb nj\u00eb snapshot-i, n\u00eb lidhje me t\u00eb cilin fillon t\u00eb mbahet nj\u00eb regjist\u00ebr i ri (gjendja e DB n\u00eb memory \u00ebsht\u00eb identike me snapshot-in + regjistrin e grumbulluar t\u00eb ndryshimeve). <\/p>\n
Ve\u00e7orit\u00eb e rqlite: <\/p>\n
\n
Thjesht\u00ebsia e vendosjes s\u00eb klasterit, pa nevoj\u00ebn p\u00ebr nj\u00eb instalim t\u00eb ve\u00e7ant\u00eb t\u00eb SQLite.\n
Mund\u00ebsia p\u00ebr t\u00eb marr\u00eb shpejt nj\u00eb ruajtje SQL t\u00eb replikuar.\n
Gati p\u00ebr t'u p\u00ebrdorur n\u00eb projekte punuese (Production-grade).\n
Disponibiliteti i API HTTP(S), i cili lejon p\u00ebrdit\u00ebsimin e t\u00eb dh\u00ebnave n\u00eb mod\u00eb grumbullore dhe p\u00ebrcaktimin e nyj\u00ebs udh\u00ebheq\u00ebse t\u00eb klasterit. Gjithashtu ofrohet nj\u00eb nd\u00ebrfaqe e linj\u00ebs s\u00eb komandave dhe mund\u00ebsia e p\u00ebrdorimit t\u00eb bibliotekave t\u00eb ndryshme klienti t\u00eb krijuara p\u00ebr SQLite.\n
Prania e nj\u00eb sh\u00ebrbimi p\u00ebr p\u00ebrcaktimin e nyjave t\u00eb tjera, duke lejuar krijimin dinamik t\u00eb klastereve.\n
Mb\u00ebshtetje p\u00ebr enkriptimin e shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave nd\u00ebrmjet nyjave.\n
Mund\u00ebsia p\u00ebr t\u00eb konfiguruar nivelin e verifikimit t\u00eb vlefshm\u00ebris\u00eb dhe koherenc\u00ebs s\u00eb t\u00eb dh\u00ebnave gjat\u00eb leximet.\n
Mund\u00ebsi opsionale p\u00ebr t\u00eb lidhur nyjat n\u00eb m\u00ebnyr\u00eb vet\u00ebm p\u00ebr lexim, q\u00eb nuk marrin pjes\u00eb n\u00eb p\u00ebrcaktimin e konsensusit dhe p\u00ebrdoren p\u00ebr t\u00eb rritur shkall\u00ebzimin e klasterit p\u00ebr operacione lexim.\n
Mb\u00ebshtetje p\u00ebr nj\u00eb form\u00eb t\u00eb vetme transaksionesh bazuar n\u00eb bashkimin e komandave n\u00eb nj\u00eb k\u00ebrkes\u00eb (transaksionet bazuar n\u00eb BEGIN, COMMIT, ROLLBACK, SAVEPOINT dhe RELEASE nuk mb\u00ebshteten).\n
Mb\u00ebshtetje p\u00ebr krijimin e kopjeve rezerv\u00eb t\u00eb nxehta. <\/ul>\n
N\u00eb versionin e ri jan\u00eb b\u00ebr\u00eb ndryshime t\u00eb r\u00ebnd\u00ebsishme arkitektonike, t\u00eb cilat synojn\u00eb t\u00eb rrisin besueshm\u00ebrin\u00eb e klasterit p\u00ebrmes p\u00ebrmir\u00ebsimit t\u00eb procesit t\u00eb drejtimit t\u00eb k\u00ebrkesave p\u00ebr leximin dhe shkrimin n\u00eb nyjat e duhur t\u00eb klasterit. Nyjat rqlite tani mund t\u00eb shum\u00ebfishojn\u00eb midis tyre disa lidhje logjike, duke p\u00ebrdorur lidhje TCP q\u00eb jan\u00eb vendosur midis nyjave nga protokolli Raft. N\u00ebse nj\u00eb k\u00ebrkes\u00eb k\u00ebrkon autorizimin e nyj\u00ebs udh\u00ebheq\u00ebse, por \u00ebsht\u00eb d\u00ebrguar n\u00eb nj\u00eb nyj\u00eb ndihm\u00ebse, nyja ndihm\u00ebse mund t\u00eb p\u00ebrcaktoj\u00eb adres\u00ebn e liderit dhe t'ia transmetoj\u00eb klientit, pa kryer llogaritjen e konsensusit sipas protokollit Raft. <\/p>\n
Ndryshimi gjithashtu leht\u00ebsoi heqjen e komponentit t\u00eb ve\u00e7ant\u00eb p\u00ebr sinkronizimin e metadatan\u00ebve dhe p\u00ebrjashtoi trajtimin e ve\u00e7ant\u00eb t\u00eb gjendjes Raft dhe metadatan\u00ebve. Nyjet sekondare tani i drejtojn\u00eb k\u00ebrkesat tek nyja lider vet\u00ebm kur \u00ebsht\u00eb e nevojshme, kur nevojitet t\u00eb dihet adresa e nyj\u00ebs udh\u00ebheq\u00ebse. N\u00eb API \u00ebsht\u00eb ofruar mund\u00ebsia p\u00ebr t\u00eb marr\u00eb informacion mbi gjendjen e nyjeve t\u00eb tjera n\u00eb klaster. N\u00eb nd\u00ebrfaqen e komand\u00ebs \u00ebsht\u00eb shtuar komanda \u00ab.sysdump\u00bb. \n Burimi: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"