Re: Job Distribution

Hi, There are various options here: you could distribute the 'queue chiefs' via some hashing amongst all instances in the cluster view, and reassign those chiefs upon a topology change. Or you could let the leader explicitly send a 'become-chief' job/command to particular instances that would

[jira] [Created] (SLING-5058) introduce viewCnt to ./establishedView to be able to detect missing changes

Stefan Egli created SLING-5058: -- Summary: introduce viewCnt to ./establishedView to be able to detect missing changes Key: SLING-5058 URL: https://issues.apache.org/jira/browse/SLING-5058 Project: Sling

[jira] [Commented] (SLING-5030) replace isolated mode with (larger) TOPOLOGY_CHANGING phase

[ https://issues.apache.org/jira/browse/SLING-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14906162#comment-14906162 ] Stefan Egli commented on SLING-5030: Added a follow-up ticket SLING-5058 that would go even further

[jira] [Updated] (SLING-5058) introduce viewCnt to ./establishedView to be able to detect missing changes

[ https://issues.apache.org/jira/browse/SLING-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5058: --- Priority: Minor (was: Major) > introduce viewCnt to ./establishedView to be able to detect missing

[jira] [Resolved] (SLING-5057) Support HttpServletRequest#getRemoteUser

[ https://issues.apache.org/jira/browse/SLING-5057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5057. Resolution: Fixed Fixed in https://svn.apache.org/r1705021 > Support

[jira] [Resolved] (SLING-5059) PathNotFound in voting.toString() in test

[ https://issues.apache.org/jira/browse/SLING-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-5059. Resolution: Fixed fixed in http://svn.apache.org/viewvc?rev=1705026=rev > PathNotFound in

[jira] [Updated] (SLING-5061) [HApi] HApiType.getUrl() should be an absolute URL

[ https://issues.apache.org/jira/browse/SLING-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Dulvac updated SLING-5061: - Attachment: SLING-5061.git.patch Attached patch. Can be applied with patch -p0 -i

[jira] [Created] (SLING-5060) use virtual clock for discovery tests

Stefan Egli created SLING-5060: -- Summary: use virtual clock for discovery tests Key: SLING-5060 URL: https://issues.apache.org/jira/browse/SLING-5060 Project: Sling Issue Type: Test

[jira] [Created] (SLING-5057) Support HttpServletRequest#getRemoteUser

Robert Munteanu created SLING-5057: -- Summary: Support HttpServletRequest#getRemoteUser Key: SLING-5057 URL: https://issues.apache.org/jira/browse/SLING-5057 Project: Sling Issue Type: Bug

[jira] [Created] (SLING-5059) PathNotFound in voting.toString() in test

Stefan Egli created SLING-5059: -- Summary: PathNotFound in voting.toString() in test Key: SLING-5059 URL: https://issues.apache.org/jira/browse/SLING-5059 Project: Sling Issue Type: Bug

Re: Job Distribution

Am 24.09.15 um 10:45 schrieb Stefan Egli: > Hi, > > There are various options here: you could distribute the 'queue chiefs' > via some hashing amongst all instances in the cluster view, and reassign > those chiefs upon a topology change. Or you could let the leader > explicitly send a

[jira] [Commented] (SLING-5030) replace isolated mode with (larger) TOPOLOGY_CHANGING phase

[ https://issues.apache.org/jira/browse/SLING-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14906157#comment-14906157 ] Stefan Egli commented on SLING-5030: Done #2 in http://svn.apache.org/viewvc?rev=1705024=rev >

[jira] [Created] (SLING-5061) [HApi] HApiType.getUrl() should be an absolute URL

Andrei Dulvac created SLING-5061: Summary: [HApi] HApiType.getUrl() should be an absolute URL Key: SLING-5061 URL: https://issues.apache.org/jira/browse/SLING-5061 Project: Sling Issue Type:

Re: Job Distribution

Hi Julian, I think that makes sense, it just adds one indirection on determining who will be processing ordered queues - but that shouldn't pose a problem. Regards Carsten Am 24.09.15 um 09:53 schrieb Julian Sedding: > Hi all > > I was looking into the following deployment scenario recently: >

Job Distribution

Hi all I was looking into the following deployment scenario recently: - Oak Mongo with 4 attached, clustered Sling nodes - 2 nodes to be used to render the HTML UI - 2 nodes to be used for background processing The motivation was to remove background load from the rendering nodes in order to

[jira] [Assigned] (SLING-5056) FAILED distribution response states are reported as succesful

[ https://issues.apache.org/jira/browse/SLING-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria reassigned SLING-5056: Assignee: Marius Petria > FAILED distribution response states are reported as succesful >

[jira] [Resolved] (SLING-5056) FAILED distribution response states are reported as succesful

[ https://issues.apache.org/jira/browse/SLING-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria resolved SLING-5056. -- Resolution: Fixed Committed revision 1705041. Fixed by returning isSuccesful only for

[jira] [Commented] (SLING-5030) replace isolated mode with (larger) TOPOLOGY_CHANGING phase

[ https://issues.apache.org/jira/browse/SLING-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14906370#comment-14906370 ] Stefan Egli commented on SLING-5030: and improved a log output at

[jira] [Updated] (SLING-5056) FAILED distribution response states are reported as succesful

[ https://issues.apache.org/jira/browse/SLING-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria updated SLING-5056: - Fix Version/s: Content Distribution Core 0.1.8 > FAILED distribution response states are reported

[jira] [Commented] (SLING-5030) replace isolated mode with (larger) TOPOLOGY_CHANGING phase

[ https://issues.apache.org/jira/browse/SLING-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14906352#comment-14906352 ] Stefan Egli commented on SLING-5030: Plus improved the webconsole: when it is isolated it's not

[jira] [Commented] (SLING-5030) replace isolated mode with (larger) TOPOLOGY_CHANGING phase

[ https://issues.apache.org/jira/browse/SLING-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14906290#comment-14906290 ] Stefan Egli commented on SLING-5030: Couple test, buglet fixed: *

Re: [VOTE] Release o.a.s.junit.core 1.0.12 and o.a.s.junit.teleporter 1.0.2

On Wed, Sep 23, 2015 at 6:40 PM, Bertrand Delacretaz wrote: > > Please vote to approve this release: +1 Robert

[jira] [Commented] (SLING-5030) replace isolated mode with (larger) TOPOLOGY_CHANGING phase

[ https://issues.apache.org/jira/browse/SLING-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14906406#comment-14906406 ] Stefan Egli commented on SLING-5030: and ensure delayedEventPendingFailed is always correctly set

[jira] [Resolved] (SLING-5030) replace isolated mode with (larger) TOPOLOGY_CHANGING phase

[ https://issues.apache.org/jira/browse/SLING-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-5030. Resolution: Fixed marking resolved, tests look fine. > replace isolated mode with (larger)

[VOTE] Release Apache Sling discovery.impl 1.1.8

Hi, We solved 14 issues in this release (7 of them test related only): https://issues.apache.org/jira/browse/SLING/fixforversion/12332770 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1335/ You can use this UNIX script to download the release and verify

Re: [VOTE] Release Apache Sling discovery.impl 1.1.8

+1 Cheers, Stefan On 24/09/15 17:09, "Stefan Egli" wrote: >Hi, > >We solved 14 issues in this release (7 of them test related only): >https://issues.apache.org/jira/browse/SLING/fixforversion/12332770 > >Staging repository:

Re: [VOTE] Release Apache Sling discovery.impl 1.1.8

+1 Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

Re: [VOTE] Release o.a.s.junit.core 1.0.12 and o.a.s.junit.teleporter 1.0.2

On Thu, Sep 24, 2015 at 7:33 AM, Carsten Ziegeler wrote: > ...Just curious what happened to teleporter 1.0.0?... I messed up that release...my usual pattern is that I copy the info from another pom, forget to adapt it, it's wrong at release time and the release plugin gets

New Sling Sitebuilder proof of concept demo video

Hello, as announced in my adaptTo() 2014 talk I worked on creating a CMS. What I've got now is a proof of concept for a Sling Sitebuilder and a frontend component API. To see it in action and get an understanding of how it works I created a demo video that you can find here (available in

[jira] [Updated] (SLING-5062) Apache Sling Distribution Core bundle installation is not successful.

[ https://issues.apache.org/jira/browse/SLING-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ganesh updated SLING-5062: - Attachment: ScreenShot1.png ScreenShot2.png Screen shots with the errors in

[jira] [Created] (SLING-5062) Apache Sling Distribution Core bundle installation is not successful.

Venkat Ganesh created SLING-5062: Summary: Apache Sling Distribution Core bundle installation is not successful. Key: SLING-5062 URL: https://issues.apache.org/jira/browse/SLING-5062 Project: Sling

[jira] [Commented] (SLING-5062) Apache Sling Distribution Core bundle installation is not successful.

[ https://issues.apache.org/jira/browse/SLING-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14907298#comment-14907298 ] Venkat Ganesh commented on SLING-5062: -- I saw this error in the console: Attempting to load