[jira] [Commented] (SLING-4603) oak-documentMk based discovery.impl
[
https://issues.apache.org/jira/browse/SLING-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491937#comment-14491937
]
Felix Meschberger commented on SLING-4603:
--
See discussion in http://sling.markmail.org/thread/rrodyxlxoiuyx74d
oak-documentMk based discovery.impl
---
Key: SLING-4603
URL: https://issues.apache.org/jira/browse/SLING-4603
Project: Sling
Issue Type: New Feature
Components: Extensions
Reporter: Stefan Egli
Assignee: Stefan Egli
When discovery is used in a stack based on jackrabbit oak as the repository,
the current way of discoving instances somewhat sounds like duplicating work:
oak, or more precisely documentnodestore, itself has a low-level [lease
mechanism|http://jackrabbit.apache.org/oak/docs/nodestore/documentmk.html]
where it stores information about the cluster nodes including a {{leaseEnd}}
indicating at what time others can consider a particular node as
dead/crashed. This corresponds pretty much to the discovery.impl heartbeat
mechanism. And in a stack which is built ontop of oak-documentMk, we could be
making use of this fact and delegate the decision about whether a node in a
cluster is alive or not to the oak layer. Also, with OAK-2597 the relevant
information: {{ActiveClusterNodes}} is nicely exposed via JMX - so that can
become the new source of truth defining the cluster view.
When replacing discovery-owned heartbeats with oak-owned ones, there is one
important detail to be watched out for: it can no longer easily be determined
from another instance in the cluster, whether it has this new discovery
bundle activated or not. Hence it is not given that when a voting happens,
that all {{active}} nodes (as reported by oak-documentMk) are actually going
to respond. So the 'silent instance due to deactivated discovery bundle' case
needs special attention/handling.
Other than that, given the normal case of all {{active}} nodes having the
bundle activated, the voting mechanism can stay the same as in
discovery.impl. The topology connectors can be treated the same too (by
storing announcements to their respective
{{/var/discovery/clusterInstances/slingId/announcements/announcerSlingId}}
node. The properties can be handled the same too (by storing to
{{/properties}} node. Only thing that gets replaced is the {{heartbeats}}.
Note that in order for such an oak-based discovery.impl this oak-lease
mechanism must be very robust (it should be so by its own interest already).
However, there are currently a few issues that should probably first be
resolved until discovery can be based on this: OAK-2739, OAK-2682 and
OAK-2681 are currently known in this area.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
debugger connection tooling broken?
I tried to use an eclipse remote debugger for the first time in a few months and it appears to not be working now. I was using this regularly, so I believe setup is probably OK. (famous last words) Just wondering if anyone else has seen this and if I should file a bug. When I try to connect from eclipse, it initially looks like it¹s working, I see the server added to the debug window, then I get this error dialog: An internal error occurred during: Starting Sling Server (external) at localhost. org/apache/sling/ide/transport/Repository$CommandExecutionFlag and get this in the sling log: 12.04.2015 17:14:26.273 *INFO* [qtp1958698118-46] logs/request.log 12/Apr/2015:17:14:26 -0700 [1] - PROPFIND /server/ HTTP/1.1 12.04.2015 17:14:26.295 *INFO* [qtp1958698118-46] logs/request.log 12/Apr/2015:17:14:26 -0700 [1] - 207 text/xml; charset=UTF-8 22ms 12.04.2015 17:14:26.296 *INFO* [qtp1958698118-46] logs/access.log 10.0.2.2 - admin 12/Apr/2015:17:14:26 -0700 PROPFIND /server/ HTTP/1.1 207 440 http://localhost/; Jakarta Commons-HttpClient/3.1 I know the debug port is setup correctly because can telnet to it, and trigger this Debugger failed to attach: timeout during handshake and: # lsof -p 19346 | grep TCP java19346 root4u IPv4 513679 0t0 TCP *:30303 (LISTEN) java19346 root8u IPv6 511763 0t0 TCP localhost:43545 (LISTEN) java19346 root 145u IPv6 513689 0t0 TCP *:http-alt (LISTEN) I am passing the appropriate debug startup args: 19346 pts/1Sl+0:28 java -Xmx512M -agentlib:jdwp=transport=dt_socket,address=30303,server=y,suspend=n -jar org.apache.sling.launchpad-8-SNAPSHOT-standalone.jar -a 0.0.0.0 start -Bruce
crankstart vs: provisioning-model existing module migration
I¹ve read through the list¹s posts on the provisioning-model, but I¹m missing some fundamentals. What¹s the relationship between crankstart and the provisioning-model? At first glance they appear to provide a similar mechanism to bootstrap a sling configuration, albeit using a slightly different configuration syntax. IIUC, the launchpad now uses provisioning model¹s: launchpad/builder/src/main/provisioning/*.txt files instead of the old: builder/src/main/bundles/list.xml to specify a configuration? Crankstart is run form a jar and loads bundles specified in the file provided on the command line. How is the equivalent provisioning-model started from the command line? Specifically, if the launchpad is now using the provisioning-model, can the config file be specified on the command line ala crankstart, or does one need to build a custom launchpad/builder and bake the startup config into the jar? Or, is *that* the main differentiation, launchpad provides a baked-in startup config whereas crankstart read it from a config file at boot time? Any suggestions for converting over to the provisioning-model for existing contrib modules (like the Sling-S3 module) that were depending on the https://svn.apache.org/repos/asf/sling/trunk/launchpad/builder/src/main/bun dles/list.xml to obtain the default startup configuration? Should this be extracted from launchpad/builder/src/main/provisioning/*.txt now? Or, conversely, could the sling-s3 module be simply be folded into the provisioning model by extending the boot.txt [settings] statement: [settings] sling.run.mode.install.options=jackrabbit,oak|oak_tar,oak_mongo,oak_tar_s3 ,oak_mongo_s3 and providing the additional artifact/runmodes in oak.txt? That seems highly preferable to managing sling-s3 as a separate module from the rest of the provided boot-time config options. I also need to fix the contrib/launchpad/debian package to use this as well. It¹s broken right now without the builder/src/main/bundles/list.xml to use for the bootstrap config. -Bruce
Re: crankstart vs: provisioning-model existing module migration
Hi Bruce, Le 12 avr. 2015 10:25, Bruce Edge bruce.e...@nextissuemedia.com a écrit : .. What¹s the relationship between crankstart and the provisioning-model?... The idea is to convert crankstart to use the provisioning model. I've been busy lately but hoping to find time for that soon, unless someone beats me to it. -Bertrand
[jira] [Resolved] (SLING-4610) Ignore maven-enforcer-plugin and maven-remote-resources-plugin for m2e
[
https://issues.apache.org/jira/browse/SLING-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-4610.
Resolution: Fixed
Fix Version/s: Parent 23
Assignee: Konrad Windszus
Ignore maven-enforcer-plugin and maven-remote-resources-plugin for m2e
--
Key: SLING-4610
URL: https://issues.apache.org/jira/browse/SLING-4610
Project: Sling
Issue Type: Improvement
Components: General
Affects Versions: Parent 22
Reporter: Konrad Windszus
Assignee: Konrad Windszus
Fix For: Parent 23
Currently Eclipse issues the following warnings for a POM referencing
{code}
parent
groupIdorg.apache.sling/groupId
artifactIdsling/artifactId
version22/version
/parent
{code}
{quote}
- maven-enforcer-plugin (goal enforce) is ignored by m2e.
- maven-remote-resources-plugin (goal process) is ignored by m2e.
{quote}
Those executions should be ignored by m2e.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SLING-4610) Ignore maven-enforcer-plugin and maven-remote-resources-plugin for m2e
[
https://issues.apache.org/jira/browse/SLING-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-4610:
---
Priority: Minor (was: Major)
Ignore maven-enforcer-plugin and maven-remote-resources-plugin for m2e
--
Key: SLING-4610
URL: https://issues.apache.org/jira/browse/SLING-4610
Project: Sling
Issue Type: Improvement
Components: General
Affects Versions: Parent 22
Reporter: Konrad Windszus
Assignee: Konrad Windszus
Priority: Minor
Fix For: Parent 23
Currently Eclipse issues the following warnings for a POM referencing
{code}
parent
groupIdorg.apache.sling/groupId
artifactIdsling/artifactId
version22/version
/parent
{code}
{quote}
- maven-enforcer-plugin (goal enforce) is ignored by m2e.
- maven-remote-resources-plugin (goal process) is ignored by m2e.
{quote}
Those executions should be ignored by m2e.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLING-4610) Ignore maven-enforcer-plugin and maven-remote-resources-plugin for m2e
Konrad Windszus created SLING-4610:
--
Summary: Ignore maven-enforcer-plugin and
maven-remote-resources-plugin for m2e
Key: SLING-4610
URL: https://issues.apache.org/jira/browse/SLING-4610
Project: Sling
Issue Type: Improvement
Components: General
Affects Versions: Parent 22
Reporter: Konrad Windszus
Currently Eclipse issues the following warnings for a POM referencing
{code}
parent
groupIdorg.apache.sling/groupId
artifactIdsling/artifactId
version22/version
/parent
{code}
{quote}
- maven-enforcer-plugin (goal enforce) is ignored by m2e.
- maven-remote-resources-plugin (goal process) is ignored by m2e.
{quote}
Those executions should be ignored by m2e.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Jenkins build is unstable: sling-trunk-1.6 #3290
See https://builds.apache.org/job/sling-trunk-1.6/3290/changes
Build failed in Jenkins: sling-trunk-1.8 #970
See https://builds.apache.org/job/sling-trunk-1.8/970/changes Changes: [cziegeler] Add missing licence headers and move model dependencies into models [cziegeler] Refactor slingstart maven plugin: resolve slingstart/slingfeature projects during setup of maven (reactor) project -- [...truncated 53173 lines...] [INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [1.734s] [INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [7.107s] [INFO] Apache Sling Commons Java Compiler SUCCESS [3.425s] [INFO] Apache Sling JSON Library . SUCCESS [3.627s] [INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [24.684s] [INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [2.498s] [INFO] Apache Sling MIME type mapping support SUCCESS [2.684s] [INFO] Apache Sling Commons OSGi support . SUCCESS [2.787s] [INFO] Apache Sling Scheduler Support SUCCESS [2.088s] [INFO] Apache Sling Testing Utilities SUCCESS [10.342s] [INFO] Apache Sling Thread Dumper SUCCESS [1.660s] [INFO] Apache Sling Thread Support ... SUCCESS [1.828s] [INFO] Apache Sling Authentication Service ... SUCCESS [2.947s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [4.874s] [INFO] Apache Sling Engine Implementation SUCCESS [11.627s] [INFO] Apache Sling Repository API Bundle SUCCESS [1.640s] [INFO] Apache Sling Testing JCR Mock . SUCCESS [2.920s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [2.835s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [1.855s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [3.112s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [10.906s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [2.141s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [1.951s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [1.533s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [32.499s] [INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver SUCCESS [20.402s] [INFO] Apache Sling Versioning Integration Tests . SUCCESS [7.171s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [3.147s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [2.438s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [2.911s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [1.701s] [INFO] Apache Sling Oak Repository Server SUCCESS [2.556s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [3:41.082s] [INFO] Apache Sling Servlet Resolver . SUCCESS [3.382s] [INFO] Apache Sling Default GET Servlets . SUCCESS [3.290s] [INFO] Apache Sling Default POST Servlets SUCCESS [3.557s] [INFO] Apache Sling Compat Servlets .. SUCCESS [1.726s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [1.629s] [INFO] Apache Sling Scripting Core implementation SUCCESS [10.073s] [INFO] Apache Sling Scripting JavaScript Support . SUCCESS [8.116s] [INFO] Apache Sling Scripting JSP Support SUCCESS [4.777s] [INFO] Apache Sling JSP Tag Library .. SUCCESS [4.007s] [INFO] Apache Sling JSP Standard Tag Library . SUCCESS [1.772s] [INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [2.708s] [INFO] Apache Sling Bundle Resource Provider . SUCCESS [1.742s] [INFO] Apache Sling Distributed Event Admin .. SUCCESS [4.057s] [INFO] Apache Sling Discovery API SUCCESS [1.595s] [INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [4:32.364s] [INFO] Apache Sling Discovery Support Bundle . SUCCESS [1.679s] [INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [1.664s] [INFO] Apache Sling Event Support SUCCESS [10:49.718s] [INFO] Apache Sling Feature Flags SUCCESS [1.791s] [INFO] Apache Sling Filesystem Resource Provider . SUCCESS [1.798s] [INFO] Apache Sling javax.activation bundle .. SUCCESS [1.812s] [INFO] Apache Sling Service User Mapper .. SUCCESS [2.585s] [INFO] Apache Sling Settings . SUCCESS [2.506s] [INFO] Apache Sling Web Console Branding . SUCCESS [1.535s] [INFO] Apache Sling Web Console Security Provider SUCCESS [1.831s] [INFO] Apache Sling Explorer . SUCCESS [1.677s] [INFO] Apache Sling Health Check Core SUCCESS [7.198s] [INFO] Apache Sling Health Check
Jenkins build is unstable: sling-trunk-1.8 #971
See https://builds.apache.org/job/sling-trunk-1.8/971/changes
Jenkins build is still unstable: sling-oak-it-1.6 #469
See https://builds.apache.org/job/sling-oak-it-1.6/changes
Jenkins build is still unstable: sling-oak-it-1.7 #25
See https://builds.apache.org/job/sling-oak-it-1.7/changes
Jenkins build became unstable: sling-trunk-1.7 #1683
See https://builds.apache.org/job/sling-trunk-1.7/1683/changes
Re: Using the provisioning model
Another update :) I refactored the maven plugin and rewrote the dependency handling and this seems to have solved the reactor build problem. At least on my machine everything is running fine now. The Jenkins builds will take some cycles until they pick up the most recent code. It seems the jenkins 1.6 oak job is failing. Not sure if that one worked before the changes? Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Jenkins build is still unstable: sling-trunk-1.6 #3291
See https://builds.apache.org/job/sling-trunk-1.6/changes
Build failed in Jenkins: sling-trunk-1.7 #1684
See https://builds.apache.org/job/sling-trunk-1.7/1684/changes Changes: [cziegeler] Enable integration tests again -- [...truncated 49941 lines...] [INFO] Apache Sling Authentication Service ... SUCCESS [3.059s] [INFO] Apache Sling Form Based Authentication Handler SUCCESS [5.211s] [INFO] Apache Sling Engine Implementation SUCCESS [13.892s] [INFO] Apache Sling Repository API Bundle SUCCESS [1.760s] [INFO] Apache Sling Testing JCR Mock . SUCCESS [2.980s] [INFO] Apache Sling JCR Base Bundle .. SUCCESS [2.982s] [INFO] Apache Sling JCR ClassLoader .. SUCCESS [2.052s] [INFO] Apache Sling Initial Content Loader ... SUCCESS [3.315s] [INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [12.790s] [INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [2.583s] [INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support SUCCESS [2.004s] [INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [1.693s] [INFO] Apache Sling JCR Resource Resolver SUCCESS [32.261s] [INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver SUCCESS [12.529s] [INFO] Apache Sling Versioning Integration Tests . SUCCESS [8.410s] [INFO] Apache Sling JCR Repository Registration .. SUCCESS [3.548s] [INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [2.655s] [INFO] Apache Sling DavEx Access to repositories . SUCCESS [3.061s] [INFO] Apache Sling JCR WebConsole Bundle SUCCESS [1.909s] [INFO] Apache Sling Oak Repository Server SUCCESS [2.753s] [INFO] Apache Sling SlingRepository Integration Tests SUCCESS [49.503s] [INFO] Apache Sling Servlet Resolver . SUCCESS [3.574s] [INFO] Apache Sling Default GET Servlets . SUCCESS [3.807s] [INFO] Apache Sling Default POST Servlets SUCCESS [3.705s] [INFO] Apache Sling Compat Servlets .. SUCCESS [1.896s] [INFO] Apache Sling Scripting Implementation API . SUCCESS [1.728s] [INFO] Apache Sling Scripting Core implementation SUCCESS [10.361s] [INFO] Apache Sling Scripting JavaScript Support . SUCCESS [9.120s] [INFO] Apache Sling Scripting JSP Support SUCCESS [4.991s] [INFO] Apache Sling JSP Tag Library .. SUCCESS [4.162s] [INFO] Apache Sling JSP Standard Tag Library . SUCCESS [1.855s] [INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [2.662s] [INFO] Apache Sling Bundle Resource Provider . SUCCESS [1.780s] [INFO] Apache Sling Distributed Event Admin .. SUCCESS [4.410s] [INFO] Apache Sling Discovery API SUCCESS [1.741s] [INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [4:30.319s] [INFO] Apache Sling Discovery Support Bundle . SUCCESS [1.841s] [INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [1.864s] [INFO] Apache Sling Event Support SUCCESS [11:47.733s] [INFO] Apache Sling Feature Flags SUCCESS [1.886s] [INFO] Apache Sling Filesystem Resource Provider . SUCCESS [2.051s] [INFO] Apache Sling javax.activation bundle .. SUCCESS [1.841s] [INFO] Apache Sling Service User Mapper .. SUCCESS [2.699s] [INFO] Apache Sling Settings . SUCCESS [2.623s] [INFO] Apache Sling Web Console Branding . SUCCESS [1.603s] [INFO] Apache Sling Web Console Security Provider SUCCESS [1.903s] [INFO] Apache Sling Explorer . SUCCESS [1.847s] [INFO] Apache Sling Health Check Core SUCCESS [6.472s] [INFO] Apache Sling Health Check Annotations . SUCCESS [1.707s] [INFO] Apache Sling Health Check Samples . SUCCESS [2.688s] [INFO] Apache Sling Health Check Support Components .. SUCCESS [3.080s] [INFO] Apache Sling Health Check Webconsole Plugin ... SUCCESS [1.873s] [INFO] Apache Sling Health Check JUnit Bridge SUCCESS [2.533s] [INFO] Apache Sling Health Check Integration Tests ... SUCCESS [25.485s] [INFO] Apache Sling Health Check Reactor POM . SUCCESS [1.036s] [INFO] Apache Sling Resource Access Security . SUCCESS [2.019s] [INFO] Apache Sling Resource Access Security Integration Tests SUCCESS [21.812s] [INFO] Apache Sling Validation Framework API . SUCCESS [1.718s] [INFO] Apache Sling Validation Framework Core Implementation SUCCESS [10.297s] [INFO] Apache Sling Validation Framework Testing Services SUCCESS [2.060s] [INFO] Apache Sling Validation Framework Integration Tests SUCCESS [19.943s] [INFO] Apache Sling Validation Framework Examples SUCCESS [1.907s] [INFO] Apache Sling Validation
Jenkins build is still unstable: sling-trunk-1.6 #3292
See https://builds.apache.org/job/sling-trunk-1.6/changes
Jenkins build is back to normal : sling-trunk-1.7 #1685
See https://builds.apache.org/job/sling-trunk-1.7/1685/changes
Jenkins build is still unstable: sling-trunk-1.6 #3293
See https://builds.apache.org/job/sling-trunk-1.6/changes
