summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* posix: fix io_uring crash in reconfigure (#1804)Ravishankar N2020-11-172-1/+24
| | | | | | | | | Call posix_io_uring_fini only if it was inited to begin with. Fixes: #1794 Reported-by: Mohit Agrawal <moagrawa@redhat.com> Signed-off-by: Ravishankar N <ravishankar@redhat.com> Change-Id: I0e840b6b1d1f26b104b30c8c4b88c14ce4aaac0d
* afr: call afr_is_lock_mode_mandatory only while xdata is valid (#1797)mohit842020-11-171-9/+9
| | | | | | | | | afr_is_lock_mode_mandatory throws a warning message while xdata is not valid, to avoid a message call a function only while xdata is valid. Fixes: #1796 Change-Id: I32d37960ea4e936ba87e65811c1792a2f1158c0d Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* glusterd: resource leaks (#1748)Nikhil Ladha2020-11-122-37/+29
| | | | | | | | | | | | | | | Issue: iobref was not freed before exiting the function if all the checks were OK, which caused the resource leak. Fix: Modified the code a bit to avoid use of an extra reference to the label, and to free the iobref and iobuf if not NULL, and then exit the function. CID: 1430118 Updates: #1060
* ganesha-ha: revised regex exprs for --statusKaleb S. KEITHLEY2020-11-101-4/+4
| | | | | | | | | | better whitespace in regex This has worked for years, but somehow no longer works on rhel8 Updates: #1000 Change-Id: I2c1a3537573d125608334772ba1a263c55407dd4 Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
* posix: Attach a posix_spawn_disk_thread with glusterfs_ctx (#1595)mohit842020-11-098-67/+158
| | | | | | | | | | | | | Currently posix xlator spawns posix_disk_space_threads per brick and in case of brick_mux environment while glusterd attached bricks at maximum level(250) with a single brick process in that case 250 threads are spawned for all bricks and brick process memory size also increased. Solution: Attach a posix_disk_space thread with glusterfs_ctx to spawn a thread per process basis instead of spawning a per brick Fixes: #1482 Change-Id: I8dd88f252a950495b71742e2a7588bd5bb019ec7 Signed-off-by: Mohit Agrawal moagrawa@redhat.com
* Modify templet to file an issue on gluster (#1759)Ashish Pandey2020-11-091-6/+12
| | | | | | | | Add more sections to get more information from user to avoid back and forth queries. This will help community to provide faster resolution. Change-Id: I88be0214cea7cfa979bedb4aab7c312e0ff8d5f3 Updates: #1743
* logger: Always print errors in english (#1657)Rinku Kothiya2020-11-071-1/+5
| | | | | | fixes: #1302 Change-Id: If0e21f016155276a953c64a8dd13ff3eb281d09d Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>
* tests: Fix issues in CentOS 8 (#1756)Xavi Hernandez2020-11-062-6/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * tests: Fix issues in CentOS 8 Due to some configuration changes in CentOS 8/RHEL 8, ssl-ciphers.t and bug-1053579.t were failing. The first one was failing because TLS v1.0 is disabled by default. The test hash been updated to check that at least one of TLS v1.0, v1.1 or v1.2 succeeds. For the second case, the issue is that the test assumed that the latest added group to a user should always be listed the last, but this is not always true because nsswitch.conf now uses 'sss' before 'files', which means that data comes from a db that could not be sorted. Updates: #1009 Change-Id: I4ca01a099854ec25926c3d76b3a98072175bab06 Signed-off-by: Xavi Hernandez <xhernandez@redhat.com> * tests: Fix TLS version detection The old test didn't correctly determine which version of TLS should be allowed by openssl. Change-Id: Ic081c329d5ed1842fa9f5fd23742ae007738aec0 Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
* glusterd: fix bug in enabling granular-entry-heal (#1752)Ravishankar N2020-11-053-7/+23
| | | | | | | | | | | | | | commit f5e1eb87d4af44be3b317b7f99ab88f89c2f0b1a meant to enable the volume option only for replica volumes but inadvertently enabled it for all volume types. Fixing it now. Also found a bug in glusterd where disabling the option on plain distribute was succeeding even though setting it in the fist place fails. Fixed that too. Fixes: #1483 Change-Id: Icb6c169a8eec44cc4fb4dd636405d3b3485e91b4 Reported-by: Sheetal Pamecha <spamecha@redhat.com> Signed-off-by: Ravishankar N <ravishankar@redhat.com>
* CLI: added an error message in case of timeoutnik-redhat2020-11-051-1/+4
| | | | | | | | | Added an error message in CLI when there are volumes present in cluster but timeout happens on fetching them. This PR fixes #1738 Signed-off-by: nik-redhat <nladha@redhat.com>
* api: conscious language changes (#1737)Ravishankar N2020-11-044-56/+57
| | | | | | | | | -Removed the occurences of 'master' in api. -Some changes threw up clang-format errors, so fixed them as well. -Renamed api/src/{glfs-master.c => glfs-primary.c} Fixes: #1733 Change-Id: I57aea9d93e219305e87985bc2f81ac47cdebb72f Signed-off-by: Ravishankar N <ravishankar@redhat.com>
* posix: Use CALLOC instead of alloca to allocate memory for xattrs list (#1730)mohit842020-11-043-5/+15
| | | | | | | | | | | In case of file is having huge xattrs on backend a brick process is crashed while alloca(size) limit has been crossed 256k because iot_worker stack size is 256k. Use MALLOC to allocate memory instead of using alloca Fixes: #1699 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com> Change-Id: I100468234f83329a7d65b43cbe4e10450c1ccecd
* gfapi: give appropriate error when size exceedsRinku Kothiya2020-11-031-0/+8
| | | | | | | | | | | | This patch help generate appropriate error message when the gfapi tries to write data equal to or greater than 1 Gb due to the limitation at the socket layer. fixes: #1518 Change-Id: I1234a0b5a6e675a0b20c6b1afe0f4390fd721f6f Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>
* write-behind: Implement 'pass-through' optionXavi Hernandez2020-11-033-1/+27
| | | | | | | | | | | | | | | The pass-through option was implemented for all performance xlators in commit 549b547, but write-behind was missed. This patch implements the functionality for write-behind. Given that it's not safe to enable or disable this option while the volume is mounted, it cannot be reconfigured online. A change will only take effect after a remount. Fixes: #1565 Change-Id: I189a48e0044b292e1d6c3b77751ff25045531883 Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
* xlators: misc conscious language changes (#1715)Ravishankar N2020-11-0221-71/+69
| | | | | | | | | | | | core:change xlator_t->ctx->master to xlator_t->ctx->primary afr: just changed comments. meta: change .meta/master to .meta/primary. Might break scripts. changelog: variable/function name changes only. These are unrelated to geo-rep. Fixes: #1713 Change-Id: I58eb5fcd75d65fc8269633acc41313503dccf5ff Signed-off-by: Ravishankar N <ravishankar@redhat.com>
* cli-rpc: conditional init of global quota rpc (#1578)schaffung2020-11-022-3/+15
| | | | | | | | | | | | | | | | | | | | Issue: It is seem that the initialization of rpc to connect with quotad is done in every glusterfs cli command, irrespective of whether the quota feature is enabled or disabled. This seems to be an overkill. Code change: The file /var/run/quotad/quotad.pid is present signals that quotad is enabled. Hence we can put a conditional check for seeing when this file exists and if it doesn't we just skip over the initialization of the global quotad rpc. This will go on to reduce the extra rpc calls and operations being performed in the kernel space. Fixes: #1577 Change-Id: Icb69d35330f76ce95626f59af75a12726eb620ff Signed-off-by: srijan-sivakumar <ssivakumar@redhat.com> Co-authored-by: srijan-sivakumar <ssivakumar@redhat.com>
* extras/rebalance: Script to perform directory rebalance (#1676)Pranith Kumar Karampuri2020-10-303-0/+362
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * extras/rebalance: Script to perform directory rebalance How should the script be executed? $ /path/to/directory-rebalance.py <dir-to-rebalance> will do rebalance just for that directory. The script assumes that fix-layout operation is completed for all the directories present inside the <dir-to-rebalance> How does it work? For the given directory path that needs to be rebalanced, full crawl is performed and the files that need to be healed and the size of each file is first written to the index. Once building the index is completed, the index is read and for each file the script executes equivalent of setfattr -n trusted.distribute.migrate-data -v 1 <path/to/file> Why does the script take two passes? Printing a sensible ETA has been a primary goal of the script. Without knowing the approximate size that will be rebalanced, it is difficult to find ETA. Hence the script does one pass to find files, sizes which it writes to the index file and then the next pass is done on the index file. It takes a minute or two for the ETA to converge but in our testing it has been giving a reasonable ETA What versions does the script support? For the script to work correctly, dht should handle "trusted.distribute.migrate-data" setxattr correctly. fixes: #1654 Change-Id: Ie5070127bd45f1a1b9cd18ed029e364420c971c1 Signed-off-by: Pranith Kumar K <pranith.karampuri@phonepe.com>
* DHT - Fixing rebalance failure on issuing stop command (#1628)Barak Sason Rofman2020-10-301-11/+12
| | | | | | | | | | | | | | | | | | Issuing a stop command for an ongoing rebalance process results in an error. This issue was brought up in https://bugzilla.redhat.com/1286171 and a patch (https://review.gluster.org/24103/) was submitted to resolve the issue. However the submitted patch resolved only part of the problem by reducing the number of log messages that were printed (since rebalnace is currently a recursive process, an error message was printed for every directory) but didn't fully resolve the root cause for the failure. This patch fixes the issue by modifying the code-path which handles the termination of the rebalance process by issuing a stop command. fixes: #1627 Change-Id: I604f2b0f8b1ccb1026b8425a14200bbd1dc5bd03 Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>
* glusterd: Resolve coverity bug CID1435891 (#1716)mohit842020-10-301-2/+3
| | | | | | | The PR #1672 has introduced a coverity bug, this fixes it. Change-Id: I1140bf7527b6466f4210809a74dc3e59ecf02b6e Fixes: #1663 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* cluster/dht: Perform migrate-file with lk-owner (#1581)Pranith Kumar Karampuri2020-10-2911-12/+143
| | | | | | | | | | | | | | | | | | | | | | * cluster/dht: Perform migrate-file with lk-owner 1) Added GF_ASSERT() calls in client-xlator to find these issues sooner. 2) Fuse is setting zero-lkowner with len as 8 when the fop doesn't have any lk-owner. Changed this to have len as 0 just as we have in fops triggered from xlators lower to fuse. * syncop: Avoid frame allocation if we can * cluster/dht: Set lkowner in daemon rebalance code path * cluster/afr: Set lkowner for ta-selfheal * cluster/ec: Destroy frame after heal is done * Don't assert for lk-owner in lk call * set lkowner for mandatory lock heal tests fixes: #1529 Change-Id: Ia803db6b00869316893abb1cf435b898eec31228 Signed-off-by: Pranith Kumar K <pranith.karampuri@phonepe.com>
* io-cache: Minor Performance Optimization (#1656)Shree Vatsa N2020-10-281-17/+3
| | | | | | | | move trace logs after mutex unlock in some macros * Also removed unused macros - ioc_page_lock and ioc_page_unlock Fixes: #1653 Signed-off-by: Shreevatsa N <i.mnshreevatsa@gmail.com>
* tests: exclude more contrib/fuse-lib objects (#1694)Dmitry Antipov2020-10-271-0/+3
| | | | | | | Exclude more contrib/fuse-lib objects to avoid silly tests/basic/0symbol-check.t breakage. Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru> Fixes: #1692
* rpcsvc/transport: gracefully disconnect when graph is not ready (#1671)Rafi KC2020-10-272-7/+11
| | | | | | | | | | | | | | | | | * rpcsvc/transport: gracefully disconnect when graph is not ready. There was a crash reported when the brick rpc get's an accept request from a client before the server xlator is fully inited. The fix https://review.gluster.org/22339/ solves the crash, but it leaves the connection alive with out adding the rpc to xprts list of server conf. This will leads to problems with upcall, dump, and other cleanup codes. So this patch will make the rpc to fail and disconnect if a connection attempted before the server is fully inited. Change-Id: I3bf1113c0da4c2614afaa2c0f4eb6abfb0d26ed0 Signed-off-by: Mohammed Rafi KC <rafi.kavungal@iternity.com>
* tests: ./tests/bugs/core/bug-1650403.t is getting timed out (#1672)mohit842020-10-2712-15/+112
| | | | | | | | | | | | | | | | | | | | | | The test case ./tests/bugs/core/bug-1650403.t is consuming more than 500s while running a regression job so the regression is failing. After executed the test case in softserve environment i have found it is getting timed-out because DNS call is consuming time by glusterd while it is trying to disbale/enable shd. time ./tests/bugs/core/bug-1650403.t real 20m52.952s user 0m20.842s sys 0m9.824s After save the local IP address into glusterd_conf_t list test case time is reduced time ./tests/bugs/core/bug-1650403.t real 1m29.467s user 0m23.366s sys 0m10.395s Fixes: #1663 Change-Id: Iee3462075f84897faa294e48d81af9761929613a Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* nfs: Fix inconsistency between glibc and libtirpc (#1698)Xavi Hernandez2020-10-245-18/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * nfs: Fix inconsistency between glibc and libtirpc There's a critical difference between RPC implementation in glibc and libtirpc. In libtirpc, svc_run() starts a polling loop that listens from all registered connections and handles requests. When this is done from multiple threads, a race can happen where both threads are trying to process the same connection simultaneously. This causes memory corruption. However, in glibc, svc_run() only handles the registered connections on the current thread, so it's necessary to call svc_run() on all threads that register services. This patch fixes that problem by calling svc_run() from all threads only if libtirpc is not used. Otherwise it's called only once. Change-Id: I97c3c39a9aad90115e7e23c70884a4ee7769a2dd Updates: #1009 Signed-off-by: Xavi Hernandez <xhernandez@redhat.com> * nfs: Use an atomic instead of a mutex Instead of using a mutex to synchronize the call to svc_run(), we use an atomic operation to update the flag. Change-Id: I401481d1d0308a557271f99a32527a2ab3c4542f Signed-off-by: Xavi Hernandez <xhernandez@redhat.com> * nfs: Align fields of struct nfs_state Change-Id: Ib0da4911533ffd9c08636457b664eaa45172e975 Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
* posix: add io_uring supportRavishankar N2020-10-2311-5/+744
| | | | | | | | | | | | | | | | | This patch adds support for reads, writes and fsyncs using io-uring in posix xlator. A volume option 'storage.linux-io_uring' is introduced to turn it on or off. When I ran tests with fio and iozone on physical machines on a 2x3 volume + single client, the numbers were not any worse than regular pwrite/pread syscalls which posix does with default volume configurations. But given that io_uring itself undergoing rapid improvement and bug fixes,it is good to have an intial working implementation in gluster and iteratively develop on top of it. Updates: #1398 Change-Id: Ia47456ebb4c16a3b66ad9beb6a9043cc090fed2b Signed-off-by: Ravishankar N <ravishankar@redhat.com>
* glusterd/afr: enable granular-entry-heal by default (#1621)Ravishankar N2020-10-2217-23/+555
| | | | | | | | | | | | | | | | | | | | | | | | | 1. The option has been enabled and tested for quite some time now in RHHI-V downstream and I think it is safe to make it 'on' by default. Since it is not possible to simply change it from 'off' to 'on' without breaking rolling upgrades, old clients etc., I have made it default only for new volumes starting from op-verison GD_OP_VERSION_9_0. Note: If you do a volume reset, the option will be turned back off. This is okay as the dir's gfid will be captured in 'xattrop' folder and heals will proceed. There might be stale entries inside entry-changes' folder, which will be removed when we enable the option again. 2. I encountered a cust. issue where entry heal was pending on a dir. with 236436 files in it and the glustershd.log output was just stuck at "performing entry selfheal", so I have added logs to give us more info in DEBUG level about whether entry heal and data heal are progressing (metadata heal doesn't take much time). That way, we have a quick visual indication to say things are not 'stuck' if we briefly enable debug logs, instead of taking statedumps or checking profile info etc. Fixes: #1483 Change-Id: I4f116f8c92f8cd33f209b758ff14f3c7e1981422 Signed-off-by: Ravishankar N <ravishankar@redhat.com>
* glusterd: brick sock file deleted, log error (#1560)schaffung2020-10-221-2/+25
| | | | | | | | | | | | | | | | | | Issue: The satus of the brick as tracked by glusterd is stopped if the socket file corresponding to a running brick process is absent in /var/run/gluster. The glusterd keeps on trying to reconnect ( rpc layer ) but it fails. Code change: Rather than registering the rpc connection with the help of the given sockfilepath which is not even present as it keeps on reconnecting, why not log this as an error and not try to reconnect using the non-existing sock file path. Fixes: #1526 Change-Id: I6c81691ab1624c66dec74f5ffcc6c383201ac757 Signed-off-by: srijan-sivakumar <ssivakumar@redhat.com> Co-authored-by: srijan-sivakumar <ssivakumar@redhat.com>
* trash: Create inode_table only while feature is enabled (#1626)mohit842020-10-221-3/+44
| | | | | | | | | | | | | | Currently trash xlator create a inode table(1M) even if feature is not enabled.In brick_mux environment while 250 bricks are attached with a single brick process and feature is not enable brick process increase RSS size unnecessarily. Solution: Create inode_table only while a feature is enabled. The patch reduces 250M RSS size per brick process if trash feature is not enabled. Change-Id: I11a6fd2b8419fe2988f398be6ec30fb4f3b99a5d Fixes: #1543 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* afr: fixing null dereference reported by coverity (#1570)Tamar Shacked2020-10-221-1/+1
| | | | | | | Added a null check to avoid a null pointer dereference CID: 1433222 Updates: #1060 Signed-off-by: Tamar Shacked <tshacked@redhat.com>
* geo-rep: Enable rsync verbose logging for debugging (#1588)Kotresh HR2020-10-211-1/+10
| | | | | | | | | | | | By default rsync command is run without --verbose argument. The rsync command takes "--verbose" or "-vv" which prints verbal output which helps in debugging rsync errors. The verbose argument can be passed by setting geo-rep config option "rsync_options" to required verbose string. If set, this patch logs rsync verbose output in the geo-rep log file. Fixes: #1587 Change-Id: I0b7e1e813eb7e90f1c2ba885b42fd52dbd44386a Signed-off-by: Kotresh HR <khiremat@redhat.com>
* libglusterfs/coverity: pointer to local outside the scope (#1675)Vinayak hariharmath2020-10-213-7/+12
| | | | | | | | | | | | | | issue: gf_store_read_and_tokenize() returns the address of the locally referred string. fix: pass the buf to gf_store_read_and_tokenize() and use it for tokenize. CID: 1430143 Updates: #1060 Change-Id: Ifc346540c263f58f4014ba2ba8c1d491c20ac609 Signed-off-by: Vinayakswami Hariharmath <vharihar@redhat.com>
* glusterd: wrong comparison in glusterd_brick_start() function (#1665)mohit842020-10-211-2/+2
| | | | | | | | Call gf_uuid_compare in glusterd_brick_start to compare two uuid instead of calling strncmp. Fixes: #1659 Change-Id: Icd1bdcc1ed4dfab4407fc51ae4ba248989a32f17 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* dht/rebalance - fixed dhtfcnt_thread wakeup time to be in absolute time (#1667)Tamar Shacked2020-10-211-1/+1
| | | | | | | | | | | The dhtfcnt_thread is designed to wakeup each 10min. Changed the time units passed to pthread_cond_timedwait() to be in absolute time (epoch time) todo: verify the values of total_file_size updates: #1507 Change-Id: I1a81ff23ff2c313463add9e0a5fc05c84ac1b4a5 Signed-off-by: Tamar Shacked <tshacked@redhat.com>
* Maintainers List Update : Management daemon. (#1633)schaffung2020-10-201-0/+1
| | | | | | | | Hello Maintainers, requesting permission to be a peer in the management daemon component. I believe I can actively help in the maintenance as well as the enhancement of the component. Updates: #1584 Signed-off-by: srijan-sivakumar <ssivakum@redhat.com>
* Update maintainers list of geo-rep and glusterfind (#1629)Shwetha Acharya2020-10-191-0/+2
| | | | | Change-Id: I6afd762ca9d9a7f6d2fb83256cb6edffb37b67a3 Updates: #1584 Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>
* test: The test case tests/bugs/bug-1064147.t is failing (#1662)mohit842020-10-191-0/+3
| | | | | | | | | | | | The test case tests/bugs/bug-1064147.t is failing at the time of comparing root permission with permission changed while one of the brick was down.The permission was not matching because layout was not existing on root at the time of healing a permission, so correct permission was not healed on newly started brick Fixes: #1661 Change-Id: If63ea47576dd14f4b91681dd390e2f84f8b6ac18 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* tests/00-geo-rep: 00-georep-verify-non-root-setup.t fails on devel branch ↵Shwetha Acharya2020-10-151-1/+1
| | | | | | | | | | (#1639) Increasing the timeout value to overcome the encountered delay in execution of test Change-Id: Id40d92366738439634a6b06d447a43a2c6cdbf44 Updates: #1594 Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>
* io-stats: Configure ios_sample_buf_size based on sample_interval value (#1574)mohit842020-10-152-8/+26
| | | | | | | | | | | io-stats xlator declares a ios_sample_buf_size 64k object(10M) per xlator but in case of sample_interval is 0 this big buffer is not required so declare the default value only while sample_interval is not 0.The new change would be helpful to reduce RSS size for a brick and shd process while the number of volumes are huge. Change-Id: I3e82cca92e40549355edfac32580169f3ce51af8 Fixes: #1542 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* glusterd: Resolve clang format issue (#1622)mohit842020-10-131-10/+10
| | | | | | | | | In the commit 8d54899724a31f29848e1461f68ce2cf40585056 clang format issue was introduced in patch but clang check was not complained at the time of running regression. Fixes: #1569 Change-Id: Ib1fb039ebe3c77f39b8c686eb4699327256ac494 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* tests/00-geo-rep: 00-georep-verify-non-root-setup.t fails on devel branch ↵Shwetha Acharya2020-10-131-0/+4
| | | | | | | | | | | | | | (#1617) ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem -p 22 nroot@127.0.0.1 /build/install/sbin/gluster --xml --remote-host=localhost volume info slave failes with error 255. Adding ssh key clean up code at the beginning of the test, inorder to clean any stale entries Updates: #1594 Signed-off-by: Shwetha K Acharya <sacharya@redhat.com>
* MAINTAINERS: update Amar's contact (#1598)Amar Tumballi2020-10-121-5/+5
| | | | | | | * Also add Deepshika to Platform section! Updates: #1584 Change-Id: I9846fb1a16ad536e0a23d606d308a61e2ff60b54 Signed-off-by: Amar Tumballi <amar@kadalu.io>
* core: configure optimum inode table hash_size for shd (#1576)mohit842020-10-1112-35/+65
| | | | | | | | | | | | | | | | | | | | | In brick_mux environment a shd process consume high memory. After print the statedump i have found it allocates 1M per afr xlator for all bricks.In case of configure 4k volumes it consumes almost total 6G RSS size in which 4G consumes by inode_tables [cluster/replicate.test1-replicate-0 - usage-type gf_common_mt_list_head memusage] size=1273488 num_allocs=2 max_size=1273488 max_num_allocs=2 total_allocs=2 inode_new_table function allocates memory(1M) for a list of inode and dentry hash. For shd lru_limit size is 1 so we don't need to create a big hash table so to reduce RSS size for shd process pass optimum bucket count at the time of creating inode_table. Change-Id: I039716d42321a232fdee1ee8fd50295e638715bb Fixes: #1538 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* configure.ac: Add --enable-brickmux (#1572)mohit842020-10-092-0/+18
| | | | | | | | Introduce an --enable-brickmux configure option to enable brick_mux as a default option. Fixes: gluster#1569 Change-Id: Id0c61ee3500630889e2cb2b5816cd40f68d47c94 Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
* MAINTAINERS: Updated Email address (#1567)Aravinda Vishwanathapura2020-10-091-6/+6
| | | | Change-Id: I867809cc2015869e480389caef22695862ccda9a Signed-off-by: Aravinda Vishwanathapura <aravinda@kadalu.io>
* rfc.sh: Handle remote-repo with .git extension (#1586)Pranith Kumar Karampuri2020-10-091-1/+1
| | | | | fixes: #1582 Change-Id: I8ad01b05f3d4befb1b502e853b4d4ee1ea8d038c Signed-off-by: Pranith Kumar K <pranith.karampuri@phonepe.com>
* Update maintainer list of EC (#1585)Sheetal Pamecha2020-10-091-0/+1
| | | | | Change-Id: I40caa4b7355c4b48ef18c45e46f5dbecb7ae538a Updates: #1584 Signed-off-by: Sheetal <spamecha@redhat.com>
* Update maintainer list of DHT (#1551)Barak Sason Rofman2020-10-091-1/+5
| | | | | | | Update maintainers list to reflect current status of DHT. fixes: #1550 Change-Id: Ie5ddd0255a53da1ac2b4dd1b210d69e78ca6c85a Signed-off-by: Barak Sason Rofman <bsasonro@redhat.com>
* rfc.sh: make proper changes to work on github (#1547)Amar Tumballi2020-10-071-9/+14
| | | | | Change-Id: Ie02ae47c766f2caaece827f0d98862f2f4589c9c Updates: #1000 Signed-off-by: Amar Tumballi <amar@kadalu.io>
* Contributing: update about who can trigger the buildAmar Tumballi2020-10-071-3/+4
| | | | | | | | | Currently only maintainers listed in github group can trigger the regression runs, it may change in future! Updates: #1000 Change-Id: I3b5f1cace8a433886d725539198998875dcdce36 Signed-off-by: Amar Tumballi <amar@kadalu.io>
generated by cgit (git 2.34.1) at 2025-08-31 06:04:13 +0000