Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

[Xie Changlong]

在 6/5/2017 6:30 PM, Pranith Kumar Karampuri 写道:

I meant what are you using gluster for? VM workload or image/video file
creation or lots of small files etc etc.


1) We use glusterfs for general purpose, no limit to image/video file
creation or small files etc.

2) We just want a low performance affect way to calculate each brick's 
iops/bandwidth for the upper layer management app. BTW, is there any 
other way to get iops/bandwith for each brick besides profile?


--
Thanks
-Xie
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Adding one variable to inode structure

[Tahereh Fattahi]

Thank you very much
But if it was like trusted.glusterfs.dht or trusted.glusterfs.qouta it was
more better.

On Mon, Jun 5, 2017 at 2:58 PM, Pranith Kumar Karampuri  wrote:

>
>
> On Mon, Jun 5, 2017 at 12:40 PM, Tahereh Fattahi 
> wrote:
>
>> yes you are correct.
>> I thought that for creating a video file i first should do a getfattr, if
>> it was not set then I should do a setxattr.
>> So it would be have bad performance to do a getfattr after every create,
>> for video files. Am I correct?
>>
>
> How consistent should it be? May be you can do this operation on another
> thread or something in the background so that your application may not see
> the delay in doing I/O?
>
>
>>
>> On Mon, Jun 5, 2017 at 11:28 AM, Pranith Kumar Karampuri <
>> pkara...@redhat.com> wrote:
>>
>>> Oh you want applications to do getfattr to find that it is there?
>>>
>>> I think I understood what you are looking for now. So basically
>>> applications will keep doing creation of some files/directories, whenever a
>>> video file is created you want the bricks to set an extended attribute on
>>> the directory, so that the application can use it. I don't think this
>>> doesn't look like the job of index xlator either.
>>>
>>> Why do you not want to set the extended attribute from client and want
>>> the fs to do it on-behalf of the application? Setting it from client has
>>> benefits like even when one brick is down it will automatically heal this
>>> extended attribute etc.
>>>
>>> On Mon, Jun 5, 2017 at 12:10 PM, Tahereh Fattahi 
>>> wrote:
>>>
 I want in in mount directory in client side

 On Mon, Jun 5, 2017 at 11:07 AM, Pranith Kumar Karampuri <
 pkara...@redhat.com> wrote:

>
>
> On Mon, Jun 5, 2017 at 11:24 AM, Tahereh Fattahi <
> t28.fatt...@gmail.com> wrote:
>
>> Thank you
>> I see that this xlator is loaded in server side.
>> How can I access to variable in index xlator in client side?
>> is it correct? getfattr trusted.index.myvar
>>
>
> To which xlator do you want this information? Or do you want this on
> mount?
>
>
>>
>> On Mon, Jun 5, 2017 at 10:00 AM, Pranith Kumar Karampuri <
>> pkara...@redhat.com> wrote:
>>
>>>
>>>
>>> On Mon, Jun 5, 2017 at 9:55 AM, Tahereh Fattahi <
>>> t28.fatt...@gmail.com> wrote:
>>>
 Assume that one client wants to search it's directories for video
 files.
  I want use something that helps this client to search just
 directories that have this kind of file.
 like a extended attribute, but I want this attribute be set by
 server not by client.
 I dont know which xlator is suitable for this work.

>>>
>>> The xlator that comes close to it is:  index xlator
>>> xlators/features/index/src
>>>
>>> You may have to track extra operations like
>>> create/mknod/link/rename/unlink to make sure you get the
>>> functionality you want. Basically this xlator helps you in indexing a
>>> behavior. We use this for indexing directories/files that need heal etc.
>>>
>>>

 On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
 pkara...@redhat.com> wrote:

> This sounds hacky. In general anything that is specific about an
> inode, we try to store it in inode-ctx. Who uses this information 
> about
> presence of video-file and how? May be with that knowledge there 
> could be a
> possibility we can improve the solution. Do let us know the complete
> problem you are trying to solve.
>
> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi <
> t28.fatt...@gmail.com> wrote:
>
>> Hi
>> I want to add one boolean field to inode structure for a
>> directory.
>>  when it is 1 it means that directory has one or more video file.
>> when it is 0 it means that there is no video file in that directory.
>> I can add this variable to inode structure and update it in
>> server side, in posix_create function (when there is a create 
>> request for a
>> video file).
>> question is about client knowledge about this variable. is it
>> possible that client can see the amount of this variable of different
>> servers (bricks) and OR them to one variable in cient's inode of the
>> directory? in which xlator I should try in client side?
>>
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
>
> --
> Pranith
>


>>>
>>>
>>> --
>>> Pranith
>>>
>>
>>
>
>
> --
> 

Re: [Gluster-devel] [Gluster-users] [Gluster-Maintainers] Backport for "Add back socket for polling of events immediately..."

[Shyam]

On 05/30/2017 08:44 PM, Zhang Huan wrote:

* Are there any existing users who need this enhancement?
https://bugzilla.redhat.com/show_bug.cgi?id=1358606#c27

Though not sure what branch Zhang Huan is on. @Zhang your inputs are
needed
here.

We are currently on 3.8. Thus the performance number is based on 3.8.
If you need more details, please let me know.


Thanks Zhang. The question was more on the lines whether you need
backport of the fix to 3.8.


Actually, we really need this backported to 3.8. I have seen the
backport of it to 3.8.
https://review.gluster.org/#/c/15046/
Once it gets merged, we will rebase to it and test it as a whole.


@Zang and @list, as this is a performance improvement feature and we do 
not backport features into releases (as a rule) that are already out in 
the field, hence we will not be backporting this to 3.8.


Further, 3.8 will EOL (end of life) from a maintenance standpoint when 
3.12 is released (scheduled around Aug 30th).


We would be merging this into 3.11.1 to provide early access for tests 
and such (Release date of June 20th), and this feature would be made 
generally available with 3.12.


We regret any inconvenience.




Can you upgrade to recent releases (say 3.11.x or 3.10.x)?


Sorry, I am afraid not. Gusterfs is one of the key components in our
product. An upgrade alone would break the whole thing.

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Coverity covscan for 2017-06-05-a9d3d043 (master branch)

[staticanalysis]

GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-06-05-a9d3d043
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Release 3.12: Scope and calendar!

[Sonal Arora]

On Thu, Jun 1, 2017 at 10:47 PM, Shyam  wrote:

> Hi,
>
> Here are some top reminders for the 3.12 release:
>
> 1) When 3.12 is released 3.8 will be EOL'd, hence users are encouraged to
> prepare for the same as per the calendar posted here.
>
> 2) 3.12 is a long term maintenance (LTM) release, and potentially the last
> in the 3.x line of Gluster!
>
> 3) From this release onward, the feature freeze date is moved ~45 days in
> advance, before the release. Hence, for this one release you will have
> lesser time to get your features into the release.
>
> Release calendar:
>
> - Feature freeze, or branching date: July 17th, 2017
>- All feature post this date need exceptions granted to make it into
> the 3.12 release
>
> - Release date: August 30th, 2017
>
> Release owners:
>
> - Shyam
> -  Any volunteers?
>
> Features and major changes process in a nutshell:
> 1) Open a github issue
>
> 2) Refer the issue # in the commit messages of all changes against the
> feature (specs, code, tests, docs, release notes) (refer to the issue as
> "updates gluster/glusterfs#N" where N is the issue)
>
> 3) We will ease out release-notes updates form this release onward. Still
> thinking how to get that done, but the intention is that a contributor can
> update release notes before/on/after completion of the feature and not
> worry about branching dates etc. IOW, you can control when you are done,
> than the release dates controlling the same for you.
>
> Thanks,
> Shyam
>

I am interested in this.

-Sonal

> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Release 3.12: Scope and calendar!

[Ankit Raj]

On Mon, Jun 5, 2017 at 3:30 PM, Jiffin Tony Thottan 
wrote:

>
>
> On 01/06/17 22:47, Shyam wrote:
>
>> Hi,
>>
>> Here are some top reminders for the 3.12 release:
>>
>> 1) When 3.12 is released 3.8 will be EOL'd, hence users are encouraged to
>> prepare for the same as per the calendar posted here.
>>
>> 2) 3.12 is a long term maintenance (LTM) release, and potentially the
>> last in the 3.x line of Gluster!
>>
>> 3) From this release onward, the feature freeze date is moved ~45 days in
>> advance, before the release. Hence, for this one release you will have
>> lesser time to get your features into the release.
>>
>> Release calendar:
>>
>> - Feature freeze, or branching date: July 17th, 2017
>>- All feature post this date need exceptions granted to make it into
>> the 3.12 release
>>
>> - Release date: August 30th, 2017
>>
>> Release owners:
>>
>> - Shyam
>> -  Any volunteers?
>>
>>
> I am interested
> --
> Jiffin
>
>

  I am also interested
   Ankit

> Features and major changes process in a nutshell:
>> 1) Open a github issue
>>
>> 2) Refer the issue # in the commit messages of all changes against the
>> feature (specs, code, tests, docs, release notes) (refer to the issue as
>> "updates gluster/glusterfs#N" where N is the issue)
>>
>> 3) We will ease out release-notes updates form this release onward. Still
>> thinking how to get that done, but the intention is that a contributor can
>> update release notes before/on/after completion of the feature and not
>> worry about branching dates etc. IOW, you can control when you are done,
>> than the release dates controlling the same for you.
>>
>> Thanks,
>> Shyam
>> ___
>> Gluster-users mailing list
>> gluster-us...@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

[Pranith Kumar Karampuri]

On Mon, Jun 5, 2017 at 12:40 PM, Xie Changlong 
wrote:

> 在 6/5/2017 2:34 PM, Pranith Kumar Karampuri 写道:
>
>> What is your usecase if I may ask?
>>
>>
> Only fio/iozone now, maybe you can give me better test sugguestion :)
>

I meant what are you using gluster for? VM workload or image/video file
creation or lots of small files etc etc.


>
> seq read
> # dd if=/dev/zero  of=test bs=4k count=524288
> #fio --filename=test -iodepth=64 -ioengine=libaio --direct=1 --rw=read
> --bs=1m --size=2g --numjobs=4 --runtime=10 --group_reporting
> --name=test-read
> seq write
> # fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=write
> -bs=1m -size=2g -numjobs=4 -runtime=20 -group_reporting -name=test-write
>
> random read
> #fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=randread
> -bs=4k -size=2G -numjobs=64 -runtime=20 -group_reporting
> -name=test-rand-read
>
> random write
> #fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=randwrite
> -bs=4k -size=2G -numjobs=64 -runtime=20 -group_reporting
> -name=test-rand-write
>
>
> iozone  1 thread
> # ./iozone -s 10g -r 1m -i 0 -i 1 -f /mnt/test-volume/test -Rb
> /tmp/test_iozone_1.xls
> iozone  2 multi-threads
> # ./iozone -s 10g -r 1m -i 0 -i 1 -f /mnt/test-volume/test -t 8 -Rb
> /tmp/test_iozone_2.xls
>
>
>
> On Mon, Jun 5, 2017 at 11:08 AM, Xie Changlong
>> wrote:
>>
>> 在 6/5/2017 1:22 PM, Pranith Kumar Karampuri 写道:
>>>
>>> On Mon, Jun 5, 2017 at 8:29 AM, Xie Changlong
 wrote:

 在 6/5/2017 10:50 AM, Pranith Kumar Karampuri 写道:

> I think there have been improvements here to use special instructions
> to
>

> --
> Thanks
> -Xie
>



-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Adding one variable to inode structure

[Pranith Kumar Karampuri]

On Mon, Jun 5, 2017 at 12:40 PM, Tahereh Fattahi 
wrote:

> yes you are correct.
> I thought that for creating a video file i first should do a getfattr, if
> it was not set then I should do a setxattr.
> So it would be have bad performance to do a getfattr after every create,
> for video files. Am I correct?
>

How consistent should it be? May be you can do this operation on another
thread or something in the background so that your application may not see
the delay in doing I/O?


>
> On Mon, Jun 5, 2017 at 11:28 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>> Oh you want applications to do getfattr to find that it is there?
>>
>> I think I understood what you are looking for now. So basically
>> applications will keep doing creation of some files/directories, whenever a
>> video file is created you want the bricks to set an extended attribute on
>> the directory, so that the application can use it. I don't think this
>> doesn't look like the job of index xlator either.
>>
>> Why do you not want to set the extended attribute from client and want
>> the fs to do it on-behalf of the application? Setting it from client has
>> benefits like even when one brick is down it will automatically heal this
>> extended attribute etc.
>>
>> On Mon, Jun 5, 2017 at 12:10 PM, Tahereh Fattahi 
>> wrote:
>>
>>> I want in in mount directory in client side
>>>
>>> On Mon, Jun 5, 2017 at 11:07 AM, Pranith Kumar Karampuri <
>>> pkara...@redhat.com> wrote:
>>>


 On Mon, Jun 5, 2017 at 11:24 AM, Tahereh Fattahi  wrote:

> Thank you
> I see that this xlator is loaded in server side.
> How can I access to variable in index xlator in client side?
> is it correct? getfattr trusted.index.myvar
>

 To which xlator do you want this information? Or do you want this on
 mount?


>
> On Mon, Jun 5, 2017 at 10:00 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>>
>>
>> On Mon, Jun 5, 2017 at 9:55 AM, Tahereh Fattahi <
>> t28.fatt...@gmail.com> wrote:
>>
>>> Assume that one client wants to search it's directories for video
>>> files.
>>>  I want use something that helps this client to search just
>>> directories that have this kind of file.
>>> like a extended attribute, but I want this attribute be set by
>>> server not by client.
>>> I dont know which xlator is suitable for this work.
>>>
>>
>> The xlator that comes close to it is:  index xlator
>> xlators/features/index/src
>>
>> You may have to track extra operations like
>> create/mknod/link/rename/unlink to make sure you get the
>> functionality you want. Basically this xlator helps you in indexing a
>> behavior. We use this for indexing directories/files that need heal etc.
>>
>>
>>>
>>> On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
>>> pkara...@redhat.com> wrote:
>>>
 This sounds hacky. In general anything that is specific about an
 inode, we try to store it in inode-ctx. Who uses this information about
 presence of video-file and how? May be with that knowledge there could 
 be a
 possibility we can improve the solution. Do let us know the complete
 problem you are trying to solve.

 On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi <
 t28.fatt...@gmail.com> wrote:

> Hi
> I want to add one boolean field to inode structure for a directory.
>  when it is 1 it means that directory has one or more video file.
> when it is 0 it means that there is no video file in that directory.
> I can add this variable to inode structure and update it in server
> side, in posix_create function (when there is a create request for a 
> video
> file).
> question is about client knowledge about this variable. is it
> possible that client can see the amount of this variable of different
> servers (bricks) and OR them to one variable in cient's inode of the
> directory? in which xlator I should try in client side?
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



 --
 Pranith

>>>
>>>
>>
>>
>> --
>> Pranith
>>
>
>


 --
 Pranith

>>>
>>>
>>
>>
>> --
>> Pranith
>>
>
>


-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] Release 3.12: Scope and calendar!

[Jiffin Tony Thottan]

On 01/06/17 22:47, Shyam wrote:

Hi,

Here are some top reminders for the 3.12 release:

1) When 3.12 is released 3.8 will be EOL'd, hence users are encouraged 
to prepare for the same as per the calendar posted here.


2) 3.12 is a long term maintenance (LTM) release, and potentially the 
last in the 3.x line of Gluster!


3) From this release onward, the feature freeze date is moved ~45 days 
in advance, before the release. Hence, for this one release you will 
have lesser time to get your features into the release.


Release calendar:

- Feature freeze, or branching date: July 17th, 2017
   - All feature post this date need exceptions granted to make it 
into the 3.12 release


- Release date: August 30th, 2017

Release owners:

- Shyam
-  Any volunteers?



I am interested
--
Jiffin


Features and major changes process in a nutshell:
1) Open a github issue

2) Refer the issue # in the commit messages of all changes against the 
feature (specs, code, tests, docs, release notes) (refer to the issue 
as "updates gluster/glusterfs#N" where N is the issue)


3) We will ease out release-notes updates form this release onward. 
Still thinking how to get that done, but the intention is that a 
contributor can update release notes before/on/after completion of the 
feature and not worry about branching dates etc. IOW, you can control 
when you are done, than the release dates controlling the same for you.


Thanks,
Shyam
___
Gluster-users mailing list
gluster-us...@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

[Xie Changlong]

在 6/5/2017 3:10 PM, Xie Changlong 写道:

在 6/5/2017 2:34 PM, Pranith Kumar Karampuri 写道:

What is your usecase if I may ask?



Only fio/iozone now, maybe you can give me better test sugguestion :)

seq read
# dd if=/dev/zero  of=test bs=4k count=524288
#fio --filename=test -iodepth=64 -ioengine=libaio --direct=1 --rw=read 
--bs=1m --size=2g --numjobs=4 --runtime=10 --group_reporting 
--name=test-read

seq write
# fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=write 
-bs=1m -size=2g -numjobs=4 -runtime=20 -group_reporting -name=test-write


random read
#fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=randread 
-bs=4k -size=2G -numjobs=64 -runtime=20 -group_reporting 
-name=test-rand-read


random write
#fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=randwrite 
-bs=4k -size=2G -numjobs=64 -runtime=20 -group_reporting 
-name=test-rand-write



iozone  1 thread
# ./iozone -s 10g -r 1m -i 0 -i 1 -f /mnt/test-volume/test -Rb 
/tmp/test_iozone_1.xls

iozone  2 multi-threads
# ./iozone -s 10g -r 1m -i 0 -i 1 -f /mnt/test-volume/test -t 8 -Rb 
/tmp/test_iozone_2.xls




Re-declare,
For fio, i compare "bw" and "iops" fileds.
For iozone, i compare "write" "rewrite" "read" "re-read" fileds.




On Mon, Jun 5, 2017 at 11:08 AM, Xie Changlong
wrote:


在 6/5/2017 1:22 PM, Pranith Kumar Karampuri 写道:


On Mon, Jun 5, 2017 at 8:29 AM, Xie Changlong
wrote:

在 6/5/2017 10:50 AM, Pranith Kumar Karampuri 写道:
I think there have been improvements here to use special 
instructions to




--
Thanks
-Xie
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

[Xie Changlong]

在 6/5/2017 2:34 PM, Pranith Kumar Karampuri 写道:

What is your usecase if I may ask?



Only fio/iozone now, maybe you can give me better test sugguestion :)

seq read
# dd if=/dev/zero  of=test bs=4k count=524288
#fio --filename=test -iodepth=64 -ioengine=libaio --direct=1 --rw=read 
--bs=1m --size=2g --numjobs=4 --runtime=10 --group_reporting 
--name=test-read

seq write
# fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=write 
-bs=1m -size=2g -numjobs=4 -runtime=20 -group_reporting -name=test-write


random read
#fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=randread 
-bs=4k -size=2G -numjobs=64 -runtime=20 -group_reporting 
-name=test-rand-read


random write
#fio -filename=test -iodepth=64 -ioengine=libaio -direct=1 -rw=randwrite 
-bs=4k -size=2G -numjobs=64 -runtime=20 -group_reporting 
-name=test-rand-write



iozone  1 thread
# ./iozone -s 10g -r 1m -i 0 -i 1 -f /mnt/test-volume/test -Rb 
/tmp/test_iozone_1.xls

iozone  2 multi-threads
# ./iozone -s 10g -r 1m -i 0 -i 1 -f /mnt/test-volume/test -t 8 -Rb 
/tmp/test_iozone_2.xls




On Mon, Jun 5, 2017 at 11:08 AM, Xie Changlong
wrote:


在 6/5/2017 1:22 PM, Pranith Kumar Karampuri 写道:


On Mon, Jun 5, 2017 at 8:29 AM, Xie Changlong
wrote:

在 6/5/2017 10:50 AM, Pranith Kumar Karampuri 写道:

I think there have been improvements here to use special instructions to


--
Thanks
-Xie
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Adding one variable to inode structure

[Pranith Kumar Karampuri]

Oh you want applications to do getfattr to find that it is there?

I think I understood what you are looking for now. So basically
applications will keep doing creation of some files/directories, whenever a
video file is created you want the bricks to set an extended attribute on
the directory, so that the application can use it. I don't think this
doesn't look like the job of index xlator either.

Why do you not want to set the extended attribute from client and want the
fs to do it on-behalf of the application? Setting it from client has
benefits like even when one brick is down it will automatically heal this
extended attribute etc.

On Mon, Jun 5, 2017 at 12:10 PM, Tahereh Fattahi 
wrote:

> I want in in mount directory in client side
>
> On Mon, Jun 5, 2017 at 11:07 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>>
>>
>> On Mon, Jun 5, 2017 at 11:24 AM, Tahereh Fattahi 
>> wrote:
>>
>>> Thank you
>>> I see that this xlator is loaded in server side.
>>> How can I access to variable in index xlator in client side?
>>> is it correct? getfattr trusted.index.myvar
>>>
>>
>> To which xlator do you want this information? Or do you want this on
>> mount?
>>
>>
>>>
>>> On Mon, Jun 5, 2017 at 10:00 AM, Pranith Kumar Karampuri <
>>> pkara...@redhat.com> wrote:
>>>


 On Mon, Jun 5, 2017 at 9:55 AM, Tahereh Fattahi 
 wrote:

> Assume that one client wants to search it's directories for video
> files.
>  I want use something that helps this client to search just
> directories that have this kind of file.
> like a extended attribute, but I want this attribute be set by server
> not by client.
> I dont know which xlator is suitable for this work.
>

 The xlator that comes close to it is:  index xlator
 xlators/features/index/src

 You may have to track extra operations like
 create/mknod/link/rename/unlink to make sure you get the functionality
 you want. Basically this xlator helps you in indexing a behavior. We use
 this for indexing directories/files that need heal etc.


>
> On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>> This sounds hacky. In general anything that is specific about an
>> inode, we try to store it in inode-ctx. Who uses this information about
>> presence of video-file and how? May be with that knowledge there could 
>> be a
>> possibility we can improve the solution. Do let us know the complete
>> problem you are trying to solve.
>>
>> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi <
>> t28.fatt...@gmail.com> wrote:
>>
>>> Hi
>>> I want to add one boolean field to inode structure for a directory.
>>>  when it is 1 it means that directory has one or more video file.
>>> when it is 0 it means that there is no video file in that directory.
>>> I can add this variable to inode structure and update it in server
>>> side, in posix_create function (when there is a create request for a 
>>> video
>>> file).
>>> question is about client knowledge about this variable. is it
>>> possible that client can see the amount of this variable of different
>>> servers (bricks) and OR them to one variable in cient's inode of the
>>> directory? in which xlator I should try in client side?
>>>
>>> ___
>>> Gluster-devel mailing list
>>> Gluster-devel@gluster.org
>>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>>
>>
>>
>>
>> --
>> Pranith
>>
>
>


 --
 Pranith

>>>
>>>
>>
>>
>> --
>> Pranith
>>
>
>


-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Adding one variable to inode structure

[Tahereh Fattahi]

I want in in mount directory in client side

On Mon, Jun 5, 2017 at 11:07 AM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:

>
>
> On Mon, Jun 5, 2017 at 11:24 AM, Tahereh Fattahi 
> wrote:
>
>> Thank you
>> I see that this xlator is loaded in server side.
>> How can I access to variable in index xlator in client side?
>> is it correct? getfattr trusted.index.myvar
>>
>
> To which xlator do you want this information? Or do you want this on mount?
>
>
>>
>> On Mon, Jun 5, 2017 at 10:00 AM, Pranith Kumar Karampuri <
>> pkara...@redhat.com> wrote:
>>
>>>
>>>
>>> On Mon, Jun 5, 2017 at 9:55 AM, Tahereh Fattahi 
>>> wrote:
>>>
 Assume that one client wants to search it's directories for video files.
  I want use something that helps this client to search just directories
 that have this kind of file.
 like a extended attribute, but I want this attribute be set by server
 not by client.
 I dont know which xlator is suitable for this work.

>>>
>>> The xlator that comes close to it is:  index xlator
>>> xlators/features/index/src
>>>
>>> You may have to track extra operations like
>>> create/mknod/link/rename/unlink to make sure you get the functionality
>>> you want. Basically this xlator helps you in indexing a behavior. We use
>>> this for indexing directories/files that need heal etc.
>>>
>>>

 On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
 pkara...@redhat.com> wrote:

> This sounds hacky. In general anything that is specific about an
> inode, we try to store it in inode-ctx. Who uses this information about
> presence of video-file and how? May be with that knowledge there could be 
> a
> possibility we can improve the solution. Do let us know the complete
> problem you are trying to solve.
>
> On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi  > wrote:
>
>> Hi
>> I want to add one boolean field to inode structure for a directory.
>>  when it is 1 it means that directory has one or more video file.
>> when it is 0 it means that there is no video file in that directory.
>> I can add this variable to inode structure and update it in server
>> side, in posix_create function (when there is a create request for a 
>> video
>> file).
>> question is about client knowledge about this variable. is it
>> possible that client can see the amount of this variable of different
>> servers (bricks) and OR them to one variable in cient's inode of the
>> directory? in which xlator I should try in client side?
>>
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
>
> --
> Pranith
>


>>>
>>>
>>> --
>>> Pranith
>>>
>>
>>
>
>
> --
> Pranith
>
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Adding one variable to inode structure

[Pranith Kumar Karampuri]

On Mon, Jun 5, 2017 at 11:24 AM, Tahereh Fattahi 
wrote:

> Thank you
> I see that this xlator is loaded in server side.
> How can I access to variable in index xlator in client side?
> is it correct? getfattr trusted.index.myvar
>

To which xlator do you want this information? Or do you want this on mount?


>
> On Mon, Jun 5, 2017 at 10:00 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>>
>>
>> On Mon, Jun 5, 2017 at 9:55 AM, Tahereh Fattahi 
>> wrote:
>>
>>> Assume that one client wants to search it's directories for video files.
>>>  I want use something that helps this client to search just directories
>>> that have this kind of file.
>>> like a extended attribute, but I want this attribute be set by server
>>> not by client.
>>> I dont know which xlator is suitable for this work.
>>>
>>
>> The xlator that comes close to it is:  index xlator
>> xlators/features/index/src
>>
>> You may have to track extra operations like create/mknod/link/rename/unlink
>> to make sure you get the functionality you want. Basically this xlator
>> helps you in indexing a behavior. We use this for indexing
>> directories/files that need heal etc.
>>
>>
>>>
>>> On Mon, Jun 5, 2017 at 7:13 AM, Pranith Kumar Karampuri <
>>> pkara...@redhat.com> wrote:
>>>
 This sounds hacky. In general anything that is specific about an inode,
 we try to store it in inode-ctx. Who uses this information about presence
 of video-file and how? May be with that knowledge there could be a
 possibility we can improve the solution. Do let us know the complete
 problem you are trying to solve.

 On Mon, Jun 5, 2017 at 4:53 AM, Tahereh Fattahi 
 wrote:

> Hi
> I want to add one boolean field to inode structure for a directory.
>  when it is 1 it means that directory has one or more video file. when
> it is 0 it means that there is no video file in that directory.
> I can add this variable to inode structure and update it in server
> side, in posix_create function (when there is a create request for a video
> file).
> question is about client knowledge about this variable. is it possible
> that client can see the amount of this variable of different servers
> (bricks) and OR them to one variable in cient's inode of the directory? in
> which xlator I should try in client side?
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



 --
 Pranith

>>>
>>>
>>
>>
>> --
>> Pranith
>>
>
>


-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Qusetions] How profile affect glusterfs performance?

[Pranith Kumar Karampuri]

What is your usecase if I may ask?

On Mon, Jun 5, 2017 at 11:08 AM, Xie Changlong 
wrote:

> 在 6/5/2017 1:22 PM, Pranith Kumar Karampuri 写道:
>
>> On Mon, Jun 5, 2017 at 8:29 AM, Xie Changlong 
>> wrote:
>>
>> 在 6/5/2017 10:50 AM, Pranith Kumar Karampuri 写道:
>>>
>>> I think there have been improvements here to use special instructions to


>>> if "special instructions" means profile command or more? Also can you
>>> point which commit?
>>>
>>>
>> I meant Intel CPU extentions
>> You should look at
>> http://review.gluster.org/12209
>> http://review.gluster.org/12210
>> https://review.gluster.org/16963
>> https://review.gluster.org/17009
>>
>
> Useful enough for me, thanks for your patience.
>
>
>>
>> do the increments instead of taking spin-locks and doing increments. So
>>>
 may be it doesn't affect performance as much anymore. I think if you
 don't
 see a difference, then the enhancements are doing a good job :-).

 Which version of gluster are you using?


>>> Our version is gluster 3.8.4
>>>
>>> --
>>> Thanks
>>>  -Xie
>>>
>>>
>>
>>
>>
> --
> Thanks
> -Xie
>



-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel