[Gluster-devel] Compilation failed on latest gluster

[Ashish Pandey]

Hi, 

I am trying to build latest code on my laptop and it is giving compilation 
error - 

CC cli-rl.o 
CC cli-cmd-global.o 
CC cli-cmd-volume.o 
cli-cmd-volume.c: In function ‘cli_cmd_quota_cbk’: 
cli-cmd-volume.c:1712:35: error: ‘EVENT_QUOTA_ENABLE’ undeclared (first use in 
this function) 
gf_event (EVENT_QUOTA_ENABLE, "volume=%s", volname); 
^ 
cli-cmd-volume.c:1712:35: note: each undeclared identifier is reported only 
once for each function it appears in 
cli-cmd-volume.c:1715:35: error: ‘EVENT_QUOTA_DISABLE’ undeclared (first use in 
this function) 
gf_event (EVENT_QUOTA_DISABLE, "volume=%s", volname); 
^ 
cli-cmd-volume.c:1718:35: error: ‘EVENT_QUOTA_SET_USAGE_LIMIT’ undeclared 
(first use in this function) 
gf_event (EVENT_QUOTA_SET_USAGE_LIMIT, "volume=%s;" 
^ 
cli-cmd-volume.c:1723:35: error: ‘EVENT_QUOTA_SET_OBJECTS_LIMIT’ undeclared 
(first use in this function) 
gf_event (EVENT_QUOTA_SET_OBJECTS_LIMIT, "volume=%s;" 
^ 
cli-cmd-volume.c:1728:35: error: ‘EVENT_QUOTA_REMOVE_USAGE_LIMIT’ undeclared 
(first use in this function) 
gf_event (EVENT_QUOTA_REMOVE_USAGE_LIMIT, "volume=%s;" 
^ 
cli-cmd-volume.c:1732:35: error: ‘EVENT_QUOTA_REMOVE_OBJECTS_LIMIT’ undeclared 
(first use in this function) 
gf_event (EVENT_QUOTA_REMOVE_OBJECTS_LIMIT, 
^ 
cli-cmd-volume.c:1736:35: error: ‘EVENT_QUOTA_ALERT_TIME’ undeclared (first use 
in this function) 
gf_event (EVENT_QUOTA_ALERT_TIME, "volume=%s;time=%s", 
^ 
cli-cmd-volume.c:1740:35: error: ‘EVENT_QUOTA_SOFT_TIMEOUT’ undeclared (first 
use in this function) 
gf_event (EVENT_QUOTA_SOFT_TIMEOUT, "volume=%s;" 
^ 
cli-cmd-volume.c:1744:35: error: ‘EVENT_QUOTA_HARD_TIMEOUT’ undeclared (first 
use in this function) 
gf_event (EVENT_QUOTA_HARD_TIMEOUT, "volume=%s;" 
^ 
cli-cmd-volume.c:1748:35: error: ‘EVENT_QUOTA_DEFAULT_SOFT_LIMIT’ undeclared 
(first use in this function) 
gf_event (EVENT_QUOTA_DEFAULT_SOFT_LIMIT, "volume=%s;" 
^ 
Makefile:539: recipe for target 'cli-cmd-volume.o' failed 

If I roll back 4 patches and then compile it is working. 
I am suspecting that http://review.gluster.org/15230 is doing something. 
Could you please look into this? 
Do I need to do something to make it work? 

Ashish 





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

Re: [Gluster-devel] gfapi zero copy write enhancement

[Shyam]

On 08/24/2016 03:28 PM, Shyam wrote:

Hi,

I was attempting to review this [1] change, and for a long time I wanted
to understand why we need this and what is the manner in which we need
to achieve the same. As there is a lack of understanding on my part I am
starting with some questions.

1) In writev FOP what is the role/use of the iobref parameter?
- I do not see the posix xlator using this
- The payload is carried in vector, rather than in the iobref
- Across the code, other than protocol/client that (sorf of) serializes
this, I do not see it having any use

So what am I missing?


Looks like this [6] thread has some answers to this, digging through this.



2) Coming to the current change, what prevents us from doing this as [2]?
- in short just pass in the buffer received as a part of iovec

[2] is not necessarily clean, just a hack, that assumes there is a
iovcount of 1 always, and I just tested this with a write call, and not
a writev call. (just stating before we start a code review of the same ;) )

3) From discussions in [3] and [4] I understand that this is to
eliminate copy when working with RDMA. Further, Avati's response to the
thought, discusses why we need to leave the memory management of
read/write buffers to the applications than use/reuse gluster buffers.

So, in the long term if this is for RDMA, what is the change in
justification for the manner in which we are asking applications to use
gluster buffers, than doing it the other way?

4) Why should applications not reuse buffers? and instead ask for
fresh/new buffers for each write call?

5) What is the performance gain noticed with this approach? As the
thread that (re)started this is [5]. In Commvault Simpana,
- What were the perf gains due to this approach?
- How does the application use the write buffers?
  - Meaning, the buffer that is received from Gluster is used to
populate data from the network? I am curious as to how this application
uses these buffers, and where does data get copied into these buffers from.

Eliminating a copy in glfs_write seems trivial (if my hack and answers
to the first question are as per my assumptions), I am wondering what we
are attempting here, or what I am missing.

Thanks,
Shyam

[1] http://review.gluster.org/#/c/14784/
[2] https://paste.fedoraproject.org/413514/14720651/
[3] https://www.mail-archive.com/gluster-devel@gluster.org/msg03347.html
[4]
http://www.gluster.org/pipermail/gluster-devel/2015-February/043966.html
[5] http://www.gluster.org/pipermail/gluster-devel/2016-June/049858.html


[6] http://www.gluster.org/pipermail/gluster-devel/2016-June/049873.html


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

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

[Gluster-devel] gfapi zero copy write enhancement

[Shyam]

Hi,

I was attempting to review this [1] change, and for a long time I wanted 
to understand why we need this and what is the manner in which we need 
to achieve the same. As there is a lack of understanding on my part I am 
starting with some questions.


1) In writev FOP what is the role/use of the iobref parameter?
- I do not see the posix xlator using this
- The payload is carried in vector, rather than in the iobref
- Across the code, other than protocol/client that (sorf of) serializes 
this, I do not see it having any use


So what am I missing?

2) Coming to the current change, what prevents us from doing this as [2]?
- in short just pass in the buffer received as a part of iovec

[2] is not necessarily clean, just a hack, that assumes there is a 
iovcount of 1 always, and I just tested this with a write call, and not 
a writev call. (just stating before we start a code review of the same ;) )


3) From discussions in [3] and [4] I understand that this is to 
eliminate copy when working with RDMA. Further, Avati's response to the 
thought, discusses why we need to leave the memory management of 
read/write buffers to the applications than use/reuse gluster buffers.


So, in the long term if this is for RDMA, what is the change in 
justification for the manner in which we are asking applications to use 
gluster buffers, than doing it the other way?


4) Why should applications not reuse buffers? and instead ask for 
fresh/new buffers for each write call?


5) What is the performance gain noticed with this approach? As the 
thread that (re)started this is [5]. In Commvault Simpana,

- What were the perf gains due to this approach?
- How does the application use the write buffers?
  - Meaning, the buffer that is received from Gluster is used to 
populate data from the network? I am curious as to how this application 
uses these buffers, and where does data get copied into these buffers from.


Eliminating a copy in glfs_write seems trivial (if my hack and answers 
to the first question are as per my assumptions), I am wondering what we 
are attempting here, or what I am missing.


Thanks,
Shyam

[1] http://review.gluster.org/#/c/14784/
[2] https://paste.fedoraproject.org/413514/14720651/
[3] https://www.mail-archive.com/gluster-devel@gluster.org/msg03347.html
[4] http://www.gluster.org/pipermail/gluster-devel/2015-February/043966.html
[5] http://www.gluster.org/pipermail/gluster-devel/2016-June/049858.html
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] [Gluster-users] CFP for Gluster Developer Summit

[Arthy Loganathan]

On 08/24/2016 07:18 PM, Atin Mukherjee wrote:



On Wed, Aug 24, 2016 at 5:43 PM, Arthy Loganathan > wrote:


Hi,

I would like to propose below topic as a lightening talk.

Title: Data Logging to monitor Gluster Performance

Theme: Process and Infrastructure

To benchmark any software product, we often need to do performance
analysis of the system along with the product. I have written a
tool "System Monitor" to collect required data like CPU, memory
usage and load average periodically (with graphical
representation) of any process on a system. This data collected
can help in analyzing the system & product performance.


A link to this project would definitely help here.


Hi Atin,

Here is the link to the project - https://github.com/aloganat/system_monitor

Thanks & Regards,
Arthy



From this talk I would like to give an overview of this tool and
explain how it can be used to monitor Gluster performance.

Agenda:
  - Overview of the tool and its usage
  - Collecting the data in an excel sheet at regular intervals of time
  - Plotting the graph with that data (in progress)
  - a short demo

Thanks & Regards,

Arthy




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





--

--Atin


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

Re: [Gluster-devel] [Gluster-users] CFP for Gluster Developer Summit

[Atin Mukherjee]

On Wed, Aug 24, 2016 at 5:43 PM, Arthy Loganathan 
wrote:

> Hi,
>
> I would like to propose below topic as a lightening talk.
>
> Title: Data Logging to monitor Gluster Performance
>
> Theme: Process and Infrastructure
>
> To benchmark any software product, we often need to do performance
> analysis of the system along with the product. I have written a tool
> "System Monitor" to collect required data like CPU, memory usage and load
> average periodically (with graphical representation) of any process on a
> system. This data collected can help in analyzing the system & product
> performance.
>

A link to this project would definitely help here.


>
> From this talk I would like to give an overview of this tool and explain
> how it can be used to monitor Gluster performance.
>
> Agenda:
>   - Overview of the tool and its usage
>   - Collecting the data in an excel sheet at regular intervals of time
>   - Plotting the graph with that data (in progress)
>   - a short demo
>
> Thanks & Regards,
>
> Arthy
>
>
>
>
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>



-- 

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

[Gluster-devel] Weekly Community Meeting 24/Aug/2016 - Minutes

[Kaushal M]

Thanks once again, to all the attendees of todays meeting. We've been
having good meeting attendence lately, let's keep it going.

The minutes and logs for todays meeting are available from the links below,
Minutes: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-08-24/weekly_community_meeting_24aug2015.2016-08-24-12.00.html
Minutes (text):
https://meetbot.fedoraproject.org/gluster-meeting/2016-08-24/weekly_community_meeting_24aug2015.2016-08-24-12.00.txt
Log: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-08-24/weekly_community_meeting_24aug2015.2016-08-24-12.00.log.html

Let's meet again next week, at the same time, in #gluster-meeting.
Rastar is hosting.

~kaushal

(No minutes here this week. meetbot.fedoraproject.org isn't opening)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] [Gluster-users] CFP for Gluster Developer Summit

[Arthy Loganathan]

Hi,

I would like to propose below topic as a lightening talk.

Title: Data Logging to monitor Gluster Performance

Theme: Process and Infrastructure

To benchmark any software product, we often need to do performance 
analysis of the system along with the product. I have written a tool 
"System Monitor" to collect required data like CPU, memory usage and 
load average periodically (with graphical representation) of any process 
on a system. This data collected can help in analyzing the system & 
product performance.


From this talk I would like to give an overview of this tool and 
explain how it can be used to monitor Gluster performance.


Agenda:
  - Overview of the tool and its usage
  - Collecting the data in an excel sheet at regular intervals of time
  - Plotting the graph with that data (in progress)
  - a short demo

Thanks & Regards,

Arthy



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

[Gluster-devel] CFP for Gluster Developer Summit

[Arthy Loganathan]

Hi,

I would like to propose below topic as a lightening talk.

Title: Data Logging to monitor Gluster Performance

Theme: Process and Infrastructure

To benchmark any software product, we often need to do performance 
analysis of the system along with the product. I have written a tool 
"System Monitor" to collect required data like CPU, memory usage and 
load average periodically (with graphical representation) of any process 
on a system. This data collected can help in analyzing the system & 
product performance.


From this talk I would like to give an overview of this tool and 
explain how it can be used to monitor Gluster performance.


Agenda:
  - Overview of the tool and its usage
  - Collecting the data in an excel sheet at regular intervals of time
  - Plotting the graph with that data (in progress)
  - a short demo

Thanks & Regards,

Arthy



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

Re: [Gluster-devel] doubts in using gf_event/gf_msg

[Pranith Kumar Karampuri]

On Wed, Aug 24, 2016 at 5:38 PM, Aravinda  wrote:

> It is possible to overload gf_lg/gf_msg to send events to local eventsd.
> But we have to do additional parsing if we need to select the logs to
> convert as events. If we introduce new API, then it is not different from
> existing wrt adding events code in multiple places. But if it helps in
> sharing the host/port and other information(which we are discussing to
> support client events), I can give it a try(Move gf_event inside logging
> infra)
>

Sounds good to me. I will wait for others inputs here as well


>
> regards
> Aravinda
>
> On Wednesday 24 August 2016 05:15 PM, Pranith Kumar Karampuri wrote:
>
> Just resending in case you missed this mail.
>
> On Tue, Aug 23, 2016 at 2:31 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>> hi Aravinda,
>>I was wondering what is your opinion in sending selected logs as
>> events instead of treating them specially. Is this something you guys
>> considered? Do you think it is a bad idea to do it that way? We can even
>> come up with a new api which logs and then sends it as event.
>>
>> --
>> Pranith
>>
>
>
>
> --
> Pranith
>
>
>


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

Re: [Gluster-devel] [Gluster-users] CFP Gluster Developer Summit

[Kaleb S. KEITHLEY]

On 08/23/2016 07:29 PM, Amye Scavarda wrote:
> 
> 
> On Tue, Aug 23, 2016 at 7:41 AM, Kaleb S. KEITHLEY  > wrote:
> 
> On 08/17/2016 09:56 AM, Kaleb S. KEITHLEY wrote:
>> I propose to present on one or more of the following topics:
>>
>> * NFS-Ganesha Architecture, Roadmap, and Status, Jiffin Thotton 
>> copresenter.
>>
>> * Architecture of the High Availability
>> Solution for Ganesha and Samba - detailed walk through and demo of
>> current implementation - difference between the current and
>> storhaug implementations
>>
>> * High Level Overview of autoconf/automake/libtool configuration 
>> (I gave a presentation in BLR in 2015, so this is perhaps less 
>> interesting?)
>>
>> * Packaging Howto — RPMs and .debs (maybe a breakout session or a 
>> BOF. Would like to (re)enlist volunteers to help build packages.)
> 
> 
> Note addition of Jiffin as copresenter.  Thank you.
> 
> 
> --
> 
> 
> Kaleb
> 
> 
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org 
> http://www.gluster.org/mailman/listinfo/gluster-users
> 
> 
> 
> Out of these three? I think there's three, which one would you be most
> interested in giving?

Well four, but

I'd prefer to do the HA architecture and then let Jiffin give the
Ganesha architecture and roadmap.


-- 

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

Re: [Gluster-devel] doubts in using gf_event/gf_msg

[Pranith Kumar Karampuri]

Just resending in case you missed this mail.

On Tue, Aug 23, 2016 at 2:31 AM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:

> hi Aravinda,
>I was wondering what is your opinion in sending selected logs as
> events instead of treating them specially. Is this something you guys
> considered? Do you think it is a bad idea to do it that way? We can even
> come up with a new api which logs and then sends it as event.
>
> --
> Pranith
>



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

Re: [Gluster-devel] [Gluster-users] CFP for Gluster Developer Summit

[knarra]

Hi All,

I would like to propose below talk under the theme "Process & 
Infrastructure"


Title : Ovirt + Gluster

Ovirt is mainly a Virtualization management platform. It supports KVM 
based viritualization capabilities.
Gluster managment integration with Ovirt gives a cool web UI for the 
admin to manage the Gluster cluster.


Agenda:

1) Ovirt and its components.
2) How do one manage Gluster Cluster and perform various admin related 
tasks like add/remove/replace brick, Creating Snapshots etc

3) Nagios integration
4) Ovirt and Gluster Hyperconvergence

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

[Gluster-devel] Test email pls ignore

[Justin Clift]

Ignore this, it's just a test for measuring a delay issue with mailman.

+ Justin

--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi

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

Re: [Gluster-devel] [Gluster-users] CFP for Gluster Developer Summit

[Susant Palai]

Topic: Lock migration and how it overcomes data inconsistency in glusterFS - 
design, status and roadmap
Theme: Stability
Abstract: Rebalance process in glusterFS currently doesn't retain posix locks
  when it migrates files from source server to destination server.
  This can lead to data inconsistency in the files owing to successful
  writes by more than one client on a file incorrectly.
  In this talk, I will present the design of lock migration, its status 
and how this
  solves the problem of data inconsistency.
Thanks,
Susant Palai

- Original Message -
> From: "Shyam" 
> To: "Vijay Bellur" , "Gluster Devel" 
> , "gluster-users Discussion List"
> 
> Cc: "Amye Scavarda" 
> Sent: Tuesday, 23 August, 2016 11:29:01 PM
> Subject: Re: [Gluster-users] [Gluster-devel] CFP for Gluster Developer Summit
> 
> Theme: Gluster.Next
> 
> Topic: "DHT2 - O Brother, Where Art Thou?"
> 
> Description:
> An update on DHT2 design and it's progress, with the intention of
> enabling discussions around the love or lack of the same, for the
> proposed model.
> 
> Shyam
> 
> On 08/12/2016 03:48 PM, Vijay Bellur wrote:
> > Hey All,
> >
> > Gluster Developer Summit 2016 is fast approaching [1] on us. We are
> > looking to have talks and discussions related to the following themes in
> > the summit:
> >
> > 1. Gluster.Next - focusing on features shaping the future of Gluster
> >
> > 2. Experience - Description of real world experience and feedback from:
> >a> Devops and Users deploying Gluster in production
> >b> Developers integrating Gluster with other ecosystems
> >
> > 3. Use cases  - focusing on key use cases that drive Gluster.today and
> > Gluster.Next
> >
> > 4. Stability & Performance - focusing on current improvements to reduce
> > our technical debt backlog
> >
> > 5. Process & infrastructure  - focusing on improving current workflow,
> > infrastructure to make life easier for all of us!
> >
> > If you have a talk/discussion proposal that can be part of these themes,
> > please send out your proposal(s) by replying to this thread. Please
> > clearly mention the theme for which your proposal is relevant when you
> > do so. We will be ending the CFP by 12 midnight PDT on August 31st, 2016.
> >
> > If you have other topics that do not fit in the themes listed, please
> > feel free to propose and we might be able to accommodate some of them as
> > lightening talks or something similar.
> >
> > Please do reach out to me or Amye if you have any questions.
> >
> > Thanks!
> > Vijay
> >
> > [1] https://www.gluster.org/events/summit2016/
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-devel
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
> 
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Impact of reduced lookup on other xlators

[Anuradha Talur]

Response inline.

- Original Message -
> From: "Pranith Kumar Karampuri" 
> To: "Anuradha Talur" 
> Cc: "Poornima Gurusiddaiah" , "Raghavendra Gowdappa" 
> , "Susant Palai"
> , "Ashish Pandey" , "Ravishankar N" 
> , "Krutika
> Dhananjay" , "Nithya Balachandran" 
> , "Dan Lambright" 
> Sent: Tuesday, August 23, 2016 4:27:56 PM
> Subject: Re: Impact of reduced lookup on other xlators
> 
> On Tue, Aug 23, 2016 at 1:56 PM, Anuradha Talur  wrote:
> 
> > Hi,
> >
> > As we (Poornima, Krutika, Ravi and I) discussed, listing down the
> > dependencies from AFR's perspective:
> >
> > 1) AFR needs lookups to detect if a file's inode ctx is fresh, otherwise
> > it might lead to stale reads. This problem might be exposed frequently when
> > timeout is increased.
> >
> 
> I didn't get this part. Could you elaborate? Is it because of readdirp's
> need-heal? Other than this I  don't see any other requirement for lookups?
> This is something we can fix in different ways like getting need-heal in
> other fops which are wound to bricks.
> 
The easiest situation to understand is in multi-client scenario.

Two clients have accessed a file and have its details in their inode_ctx.
One client won't be aware of the failure seen by the other client in non-brick 
down
cases. Lookup was the way AFR was able to detect this failure.
Now, given that md-cache timeout is increased, lookups won't reach till AFR.
Which means, there is a chance that AFR's inode_ctx of a file is not up to date.
As event-gen doesn't change in unaware client reads might be served from stale 
brick.
This problem exists even now but increasing timeout will expose this more often.

Upcall can send invalidates. AFR should act on these invalidates selectively,
based on whether the file really needs heal or not.
We discussed some ways of doing this, but haven't arrived on any conclusion yet.

Along with this, we should also get need-heal in other fops too.
> 
> > 2) Client side healing needs stats to be wound down to AFR. (This can be
> > handled by switching off stat-prefetch or reducing its timeout only for
> > healing)
> >
> 
> I think we should do something similar to EC where we heal on getfattr on a
> virtual xattr or something. It is important to keep I/O as performant as
> possible.
> 
Hmm, correct.
> 
> >
> > Requirement on AFR from md-cache that Poornima pointed out:
> > 1) How to distinguish child_modified due to child_down from child_modified
> > from child_up so that cache is invalidated only on child_down, not on up?
> >
> 
> Didn't understand this part as well. May be you discussed it in the
> meeting. Could you clarify why we need to invalidate cache when child is
> down? If a child is down and we invalidate the cache, it will send a lookup
> which still goes to the remaining bricks right?
> 

In a non-replicate scenario, consider that md-cache has cached details of X 
files.
Now, one child goes down on which these files mapped. ls on the dir will succeed
and list these files but when the application tries to perform any operation on
one of these files, it will fail. This would be incorrect.
This is why md-cache's cache needs to be invalidated on child-down.

In a replicate scenario too this will happen when both subvols of AFR 
die/disconnect.
> 
> I think the goal should be to prevent dependency on lookups as much as
> possible. So let us work on the things that need to be taken care for that.
Correct.
> 
> >
> > If there are no objections about the first 2 points mentioned, I will
> > raise bugs to track them.
> > --
> >
> > *From: *"Poornima Gurusiddaiah" 
> > *To: *"Raghavendra Gowdappa" , "Susant Palai" <
> > spa...@redhat.com>, "Pranith Kumar Karampuri" ,
> > "Ashish Pandey" , "Anuradha Talur"
> > ,
> > "Ravishankar N" , "Krutika Dhananjay" <
> > kdhan...@redhat.com>, "Nithya Balachandran" , "Dan
> > Lambright" 
> > *Sent: *Tuesday, August 23, 2016 10:43:40 AM
> > *Subject: *Impact of reduced lookup on other xlators
> >
> > Hi All,
> >
> > Because of certain improvements in md-cache and longer caching time in
> > md-cache,
> > we will have reduced lookups sent to the cluster xlators and below. The
> > guarantee that every IO fop
> > will be preceded by a lookup will not hold true anymore(it was the case
> > earlier as well, but the
> > timeout was 1s). This may break certain assumptions made by cluster
> > xlators- dht, afr, tier, ec etc.
> >
> > This thread is intended to identify and discuss those issues and have bugs
> > filed. Request the cluster
> > xlator maintainers to identify if there are any such issues that 

[Gluster-devel] CFP Gluster Developer Summit

[Avra Sengupta]

Hi,

I would like to propose the following talks:

1. Ttitle: Server side replication
Theme: Gluster.Next
Abstract: Achieving availability and correctness without 
compromising performance, is always a challenge in designing new storage 
replication technologies. In this talk I would talk about the following:


 * Challenges faced by client side replication
 * How we can address these challenges with server side replication
 * Use cases for both server side and client side replication

2. Title: Scalability Issues and probable solutions
Theme: Stability and performance
 Abstract: Scalability in terms of number of nodes, and number of 
volumes in a cluster as of today is something I plan to explore in this 
talk. I would like to discuss the numbers we reach today, and probable 
solutions to get to better numbers. I would talk about the following:


 * Bottlenecks in scalability due to Glusterd and probable solutions
 * Scalability issues due to snapshot bricks' resource consumption and
   probable solutions


Regards,
Avra

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