[jira] [Commented] (OAK-8280) [Direct Binary Access] Allow client to veto use of CDN URI

2022-11-17 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635380#comment-17635380
 ] 

Julian Reschke commented on OAK-8280:
-

trunk: (1.22.0) 
[9c2e20564e|https://github.com/apache/jackrabbit-oak/commit/9c2e20564ef859fbd5405f7021e8c973195df72f]
1.22: (1.22.0) 
[9c2e20564e|https://github.com/apache/jackrabbit-oak/commit/9c2e20564ef859fbd5405f7021e8c973195df72f]

> [Direct Binary Access] Allow client to veto use of CDN URI
> --
>
> Key: OAK-8280
> URL: https://issues.apache.org/jira/browse/OAK-8280
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: blob-cloud, blob-cloud-azure
>Affects Versions: 1.20.0
>Reporter: Matt Ryan
>Assignee: Matt Ryan
>Priority: Major
> Fix For: 1.22.0
>
>
> As we learned in OAK-7702, using signed CDN URIs usually offers improved 
> throughput, but not always.  Implementing this issue would mean that we 
> extend the API to allow a client to indicate that they do not want the CDN 
> URI, even if a CDN is configured, because the client somehow knows that the 
> non-CDN URI will be better.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (OAK-8280) [Direct Binary Access] Allow client to veto use of CDN URI

2020-01-19 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018851#comment-17018851
 ] 

Julian Reschke commented on OAK-8280:
-

bq. Yeah the baseline plugin complained.

Understood. But should this be part of the public exported API? Otherwise we 
should suppress the export of the package...

> [Direct Binary Access] Allow client to veto use of CDN URI
> --
>
> Key: OAK-8280
> URL: https://issues.apache.org/jira/browse/OAK-8280
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: blob-cloud, blob-cloud-azure
>Affects Versions: 1.20.0
>Reporter: Matt Ryan
>Assignee: Matt Ryan
>Priority: Major
> Fix For: 1.22.0
>
>
> As we learned in OAK-7702, using signed CDN URIs usually offers improved 
> throughput, but not always.  Implementing this issue would mean that we 
> extend the API to allow a client to indicate that they do not want the CDN 
> URI, even if a CDN is configured, because the client somehow knows that the 
> non-CDN URI will be better.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OAK-8280) [Direct Binary Access] Allow client to veto use of CDN URI

2020-01-09 Thread Matt Ryan (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012449#comment-17012449
 ] 

Matt Ryan commented on OAK-8280:


Yeah the baseline plugin complained.

> [Direct Binary Access] Allow client to veto use of CDN URI
> --
>
> Key: OAK-8280
> URL: https://issues.apache.org/jira/browse/OAK-8280
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: blob-cloud, blob-cloud-azure
>Affects Versions: 1.20.0
>Reporter: Matt Ryan
>Assignee: Matt Ryan
>Priority: Major
> Fix For: 1.22.0
>
>
> As we learned in OAK-7702, using signed CDN URIs usually offers improved 
> throughput, but not always.  Implementing this issue would mean that we 
> extend the API to allow a client to indicate that they do not want the CDN 
> URI, even if a CDN is configured, because the client somehow knows that the 
> non-CDN URI will be better.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OAK-8280) [Direct Binary Access] Allow client to veto use of CDN URI

2020-01-09 Thread Marcel Reutegger (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011603#comment-17011603
 ] 

Marcel Reutegger commented on OAK-8280:
---

Looks good to me, but would be good to have someone review it that knows this 
area better than me.

The only thing I noticed, package 
{{org.apache.jackrabbit.oak.plugins.blob.datastore.directaccess}} gets a 
package-info.java. Does it need one and why is it different from the other two 
exported packages? Did the baseline plugin complain and the package should 
rather be added to the list of filtered packages of the baseline plugin in 
oak-parent/pom.xml?

> [Direct Binary Access] Allow client to veto use of CDN URI
> --
>
> Key: OAK-8280
> URL: https://issues.apache.org/jira/browse/OAK-8280
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: blob-cloud, blob-cloud-azure
>Reporter: Matt Ryan
>Assignee: Matt Ryan
>Priority: Major
>
> As we learned in OAK-7702, using signed CDN URIs usually offers improved 
> throughput, but not always.  Implementing this issue would mean that we 
> extend the API to allow a client to indicate that they do not want the CDN 
> URI, even if a CDN is configured, because the client somehow knows that the 
> non-CDN URI will be better.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OAK-8280) [Direct Binary Access] Allow client to veto use of CDN URI

2019-12-03 Thread Matt Ryan (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987512#comment-16987512
 ] 

Matt Ryan commented on OAK-8280:


The proposed changes can be reviewed here:  
https://github.com/apache/jackrabbit-oak/pull/162

This adds the ability for a client to specify to ignore the domain override 
when generating direct access upload or download URIs.  The use case (mentioned 
as something needed before) is that sometimes a client may have enough 
knowledge to know that certain requested URIs will result in faster throughput 
if the domain override is not used.  An example is a third-party VM running as 
a service in the same cloud region as where the blob storage is, which based on 
my testing (at least with Azure) gives many times faster access time if going 
direct to storage using the default domain rather than using a CDN domain 
(which would be faster for clients not within the Azure region).  With this 
change the client can request signed URIs that do not apply any domain 
override, if one is configured.

> [Direct Binary Access] Allow client to veto use of CDN URI
> --
>
> Key: OAK-8280
> URL: https://issues.apache.org/jira/browse/OAK-8280
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: blob-cloud, blob-cloud-azure
>Reporter: Matt Ryan
>Priority: Major
>
> As we learned in OAK-7702, using signed CDN URIs usually offers improved 
> throughput, but not always.  Implementing this issue would mean that we 
> extend the API to allow a client to indicate that they do not want the CDN 
> URI, even if a CDN is configured, because the client somehow knows that the 
> non-CDN URI will be better.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (OAK-8280) [Direct Binary Access] Allow client to veto use of CDN URI

2019-04-25 Thread Matt Ryan (JIRA)


[ 
https://issues.apache.org/jira/browse/OAK-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826477#comment-16826477
 ] 

Matt Ryan commented on OAK-8280:


The exception case is when the client requesting a URI is running on a VM for a 
cloud provider in the same region as where the blob storage is.  This is true 
at least for Azure - if running on an Azure VM in the same region as the blob 
storage, the best performance for downloading a signed URI is to use a non-CDN 
URI in that particular case.

In discussion with others on the Oak team, while we recognize that the testing 
results showed better performance, it is one edge case and may not be 
applicable in real-world scenarios.  Most use cases are either web clients 
requesting the URIs (which could be anywhere but are almost certainly not 
running in a cloud VM), or external services which could also be running 
anywhere.  An application built on top of the Oak repository would have no 
purpose in requesting the signed URI, because it is running in the same VM 
anyway and this doesn't improve the I/O usage of that application.  So it would 
be hard for a client to know for sure that the specific binary it needs to 
request is in the same region and also be the case that the client has a reason 
to request a signed URI for that binary.

Until we come up with a reasonable use case this is probably on hold.

> [Direct Binary Access] Allow client to veto use of CDN URI
> --
>
> Key: OAK-8280
> URL: https://issues.apache.org/jira/browse/OAK-8280
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: blob-cloud, blob-cloud-azure
>Reporter: Matt Ryan
>Priority: Major
>
> As we learned in OAK-7702, using signed CDN URIs usually offers improved 
> throughput, but not always.  Implementing this issue would mean that we 
> extend the API to allow a client to indicate that they do not want the CDN 
> URI, even if a CDN is configured, because the client somehow knows that the 
> non-CDN URI will be better.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OAK-8280) [Direct Binary Access] Allow client to veto use of CDN URI

2019-04-25 Thread Matt Ryan (JIRA)


[ 
https://issues.apache.org/jira/browse/OAK-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826473#comment-16826473
 ] 

Matt Ryan commented on OAK-8280:


See 
https://issues.apache.org/jira/browse/OAK-7702?focusedCommentId=16826464=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16826464.

> [Direct Binary Access] Allow client to veto use of CDN URI
> --
>
> Key: OAK-8280
> URL: https://issues.apache.org/jira/browse/OAK-8280
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: blob-cloud, blob-cloud-azure
>Reporter: Matt Ryan
>Priority: Major
>
> As we learned in OAK-7702, using signed CDN URIs usually offers improved 
> throughput, but not always.  Implementing this issue would mean that we 
> extend the API to allow a client to indicate that they do not want the CDN 
> URI, even if a CDN is configured, because the client somehow knows that the 
> non-CDN URI will be better.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)