[ 
https://issues.apache.org/jira/browse/GEODE-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alberto Gomez updated GEODE-10002:
----------------------------------
    Description: 
As a result of GEODE-7997, it was documented that "the persisted data from a 
parallel gateway sender must go to the same disk store as used by the region, 
because parallel gateway sender queues must be colocated with their regions
to operate correctly.".

As stated in the Activity in the original ticket by Dan Smith, "The only issue 
with separating the data into two separate disk stores is that manually 
deleting the files for just one of the disk stores could cause a hang on 
startup looking for the missing disk store. We recommend keeping all of the 
colocated data together."

Given that the current statement in the documentation adds a non compatible 
change to previous versions and also that the given restriction prevents from 
the independent management of the disk used by the region and by the parallel 
gateway sender queues it is proposed to change the statement from an obligation 
to a recommendation giving the reasons for it or completely removing the 
obligation.

  was:
As a result of GEODE-7997, it was documented that "the persisted data from a 
parallel gateway sender must go to the same disk store as used by the region, 
because parallel gateway sender queues must be colocated with their regions
to operate correctly.".

Even though it is true that "parallel gateway sender queues must be colocated 
with their regions to operate correctly", having different disk stores for the 
region and for the parallel gateway sender queues does not prevent them from 
being colocated and therefore to operate correctly.

As stated in the Activity in the original ticket by Dan Smith, "The only issue 
with separating the data into two separate disk stores is that manually 
deleting the files for just one of the disk stores could cause a hang on 
startup looking for the missing disk store. We recommend keeping all of the 
colocated data together."

Given that the current statement in the documentation adds a non compatible 
change to previous versions and also that the given restriction prevents from 
the independent management of the disk used by the region and by the parallel 
gateway sender queues it is proposed to change the statement from an obligation 
to a recommendation giving the reasons for it.


> Remove from documentation obligation for parallel gateway sender to share 
> disk store with region
> ------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-10002
>                 URL: https://issues.apache.org/jira/browse/GEODE-10002
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, wan
>            Reporter: Alberto Gomez
>            Assignee: Alberto Gomez
>            Priority: Major
>              Labels: needsTriage, pull-request-available
>
> As a result of GEODE-7997, it was documented that "the persisted data from a 
> parallel gateway sender must go to the same disk store as used by the region, 
> because parallel gateway sender queues must be colocated with their regions
> to operate correctly.".
> As stated in the Activity in the original ticket by Dan Smith, "The only 
> issue with separating the data into two separate disk stores is that manually 
> deleting the files for just one of the disk stores could cause a hang on 
> startup looking for the missing disk store. We recommend keeping all of the 
> colocated data together."
> Given that the current statement in the documentation adds a non compatible 
> change to previous versions and also that the given restriction prevents from 
> the independent management of the disk used by the region and by the parallel 
> gateway sender queues it is proposed to change the statement from an 
> obligation to a recommendation giving the reasons for it or completely 
> removing the obligation.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to