search for: tiering

...or archival applications, this migration is not helpful since the file is likely to not be accessed again just after being copied on, and it will later just migrate back to the cold tier. Sharding should be, and needs to be used with very large archive files because of bug: Bug 1277112 - Data Tiering:File create and new writes to existing file fails when the hot tier is full instead of redirecting/flushing the data to cold tier which sharding with tiering helps mitigate. This problem occurs in GlusterFS 3.7.18 and 3.12.3, at least. I/O size doesn't make any difference, I tried mul...

All, I am new to gluster and have some questions/concerns about some tiering errors that I see in the log files. OS: CentOs 7.3.1611 Gluster version: 3.10.5 Samba version: 4.6.2 I see the following (scrubbed): Node 1 /var/log/glusterfs/tier/<vol>/tierd.log: [2017-10-19 17:52:07.519614] I [MSGID: 109038] [tier.c:1169:tier_migrate_using_query_file] 0-<vol>-tie...

...lp, instead of going to > and fro with questions. > > -- > Milind > > > > On Fri, Oct 20, 2017 at 12:42 AM, Herb Burnswell < > herbert.burnswell at gmail.com> wrote: > >> All, >> >> I am new to gluster and have some questions/concerns about some tiering >> errors that I see in the log files. >> >> OS: CentOs 7.3.1611 >> Gluster version: 3.10.5 >> Samba version: 4.6.2 >> >> I see the following (scrubbed): >> >> Node 1 /var/log/glusterfs/tier/<vol>/tierd.log: >> >> [2017-10-19 1...

...22fb) If possible, a *gluster volume info* would also help, instead of going to and fro with questions. -- Milind On Fri, Oct 20, 2017 at 12:42 AM, Herb Burnswell < herbert.burnswell at gmail.com> wrote: > All, > > I am new to gluster and have some questions/concerns about some tiering > errors that I see in the log files. > > OS: CentOs 7.3.1611 > Gluster version: 3.10.5 > Samba version: 4.6.2 > > I see the following (scrubbed): > > Node 1 /var/log/glusterfs/tier/<vol>/tierd.log: > > [2017-10-19 17:52:07.519614] I [MSGID: 109038] > [tier...

...ying to weed out issues here. So, I can see quota turned *on* and would like you to check the quota settings and test to see system behavior *if quota is turned off*. Although the file size that failed migration was 29K, I'm being a bit paranoid while weeding out issues. Are you still facing tiering errors ? I can see your response to Alex with the disk space consumption and found it a bit ambiguous w.r.t. state of affairs. -- Milind On Tue, Oct 24, 2017 at 11:34 PM, Herb Burnswell < herbert.burnswell at gmail.com> wrote: > Milind - Thank you for the response.. > > >>...

Hi, Have a glusterfs 3.10.10 (tried 3.12.6 as well) volume on Ubuntu 16.04 with a 3 ssd tier where one ssd is bad. Status of volume: labgreenbin Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Hot Bricks: Brick labgfs81:/gfs/p1-tier/mount 49156 0 Y 4217 Brick

...lp, instead of going to > and fro with questions. > > -- > Milind > > > > On Fri, Oct 20, 2017 at 12:42 AM, Herb Burnswell < > herbert.burnswell at gmail.com> wrote: > >> All, >> >> I am new to gluster and have some questions/concerns about some tiering >> errors that I see in the log files. >> >> OS: CentOs 7.3.1611 >> Gluster version: 3.10.5 >> Samba version: 4.6.2 >> >> I see the following (scrubbed): >> >> Node 1 /var/log/glusterfs/tier/<vol>/tierd.log: >> >> [2017-10-19 1...

Hi Guys Got a quick question regarding hot tier and cold tier. I got a gluster volume with 1 x 3 hot tier and 1 x 3 cold tier. watermark-low is 75 and watermark-hi is 90. usage of volume is very less. My files always go to hot tier and cold tier at same time As I understand, data should go to hot tier only until demoted. Could someone please shed some light into this? Thanks in advance. --

Hi, I'm looking to use sharding on tiered volume. This is very attractive feature that could benefit tiered volume to let it handle larger files without hitting the "out of (hot)space problem". I decided to set test configuration on GlusterFS 3.12.3 when tiered volume has 2TB cold and 1GB hot segments. Shard size is set to be 16MB. For testing 100GB files are used. It seems writes

...have features.shard-block-size: 16MB and cluster.tier-demote-frequency: 150 What are you using for the hot tier that has only 1GB, some sort of RAM disk or battery back flash or something? With that small of a hot tier you may run into some strange performance characteristics, AFAIK the current tiering implementation uses rebalance to move files between tiers when the tier demote freq times out. You may end up spending alot of time waiting for your hot files to rebalance to the cold tier since its out of space, you will also probably have other files being written to the cold tier with the hot t...

Hi, The actual data will be in the hot tier only till demotion. The file that you see on the cold tier is just a linkto file of the file on the hot tier. These linkto file are necessary for the internal working of the tier. On Mon, Mar 5, 2018 at 1:16 PM, Sherin George <allmyforums at outlook.in> wrote: > Hi Guys > > Got a quick question regarding hot tier and cold tier. > I

I've recently enabled an SSD backed 2 TB hot tier on my 150 TB 2 server / 3 bricks per server distributed replicated volume. I'm seeing IO get blocked across all client FUSE threads for 10 to 15 seconds while the promotion daemon runs. I see the 'glustertierpro' thread jump to 99% CPU usage on both boxes when these delays occur and they happen every 25 minutes (my

Does anyone have any suggestions about how to deal with multiple environments/tiers? For instance, we have several environments ( production, dev, qa, etc.. ) and within each environment, different tiers ( web, data, app, etc ). Each tier is a different IP network segment, so all the hosts in each tier have different configurations for certain things like resolv.conf, ntp.conf and so on. We do

Hi, There isn't a way to replace the failing tier brick through a single command as we don't have support for replace/ remove or add brick with tier. Once you bring the brick online(volume start force), the data in the brick will be built by the self heal daemon (Done because its a replicated tier). But adding brick will still not work. Else if you use the force option, it will work as

Hi Tom, The volume info doesn't show the hot bricks. I think you have took the volume info output before attaching the hot tier. Can you send the volume info of the current setup where you see this issue. The logs you sent are from a later point in time. The issue is hit earlier than the logs what is available in the log. I need the logs from an earlier time. And along with the entire tier

Thanks for the info, Hari. Sorry about the bad gluster volume info, I grabbed that from a file not realizing it was out of date. Here's a current configuration showing the active hot tier: [root at pod-sjc1-gluster1 ~]# gluster volume info Volume Name: gv0 Type: Tier Volume ID: d490a9ec-f9c8-4f10-a7f3-e1b6d3ced196 Status: Started Snapshot Count: 13 Number of Bricks: 8 Transport-type: tcp Hot

Hi, Can you send the volume info, and volume status output and the tier logs. And I need to know the size of the files that are being stored. On Tue, Jan 9, 2018 at 9:51 PM, Tom Fite <tomfite at gmail.com> wrote: > I've recently enabled an SSD backed 2 TB hot tier on my 150 TB 2 server / 3 > bricks per server distributed replicated volume. > > I'm seeing IO get blocked

Hi Everyone, I''m working at getting Rails introduced in my company. We''re a J2EE shop. Our deployments make use of thee-tiered architecture, just to be clear, that means that there are essentially three machines involved in dealing out an app: a webserver, an application server, and a database server. As I see it (unless I''ve missed something) Ruby is essentially

...ausing this, and what a fix or work-around might be? Thanks! ~ Jeff Byers ~ Tiered volume performance degrades badly after a volume stop/start or system restart. The degradation is very significant, making the performance of an SSD hot tiered volume a fraction of what it was with the HDD before tiering. Stopping and starting the tiered volume causes the problem to exhibit. Stopping and starting the Gluster services also does. Nothing in the tier is being promoted or demoted, the volume starts empty, a file is written, then read, then deleted. The file(s) only ever exist on the hot tier. This a...

The sizes of the files are extremely varied, there are millions of small (<1 MB) files and thousands of files larger than 1 GB. Attached is the tier log for gluster1 and gluster2. These are full of "demotion failed" messages, which is also shown in the status: [root at pod-sjc1-gluster1 gv0]# gluster volume tier gv0 status Node Promoted files Demoted files