search for: nexus2

...turn, glusterfsd uses up tons of CPU (I saw it spike to 600%). gluster already has massive performance issues for me, but healing after a 4-hour downtime is on another level of bad perf. For example, this command took many minutes to run: gluster volume heal androidpolice_data3 info summary Brick nexus2:/mnt/nexus2_block4/androidpolice_data3 Status: Connected Total Number of entries: 91 Number of entries in heal pending: 90 Number of entries in split-brain: 0 Number of entries possibly healing: 1 Brick forge:/mnt/forge_block4/androidpolice_data3 Status: Connected Total Number of entries: 87 Numbe...

...U (I saw it spike to 600%). gluster already has massive performance > issues for me, but healing after a 4-hour downtime is on another level > of bad perf. > > For example, this command took many minutes to run: > > gluster volume heal androidpolice_data3 info summary > Brick nexus2:/mnt/nexus2_block4/androidpolice_data3 > Status: Connected > Total Number of entries: 91 > Number of entries in heal pending: 90 > Number of entries in split-brain: 0 > Number of entries possibly healing: 1 > > Brick forge:/mnt/forge_block4/androidpolice_data3 > Status: Conn...

...CPU (I > saw it spike to 600%). gluster already has massive performance issues for > me, but healing after a 4-hour downtime is on another level of bad perf. > > For example, this command took many minutes to run: > > gluster volume heal androidpolice_data3 info summary > Brick nexus2:/mnt/nexus2_block4/androidpolice_data3 > Status: Connected > Total Number of entries: 91 > Number of entries in heal pending: 90 > Number of entries in split-brain: 0 > Number of entries possibly healing: 1 > > Brick forge:/mnt/forge_block4/androidpolice_data3 > Status: Conn...

...> Volume Name: apkmirror_data1 >>> Type: Replicate >>> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >>> Status: Started >>> Snapshot Count: 0 >>> Number of Bricks: 1 x 4 = 4 >>> Transport-type: tcp >>> Bricks: >>> Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 >>> Brick2: forge:/mnt/forge_block1/apkmirror_data1 >>> Brick3: hive:/mnt/hive_block1/apkmirror_data1 >>> Brick4: citadel:/mnt/citadel_block1/apkmirror_data1 >>> Options Reconfigured: >>> cluster.quorum-count: 1 >&gt...

...1 >>>> Type: Replicate >>>> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >>>> Status: Started >>>> Snapshot Count: 0 >>>> Number of Bricks: 1 x 4 = 4 >>>> Transport-type: tcp >>>> Bricks: >>>> Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 >>>> Brick2: forge:/mnt/forge_block1/apkmirror_data1 >>>> Brick3: hive:/mnt/hive_block1/apkmirror_data1 >>>> Brick4: citadel:/mnt/citadel_block1/apkmirror_data1 >>>> Options Reconfigured: >>>> cluster.quo...

...gh it didn't seem to make any difference performance-wise before I applied the customizations vs after. Volume Name: apkmirror_data1 Type: Replicate Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e Status: Started Snapshot Count: 0 Number of Bricks: 1 x 4 = 4 Transport-type: tcp Bricks: Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 Brick2: forge:/mnt/forge_block1/apkmirror_data1 Brick3: hive:/mnt/hive_block1/apkmirror_data1 Brick4: citadel:/mnt/citadel_block1/apkmirror_data1 Options Reconfigured: cluster.quorum-count: 1 cluster.quorum-type: fixed network.ping-timeout: 5 network.remote-dio: e...

...ormance-wise before I applied the customizations vs after. > > Volume Name: apkmirror_data1 > Type: Replicate > Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 4 = 4 > Transport-type: tcp > Bricks: > Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 > Brick2: forge:/mnt/forge_block1/apkmirror_data1 > Brick3: hive:/mnt/hive_block1/apkmirror_data1 > Brick4: citadel:/mnt/citadel_block1/apkmirror_data1 > Options Reconfigured: > cluster.quorum-count: 1 > cluster.quorum-type: fixed > network.pi...

...to 600%). gluster already has massive performance issues for >> me, but healing after a 4-hour downtime is on another level of bad perf. >> >> For example, this command took many minutes to run: >> >> gluster volume heal androidpolice_data3 info summary >> Brick nexus2:/mnt/nexus2_block4/androidpolice_data3 >> Status: Connected >> Total Number of entries: 91 >> Number of entries in heal pending: 90 >> Number of entries in split-brain: 0 >> Number of entries possibly healing: 1 >> >> Brick forge:/mnt/forge_block4/androidpo...

...s >> massive performance issues for me, but healing after a 4-hour >> downtime is on another level of bad perf. >> >> For example, this command took many minutes to run: >> >> gluster volume heal androidpolice_data3 info summary >> Brick nexus2:/mnt/nexus2_block4/androidpolice_data3 >> Status: Connected >> Total Number of entries: 91 >> Number of entries in heal pending: 90 >> Number of entries in split-brain: 0 >> Number of entries possibly healing: 1 >> >> Brick forge:/mn...

Hi, I'm trying to squeeze performance out of gluster on 4 80GB RAM 20-CPU machines where Gluster runs on attached block storage (Linode) in (4 replicate bricks), and so far everything I tried results in sub-optimal performance. There are many files - mostly images, several million - and many operations take minutes, copying multiple files (even if they're small) suddenly freezes up for

...dy has massive performance issues for >>> me, but healing after a 4-hour downtime is on another level of bad perf. >>> >>> For example, this command took many minutes to run: >>> >>> gluster volume heal androidpolice_data3 info summary >>> Brick nexus2:/mnt/nexus2_block4/androidpolice_data3 >>> Status: Connected >>> Total Number of entries: 91 >>> Number of entries in heal pending: 90 >>> Number of entries in split-brain: 0 >>> Number of entries possibly healing: 1 >>> >>> Brick forge...

...aling after a 4-hour downtime is on another level >>> of bad perf. >>> >>> For example, this command took many minutes to run: >>> >>> gluster volume heal androidpolice_data3 info summary >>> Brick nexus2:/mnt/nexus2_block4/androidpolice_data3 >>> Status: Connected >>> Total Number of entries: 91 >>> Number of entries in heal pending: 90 >>> Number of entries in split-brain: 0 >>> Number of entri...

...izations vs after. >> >> Volume Name: apkmirror_data1 >> Type: Replicate >> Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 4 = 4 >> Transport-type: tcp >> Bricks: >> Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 >> Brick2: forge:/mnt/forge_block1/apkmirror_data1 >> Brick3: hive:/mnt/hive_block1/apkmirror_data1 >> Brick4: citadel:/mnt/citadel_block1/apkmirror_data1 >> Options Reconfigured: >> cluster.quorum-count: 1 >> cluster.quorum-typ...

...ormance-wise before I applied the customizations vs after. > > Volume Name: apkmirror_data1 > Type: Replicate > Volume ID: 11ecee7e-d4f8-497a-9994-ceb144d6841e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 4 = 4 > Transport-type: tcp > Bricks: > Brick1: nexus2:/mnt/nexus2_block1/apkmirror_data1 > Brick2: forge:/mnt/forge_block1/apkmirror_data1 > Brick3: hive:/mnt/hive_block1/apkmirror_data1 > Brick4: citadel:/mnt/citadel_block1/apkmirror_data1 > Options Reconfigured: > cluster.quorum-count: 1 > cluster.quorum-type: fixed > network.pi...