[jira] [Commented] (OAK-5262) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 failed
[ https://issues.apache.org/jira/browse/OAK-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737363#comment-15737363 ] Hudson commented on OAK-5262: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 failed > - > > Key: OAK-5262 > URL: https://issues.apache.org/jira/browse/OAK-5262 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting > #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1322/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5270) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1323 failed
[ https://issues.apache.org/jira/browse/OAK-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737358#comment-15737358 ] Hudson commented on OAK-5270: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1323 failed > - > > Key: OAK-5270 > URL: https://issues.apache.org/jira/browse/OAK-5270 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1323 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting > #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1323/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5269) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1323 failed
[ https://issues.apache.org/jira/browse/OAK-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737349#comment-15737349 ] Hudson commented on OAK-5269: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1323 failed > -- > > Key: OAK-5269 > URL: https://issues.apache.org/jira/browse/OAK-5269 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1323 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting > #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1323/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5263) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 failed
[ https://issues.apache.org/jira/browse/OAK-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737323#comment-15737323 ] Hudson commented on OAK-5263: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 failed > > > Key: OAK-5263 > URL: https://issues.apache.org/jira/browse/OAK-5263 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting > #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1322/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5267) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 failed
[ https://issues.apache.org/jira/browse/OAK-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737316#comment-15737316 ] Hudson commented on OAK-5267: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 failed > > > Key: OAK-5267 > URL: https://issues.apache.org/jira/browse/OAK-5267 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting > #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1323/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5264) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 failed
[ https://issues.apache.org/jira/browse/OAK-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737308#comment-15737308 ] Hudson commented on OAK-5264: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 failed > --- > > Key: OAK-5264 > URL: https://issues.apache.org/jira/browse/OAK-5264 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting > #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5266) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1323 failed
[ https://issues.apache.org/jira/browse/OAK-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737303#comment-15737303 ] Hudson commented on OAK-5266: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1323 failed > --- > > Key: OAK-5266 > URL: https://issues.apache.org/jira/browse/OAK-5266 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1323 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting > #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1323/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5265) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 failed
[ https://issues.apache.org/jira/browse/OAK-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737305#comment-15737305 ] Hudson commented on OAK-5265: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 failed > --- > > Key: OAK-5265 > URL: https://issues.apache.org/jira/browse/OAK-5265 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting > #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5268) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 failed
[ https://issues.apache.org/jira/browse/OAK-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737304#comment-15737304 ] Hudson commented on OAK-5268: - Build is still failing. Failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 failed > > > Key: OAK-5268 > URL: https://issues.apache.org/jira/browse/OAK-5268 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting > #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1323/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5261) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 failed
[ https://issues.apache.org/jira/browse/OAK-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737302#comment-15737302 ] Hudson commented on OAK-5261: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1324|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1324/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1324/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 failed > > > Key: OAK-5261 > URL: https://issues.apache.org/jira/browse/OAK-5261 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting > #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1322/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5262) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 failed
[ https://issues.apache.org/jira/browse/OAK-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737268#comment-15737268 ] Hudson commented on OAK-5262: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1323/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 failed > - > > Key: OAK-5262 > URL: https://issues.apache.org/jira/browse/OAK-5262 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting > #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1322/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5270) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1323 failed
Hudson created OAK-5270: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1323 failed Key: OAK-5270 URL: https://issues.apache.org/jira/browse/OAK-5270 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1323 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5269) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1323 failed
Hudson created OAK-5269: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1323 failed Key: OAK-5269 URL: https://issues.apache.org/jira/browse/OAK-5269 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1323 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_MK,profile=integrationTesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_MK,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5263) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 failed
[ https://issues.apache.org/jira/browse/OAK-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737234#comment-15737234 ] Hudson commented on OAK-5263: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1323/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 failed > > > Key: OAK-5263 > URL: https://issues.apache.org/jira/browse/OAK-5263 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 > (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting > #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1322/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5268) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 failed
Hudson created OAK-5268: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 failed Key: OAK-5268 URL: https://issues.apache.org/jira/browse/OAK-5268 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5261) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 failed
[ https://issues.apache.org/jira/browse/OAK-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15737227#comment-15737227 ] Hudson commented on OAK-5261: - Previously failing build now is OK. Passed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1323/console] > Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 failed > > > Key: OAK-5261 > URL: https://issues.apache.org/jira/browse/OAK-5261 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson > > Jenkins CI failure: > https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ > The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 > (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 has failed. > First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK > 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting > #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1322/] > [console > log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5267) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 failed
Hudson created OAK-5267: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 failed Key: OAK-5267 URL: https://issues.apache.org/jira/browse/OAK-5267 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5266) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1323 failed
Hudson created OAK-5266: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1323 failed Key: OAK-5266 URL: https://issues.apache.org/jira/browse/OAK-5266 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1323 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5265) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 failed
Hudson created OAK-5265: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 failed Key: OAK-5265 URL: https://issues.apache.org/jira/browse/OAK-5265 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5264) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 failed
Hudson created OAK-5264: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 failed Key: OAK-5264 URL: https://issues.apache.org/jira/browse/OAK-5264 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting #1323|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=SEGMENT_TAR,profile=integrationTesting/1323/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5263) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 failed
Hudson created OAK-5263: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 failed Key: OAK-5263 URL: https://issues.apache.org/jira/browse/OAK-5263 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_NS,profile=unittesting #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1322/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_NS,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5262) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 failed
Hudson created OAK-5262: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 failed Key: OAK-5262 URL: https://issues.apache.org/jira/browse/OAK-5262 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.7 (latest),nsfixtures=DOCUMENT_RDB,profile=unittesting #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1322/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.7%20(latest),nsfixtures=DOCUMENT_RDB,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OAK-5261) Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 failed
Hudson created OAK-5261: --- Summary: Build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 failed Key: OAK-5261 URL: https://issues.apache.org/jira/browse/OAK-5261 Project: Jackrabbit Oak Issue Type: Bug Components: continuous integration Reporter: Hudson Jenkins CI failure: https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/ The build Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322 has failed. First failed run: [Apache Jackrabbit Oak matrix/Ubuntu Slaves=ubuntu,jdk=JDK 1.8 (latest),nsfixtures=SEGMENT_TAR,profile=unittesting #1322|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1322/] [console log|https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/Ubuntu%20Slaves=ubuntu,jdk=JDK%201.8%20(latest),nsfixtures=SEGMENT_TAR,profile=unittesting/1322/console] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
[
https://issues.apache.org/jira/browse/OAK-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736014#comment-15736014
]
Julian Sedding edited comment on OAK-5260 at 12/9/16 7:03 PM:
--
Attached is a new [patch with a fix|^OAK-5260-jsedding.patch], the test case
provided by [~bdelacretaz] (thanks!) and an additional test case closer to the
root of the issue.
[~reschke], [~mduerig], [~mreutegg], [~tmueller] could any of you please review
the change? It is only a few lines, but pretty deep down.
was (Author: jsedding):
Attached is a new [patch with a fix|^OAK-5260-jsedding.patch], the test case
provided by [~bdelacretaz] (thanks!) and an additional test case closer to the
root of the issue.
> Incorrect handling of subpaths with leading left curly bracket
> --
>
> Key: OAK-5260
> URL: https://issues.apache.org/jira/browse/OAK-5260
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Bertrand Delacretaz
>Assignee: Julian Sedding
> Attachments: OAK-5260-jsedding.patch, OAK-5260.patch
>
>
> As per SLING-6383 it looks like the Oak name mapping causes for example
> getItem("/libs/{sub") (with a left curly bracket in the path) to return the
> /libs node if that exists but the supplied path does not.
> I'll attach a patch with a test that demonstrates this.
> [~fmeschbe] mentions in that Sling issue that the parsing of the CR 2 section
> 3.2.5.1 Expanded Form could be involved, treating the left curly bracket in a
> special way that's not appropriate here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
[
https://issues.apache.org/jira/browse/OAK-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15736014#comment-15736014
]
Julian Sedding edited comment on OAK-5260 at 12/9/16 6:57 PM:
--
Attached is a new [patch with a fix|^OAK-5260-jsedding.patch], the test case
provided by [~bdelacretaz] (thanks!) and an additional test case closer to the
root of the issue.
was (Author: jsedding):
Attached is a new patch with a fix, the test case provided by [~bdelacretaz]
(thanks!) and an additional test case closer to the root of the issue.
> Incorrect handling of subpaths with leading left curly bracket
> --
>
> Key: OAK-5260
> URL: https://issues.apache.org/jira/browse/OAK-5260
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Bertrand Delacretaz
>Assignee: Julian Sedding
> Attachments: OAK-5260-jsedding.patch, OAK-5260.patch
>
>
> As per SLING-6383 it looks like the Oak name mapping causes for example
> getItem("/libs/{sub") (with a left curly bracket in the path) to return the
> /libs node if that exists but the supplied path does not.
> I'll attach a patch with a test that demonstrates this.
> [~fmeschbe] mentions in that Sling issue that the parsing of the CR 2 section
> 3.2.5.1 Expanded Form could be involved, treating the left curly bracket in a
> special way that's not appropriate here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
[
https://issues.apache.org/jira/browse/OAK-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding reassigned OAK-5260:
---
Assignee: Julian Sedding
> Incorrect handling of subpaths with leading left curly bracket
> --
>
> Key: OAK-5260
> URL: https://issues.apache.org/jira/browse/OAK-5260
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Bertrand Delacretaz
>Assignee: Julian Sedding
> Attachments: OAK-5260-jsedding.patch, OAK-5260.patch
>
>
> As per SLING-6383 it looks like the Oak name mapping causes for example
> getItem("/libs/{sub") (with a left curly bracket in the path) to return the
> /libs node if that exists but the supplied path does not.
> I'll attach a patch with a test that demonstrates this.
> [~fmeschbe] mentions in that Sling issue that the parsing of the CR 2 section
> 3.2.5.1 Expanded Form could be involved, treating the left curly bracket in a
> special way that's not appropriate here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
[
https://issues.apache.org/jira/browse/OAK-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated OAK-5260:
Attachment: OAK-5260-jsedding.patch
Attached is a new patch with a fix, the test case provided by [~bdelacretaz]
(thanks!) and an additional test case closer to the root of the issue.
> Incorrect handling of subpaths with leading left curly bracket
> --
>
> Key: OAK-5260
> URL: https://issues.apache.org/jira/browse/OAK-5260
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Bertrand Delacretaz
> Attachments: OAK-5260-jsedding.patch, OAK-5260.patch
>
>
> As per SLING-6383 it looks like the Oak name mapping causes for example
> getItem("/libs/{sub") (with a left curly bracket in the path) to return the
> /libs node if that exists but the supplied path does not.
> I'll attach a patch with a test that demonstrates this.
> [~fmeschbe] mentions in that Sling issue that the parsing of the CR 2 section
> 3.2.5.1 Expanded Form could be involved, treating the left curly bracket in a
> special way that's not appropriate here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OAK-4069) Use read concern majority when connected to a replica set
[
https://issues.apache.org/jira/browse/OAK-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735409#comment-15735409
]
Tomek Rękawek edited comment on OAK-4069 at 12/9/16 3:24 PM:
-
Benchmark results:
{noformat}
# ConcurrentWriteReadTest C min 10% 50% 90% max
N
readconcern=majority latency=0 1 78 108 184 4921430
1061
readconcern=locallatency=0 1 87 110 193 4911244
1029
readconcern=majority latency=100 1 727 777100511631298
303
readconcern=locallatency=100 1 720 779 99611981368
301
{noformat}
I used the [local replica|https://github.com/trekawek/global-mongo]. Benchmark
invocation:
{noformat}
$ java -Druntime=300 -jar oak-run/target/oak-run-1.6-SNAPSHOT.jar benchmark
ConcurrentWriteReadTest Oak-Mongo \
--mongouri
'mongodb://mongo1:27017,mongo2:27018,mongo3:27019/oak?w=majority=nearest=majority'
{noformat}
was (Author: tomek.rekawek):
Benchmark results:
{noformat}
# ConcurrentWriteReadTest C min 10% 50% 90% max
N
Oak-Mongo (readconcern=majority) 1 78 108 184 4921430
1061
Oak-Mongo (readconcern=local) 1 87 110 193 4911244
1029
{noformat}
I used the [local replica|https://github.com/trekawek/global-mongo] set with
latency=0. Benchmark invocation:
{noformat}
$ java -Druntime=300 -jar oak-run/target/oak-run-1.6-SNAPSHOT.jar benchmark
ConcurrentWriteReadTest Oak-Mongo \
--mongouri
'mongodb://mongo1:27017,mongo2:27018,mongo3:27019/oak?w=majority=nearest=majority'
{noformat}
> Use read concern majority when connected to a replica set
> -
>
> Key: OAK-4069
> URL: https://issues.apache.org/jira/browse/OAK-4069
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Labels: resilience
> Fix For: 1.6, 1.5.16
>
> Attachments: OAK-4069-2.patch, OAK-4069.patch
>
>
> Mongo 3.2 introduces new query option: {{readConcern}}. It allows to read
> only these changes that have been already committed to the majority of
> secondary instances.
> It prevents stale reads - a situation in which a change has been committed on
> the primary (and read from it), but due to the network partition a new
> primary is elected and the change is rolled back.
> We should use this new option (together with {{w:majority}} implemented in
> OAK-3554) when running Oak on MongoDB replica set.
> References:
> * [Jepsen: MongoDB stale
> reads|https://aphyr.com/posts/322-jepsen-mongodb-stale-reads]
> * [MongoDB documentation: Read Concern
> in|https://docs.mongodb.org/manual/reference/read-concern/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
[
https://issues.apache.org/jira/browse/OAK-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735480#comment-15735480
]
Bertrand Delacretaz commented on OAK-5260:
--
In the attached test code, moving the the childA1 and childA2 test cases to the
second section, paths not found, causes the test to fail although they should
not be found.
{code}
session.getRootNode().addNode("parent");
assertNodeFound(true,
"/parent",
// TODO these should not be found
"/parent/{childA1",
"/parent/{{childA2"
);
assertNodeFound(false,
"/parent/childB1",
"/parent/}childB2",
"/parent/{childB3}",
"/parent/sub/childB4",
"/parent/sub/}childB5",
"/parent/sub/{childB6}",
"/parent/sub/{childB7"
);
{code}
> Incorrect handling of subpaths with leading left curly bracket
> --
>
> Key: OAK-5260
> URL: https://issues.apache.org/jira/browse/OAK-5260
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Bertrand Delacretaz
> Attachments: OAK-5260.patch
>
>
> As per SLING-6383 it looks like the Oak name mapping causes for example
> getItem("/libs/{sub") (with a left curly bracket in the path) to return the
> /libs node if that exists but the supplied path does not.
> I'll attach a patch with a test that demonstrates this.
> [~fmeschbe] mentions in that Sling issue that the parsing of the CR 2 section
> 3.2.5.1 Expanded Form could be involved, treating the left curly bracket in a
> special way that's not appropriate here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
[
https://issues.apache.org/jira/browse/OAK-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated OAK-5260:
-
Attachment: OAK-5260.patch
> Incorrect handling of subpaths with leading left curly bracket
> --
>
> Key: OAK-5260
> URL: https://issues.apache.org/jira/browse/OAK-5260
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
>Reporter: Bertrand Delacretaz
> Attachments: OAK-5260.patch
>
>
> As per SLING-6383 it looks like the Oak name mapping causes for example
> getItem("/libs/{sub") (with a left curly bracket in the path) to return the
> /libs node if that exists but the supplied path does not.
> I'll attach a patch with a test that demonstrates this.
> [~fmeschbe] mentions in that Sling issue that the parsing of the CR 2 section
> 3.2.5.1 Expanded Form could be involved, treating the left curly bracket in a
> special way that's not appropriate here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OAK-5260) Incorrect handling of subpaths with leading left curly bracket
Bertrand Delacretaz created OAK-5260:
Summary: Incorrect handling of subpaths with leading left curly
bracket
Key: OAK-5260
URL: https://issues.apache.org/jira/browse/OAK-5260
Project: Jackrabbit Oak
Issue Type: Bug
Components: jcr
Reporter: Bertrand Delacretaz
As per SLING-6383 it looks like the Oak name mapping causes for example
getItem("/libs/{sub") (with a left curly bracket in the path) to return the
/libs node if that exists but the supplied path does not.
I'll attach a patch with a test that demonstrates this.
[~fmeschbe] mentions in that Sling issue that the parsing of the CR 2 section
3.2.5.1 Expanded Form could be involved, treating the left curly bracket in a
special way that's not appropriate here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-4069) Use read concern majority when connected to a replica set
[
https://issues.apache.org/jira/browse/OAK-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735439#comment-15735439
]
Tomek Rękawek commented on OAK-4069:
I added the role check. It seems that the
{{storageEngine.supportsCommittedReads=true}} doesn't mean that the
{{--enableMajorityReadConcern}} has been used. I haven't found an API method
that allows to check whether the readConcern can be really used, so I created a
new method isMajorityReadConcernEnabled() that tries to run a simple find()
with readConcern=majority and catches the exception (if there's any).
If the user doesn't have the appropriate role then isSupported() method invokes
the isEnabled() (as the second implies the first).
> Use read concern majority when connected to a replica set
> -
>
> Key: OAK-4069
> URL: https://issues.apache.org/jira/browse/OAK-4069
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Labels: resilience
> Fix For: 1.6, 1.5.16
>
> Attachments: OAK-4069-2.patch, OAK-4069.patch
>
>
> Mongo 3.2 introduces new query option: {{readConcern}}. It allows to read
> only these changes that have been already committed to the majority of
> secondary instances.
> It prevents stale reads - a situation in which a change has been committed on
> the primary (and read from it), but due to the network partition a new
> primary is elected and the change is rolled back.
> We should use this new option (together with {{w:majority}} implemented in
> OAK-3554) when running Oak on MongoDB replica set.
> References:
> * [Jepsen: MongoDB stale
> reads|https://aphyr.com/posts/322-jepsen-mongodb-stale-reads]
> * [MongoDB documentation: Read Concern
> in|https://docs.mongodb.org/manual/reference/read-concern/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-4069) Use read concern majority when connected to a replica set
[
https://issues.apache.org/jira/browse/OAK-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-4069:
---
Attachment: (was: OAK-4069-2.patch)
> Use read concern majority when connected to a replica set
> -
>
> Key: OAK-4069
> URL: https://issues.apache.org/jira/browse/OAK-4069
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Labels: resilience
> Fix For: 1.6, 1.5.16
>
> Attachments: OAK-4069-2.patch, OAK-4069.patch
>
>
> Mongo 3.2 introduces new query option: {{readConcern}}. It allows to read
> only these changes that have been already committed to the majority of
> secondary instances.
> It prevents stale reads - a situation in which a change has been committed on
> the primary (and read from it), but due to the network partition a new
> primary is elected and the change is rolled back.
> We should use this new option (together with {{w:majority}} implemented in
> OAK-3554) when running Oak on MongoDB replica set.
> References:
> * [Jepsen: MongoDB stale
> reads|https://aphyr.com/posts/322-jepsen-mongodb-stale-reads]
> * [MongoDB documentation: Read Concern
> in|https://docs.mongodb.org/manual/reference/read-concern/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-4069) Use read concern majority when connected to a replica set
[
https://issues.apache.org/jira/browse/OAK-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-4069:
---
Attachment: OAK-4069-2.patch
> Use read concern majority when connected to a replica set
> -
>
> Key: OAK-4069
> URL: https://issues.apache.org/jira/browse/OAK-4069
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Labels: resilience
> Fix For: 1.6, 1.5.16
>
> Attachments: OAK-4069-2.patch, OAK-4069.patch
>
>
> Mongo 3.2 introduces new query option: {{readConcern}}. It allows to read
> only these changes that have been already committed to the majority of
> secondary instances.
> It prevents stale reads - a situation in which a change has been committed on
> the primary (and read from it), but due to the network partition a new
> primary is elected and the change is rolled back.
> We should use this new option (together with {{w:majority}} implemented in
> OAK-3554) when running Oak on MongoDB replica set.
> References:
> * [Jepsen: MongoDB stale
> reads|https://aphyr.com/posts/322-jepsen-mongodb-stale-reads]
> * [MongoDB documentation: Read Concern
> in|https://docs.mongodb.org/manual/reference/read-concern/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OAK-5259) Better default for size delta estimation
[ https://issues.apache.org/jira/browse/OAK-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari resolved OAK-5259. - Resolution: Fixed Fix Version/s: 1.5.16 Fixed at r1773404. > Better default for size delta estimation > - > > Key: OAK-5259 > URL: https://issues.apache.org/jira/browse/OAK-5259 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari > Fix For: 1.6, 1.5.16 > > > The default value for the size delta estimation used during garbage > collection should be changed to 1GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OAK-4069) Use read concern majority when connected to a replica set
[
https://issues.apache.org/jira/browse/OAK-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735409#comment-15735409
]
Tomek Rękawek edited comment on OAK-4069 at 12/9/16 2:06 PM:
-
Benchmark results:
{noformat}
\# ConcurrentWriteReadTest C min 10% 50% 90% max
N
Oak-Mongo (readconcern=majority) 1 78 108 184 4921430
1061
Oak-Mongo (readconcern=local) 1 87 110 193 4911244
1029
{noformat}
I used the [local replica|https://github.com/trekawek/global-mongo] set with
latency=0. Benchmark invocation:
{noformat}
$ java -Druntime=300 -jar oak-run/target/oak-run-1.6-SNAPSHOT.jar benchmark
ConcurrentWriteReadTest Oak-Mongo \
--mongouri
'mongodb://mongo1:27017,mongo2:27018,mongo3:27019/oak?w=majority=nearest=majority'
{noformat}
was (Author: tomek.rekawek):
Benchmark results:
{{noformat}}
\# ConcurrentWriteReadTest C min 10% 50% 90% max
N
Oak-Mongo (readconcern=majority) 1 78 108 184 4921430
1061
Oak-Mongo (readconcern=local) 1 87 110 193 4911244
1029
{{noformat}}
I used the [local replica|https://github.com/trekawek/global-mongo] set with
latency=0. Benchmark invocation:
{{noformat}}
$ java -Druntime=300 -jar oak-run/target/oak-run-1.6-SNAPSHOT.jar benchmark
ConcurrentWriteReadTest Oak-Mongo \
--mongouri
'mongodb://mongo1:27017,mongo2:27018,mongo3:27019/oak?w=majority=nearest=majority'
{{noformat}}
> Use read concern majority when connected to a replica set
> -
>
> Key: OAK-4069
> URL: https://issues.apache.org/jira/browse/OAK-4069
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Labels: resilience
> Fix For: 1.6, 1.5.16
>
> Attachments: OAK-4069-2.patch, OAK-4069.patch
>
>
> Mongo 3.2 introduces new query option: {{readConcern}}. It allows to read
> only these changes that have been already committed to the majority of
> secondary instances.
> It prevents stale reads - a situation in which a change has been committed on
> the primary (and read from it), but due to the network partition a new
> primary is elected and the change is rolled back.
> We should use this new option (together with {{w:majority}} implemented in
> OAK-3554) when running Oak on MongoDB replica set.
> References:
> * [Jepsen: MongoDB stale
> reads|https://aphyr.com/posts/322-jepsen-mongodb-stale-reads]
> * [MongoDB documentation: Read Concern
> in|https://docs.mongodb.org/manual/reference/read-concern/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-4069) Use read concern majority when connected to a replica set
[
https://issues.apache.org/jira/browse/OAK-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735409#comment-15735409
]
Tomek Rękawek commented on OAK-4069:
First, benchmark results:
{{noformat}}
# ConcurrentWriteReadTest C min 10% 50% 90% max
N
Oak-Mongo (readconcern=majority) 1 78 108 184 4921430
1061
Oak-Mongo (readconcern=local) 1 87 110 193 4911244
1029
{{noformat}}
I used the [local replica|https://github.com/trekawek/global-mongo] set with
latency=0. Benchmark invocation:
{{noformat}}
$ java -Druntime=300 -jar oak-run/target/oak-run-1.6-SNAPSHOT.jar benchmark
ConcurrentWriteReadTest Oak-Mongo \
--mongouri
'mongodb://mongo1:27017,mongo2:27018,mongo3:27019/oak?w=majority=nearest=majority'
{{noformat}}
> Use read concern majority when connected to a replica set
> -
>
> Key: OAK-4069
> URL: https://issues.apache.org/jira/browse/OAK-4069
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Labels: resilience
> Fix For: 1.6, 1.5.16
>
> Attachments: OAK-4069-2.patch, OAK-4069.patch
>
>
> Mongo 3.2 introduces new query option: {{readConcern}}. It allows to read
> only these changes that have been already committed to the majority of
> secondary instances.
> It prevents stale reads - a situation in which a change has been committed on
> the primary (and read from it), but due to the network partition a new
> primary is elected and the change is rolled back.
> We should use this new option (together with {{w:majority}} implemented in
> OAK-3554) when running Oak on MongoDB replica set.
> References:
> * [Jepsen: MongoDB stale
> reads|https://aphyr.com/posts/322-jepsen-mongodb-stale-reads]
> * [MongoDB documentation: Read Concern
> in|https://docs.mongodb.org/manual/reference/read-concern/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OAK-4069) Use read concern majority when connected to a replica set
[
https://issues.apache.org/jira/browse/OAK-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735409#comment-15735409
]
Tomek Rękawek edited comment on OAK-4069 at 12/9/16 2:05 PM:
-
Benchmark results:
{{noformat}}
\# ConcurrentWriteReadTest C min 10% 50% 90% max
N
Oak-Mongo (readconcern=majority) 1 78 108 184 4921430
1061
Oak-Mongo (readconcern=local) 1 87 110 193 4911244
1029
{{noformat}}
I used the [local replica|https://github.com/trekawek/global-mongo] set with
latency=0. Benchmark invocation:
{{noformat}}
$ java -Druntime=300 -jar oak-run/target/oak-run-1.6-SNAPSHOT.jar benchmark
ConcurrentWriteReadTest Oak-Mongo \
--mongouri
'mongodb://mongo1:27017,mongo2:27018,mongo3:27019/oak?w=majority=nearest=majority'
{{noformat}}
was (Author: tomek.rekawek):
First, benchmark results:
{{noformat}}
# ConcurrentWriteReadTest C min 10% 50% 90% max
N
Oak-Mongo (readconcern=majority) 1 78 108 184 4921430
1061
Oak-Mongo (readconcern=local) 1 87 110 193 4911244
1029
{{noformat}}
I used the [local replica|https://github.com/trekawek/global-mongo] set with
latency=0. Benchmark invocation:
{{noformat}}
$ java -Druntime=300 -jar oak-run/target/oak-run-1.6-SNAPSHOT.jar benchmark
ConcurrentWriteReadTest Oak-Mongo \
--mongouri
'mongodb://mongo1:27017,mongo2:27018,mongo3:27019/oak?w=majority=nearest=majority'
{{noformat}}
> Use read concern majority when connected to a replica set
> -
>
> Key: OAK-4069
> URL: https://issues.apache.org/jira/browse/OAK-4069
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Labels: resilience
> Fix For: 1.6, 1.5.16
>
> Attachments: OAK-4069-2.patch, OAK-4069.patch
>
>
> Mongo 3.2 introduces new query option: {{readConcern}}. It allows to read
> only these changes that have been already committed to the majority of
> secondary instances.
> It prevents stale reads - a situation in which a change has been committed on
> the primary (and read from it), but due to the network partition a new
> primary is elected and the change is rolled back.
> We should use this new option (together with {{w:majority}} implemented in
> OAK-3554) when running Oak on MongoDB replica set.
> References:
> * [Jepsen: MongoDB stale
> reads|https://aphyr.com/posts/322-jepsen-mongodb-stale-reads]
> * [MongoDB documentation: Read Concern
> in|https://docs.mongodb.org/manual/reference/read-concern/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OAK-5259) Better default for size delta estimation
Francesco Mari created OAK-5259: --- Summary: Better default for size delta estimation Key: OAK-5259 URL: https://issues.apache.org/jira/browse/OAK-5259 Project: Jackrabbit Oak Issue Type: Bug Components: segment-tar Reporter: Francesco Mari Assignee: Francesco Mari The default value for the size delta estimation used during garbage collection should be changed to 1GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-5259) Better default for size delta estimation
[ https://issues.apache.org/jira/browse/OAK-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Mari updated OAK-5259: Fix Version/s: 1.6 > Better default for size delta estimation > - > > Key: OAK-5259 > URL: https://issues.apache.org/jira/browse/OAK-5259 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-tar >Reporter: Francesco Mari >Assignee: Francesco Mari > Fix For: 1.6 > > > The default value for the size delta estimation used during garbage > collection should be changed to 1GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OAK-5258) LuceneIndexEditor skips indexing for unknown nodetype due to stale NodeType registry state
[ https://issues.apache.org/jira/browse/OAK-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved OAK-5258. -- Resolution: Fixed Fix Version/s: 1.5.16 Done with 1773383 > LuceneIndexEditor skips indexing for unknown nodetype due to stale NodeType > registry state > -- > > Key: OAK-5258 > URL: https://issues.apache.org/jira/browse/OAK-5258 > Project: Jackrabbit Oak > Issue Type: Bug > Components: lucene >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.6, 1.5.16 > > > With OAK-5218 hybrid index can be used since very starting of system. > Currently LuceneIndexEditorProvider uses a cached IndexDefinition instance > for sync/nrt mode. > In some cases it can happen that indexed content uses a new nodetype and > IndexDefinition which is cached in IndexTracker has yet not updated the > cached index definition. This is not a problem with async indexing mode as by > the time async indexer kicks in it constructs the IndexDefinition from the > current root. However with sync/nrt indexing it posses a problem as nodetype > state stored in cached index definition may be old and does not have entry > for newly registered nodetypes > As a fix we should check if NodeType registry state has changed for current > root wrt root referred to in IndexDefinition. If changed then cached > IndexDefinition should not be used -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OAK-5256) Add type property to LuceneIndexEditorProvider
[
https://issues.apache.org/jira/browse/OAK-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved OAK-5256.
--
Resolution: Fixed
Fix Version/s: 1.5.16
Done with 1773381
> Add type property to LuceneIndexEditorProvider
> --
>
> Key: OAK-5256
> URL: https://issues.apache.org/jira/browse/OAK-5256
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: lucene
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: 1.6, 1.5.16
>
>
> As done for OAK-3366 we need to register LuceneIndexEditorProvider with
> {{type}} property such components in OSGi can add static dependency to it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OAK-5257) Pass CommitContext as part of CommitInfo in OakInitializer
[
https://issues.apache.org/jira/browse/OAK-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved OAK-5257.
--
Resolution: Fixed
Fix Version/s: 1.5.16
Done with 1773382
> Pass CommitContext as part of CommitInfo in OakInitializer
> --
>
> Key: OAK-5257
> URL: https://issues.apache.org/jira/browse/OAK-5257
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: core
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: 1.6, 1.5.16
>
>
> With OAK-4640 CommitContext was introduced and passed via commits done in
> MutableRoot. We should also set this while doing commits in {{OakInitializer}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OAK-5258) LuceneIndexEditor skips indexing for unknown nodetype due to stale NodeType registry state
Chetan Mehrotra created OAK-5258: Summary: LuceneIndexEditor skips indexing for unknown nodetype due to stale NodeType registry state Key: OAK-5258 URL: https://issues.apache.org/jira/browse/OAK-5258 Project: Jackrabbit Oak Issue Type: Bug Components: lucene Reporter: Chetan Mehrotra Assignee: Chetan Mehrotra Priority: Minor Fix For: 1.6 With OAK-5218 hybrid index can be used since very starting of system. Currently LuceneIndexEditorProvider uses a cached IndexDefinition instance for sync/nrt mode. In some cases it can happen that indexed content uses a new nodetype and IndexDefinition which is cached in IndexTracker has yet not updated the cached index definition. This is not a problem with async indexing mode as by the time async indexer kicks in it constructs the IndexDefinition from the current root. However with sync/nrt indexing it posses a problem as nodetype state stored in cached index definition may be old and does not have entry for newly registered nodetypes As a fix we should check if NodeType registry state has changed for current root wrt root referred to in IndexDefinition. If changed then cached IndexDefinition should not be used -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-4069) Use read concern majority when connected to a replica set
[
https://issues.apache.org/jira/browse/OAK-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-4069:
---
Attachment: OAK-4069-2.patch
> Use read concern majority when connected to a replica set
> -
>
> Key: OAK-4069
> URL: https://issues.apache.org/jira/browse/OAK-4069
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
>Reporter: Tomek Rękawek
>Assignee: Tomek Rękawek
> Labels: resilience
> Fix For: 1.6, 1.5.16
>
> Attachments: OAK-4069-2.patch, OAK-4069.patch
>
>
> Mongo 3.2 introduces new query option: {{readConcern}}. It allows to read
> only these changes that have been already committed to the majority of
> secondary instances.
> It prevents stale reads - a situation in which a change has been committed on
> the primary (and read from it), but due to the network partition a new
> primary is elected and the change is rolled back.
> We should use this new option (together with {{w:majority}} implemented in
> OAK-3554) when running Oak on MongoDB replica set.
> References:
> * [Jepsen: MongoDB stale
> reads|https://aphyr.com/posts/322-jepsen-mongodb-stale-reads]
> * [MongoDB documentation: Read Concern
> in|https://docs.mongodb.org/manual/reference/read-concern/]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5257) Pass CommitContext as part of CommitInfo in OakInitializer
[
https://issues.apache.org/jira/browse/OAK-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-5257:
-
Summary: Pass CommitContext as part of CommitInfo in OakInitializer (was:
Pass CommitContext as part of commit done in OakInitializer)
> Pass CommitContext as part of CommitInfo in OakInitializer
> --
>
> Key: OAK-5257
> URL: https://issues.apache.org/jira/browse/OAK-5257
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: core
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: 1.6
>
>
> With OAK-4640 CommitContext was introduced and passed via commits done in
> MutableRoot. We should also set this while doing commits in {{OakInitializer}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OAK-5257) Pass CommitContext as part of commit done in OakInitializer
Chetan Mehrotra created OAK-5257:
Summary: Pass CommitContext as part of commit done in
OakInitializer
Key: OAK-5257
URL: https://issues.apache.org/jira/browse/OAK-5257
Project: Jackrabbit Oak
Issue Type: Task
Components: core
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
Priority: Minor
Fix For: 1.6
With OAK-4640 CommitContext was introduced and passed via commits done in
MutableRoot. We should also set this while doing commits in {{OakInitializer}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OAK-5256) Add type property to LuceneIndexEditorProvider
Chetan Mehrotra created OAK-5256:
Summary: Add type property to LuceneIndexEditorProvider
Key: OAK-5256
URL: https://issues.apache.org/jira/browse/OAK-5256
Project: Jackrabbit Oak
Issue Type: Task
Components: lucene
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
Priority: Minor
Fix For: 1.6
As done for OAK-3366 we need to register LuceneIndexEditorProvider with
{{type}} property such components in OSGi can add static dependency to it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OAK-5253) Optimize AbstractBlob#equal to not do content equals when possible
[
https://issues.apache.org/jira/browse/OAK-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735027#comment-15735027
]
Julian Sedding edited comment on OAK-5253 at 12/9/16 12:16 PM:
---
Thanks [~amitjain]. I am wondering if we could compare {{Blob#getReference()}},
but the contract is not very clear regarding its equality semantics. Basically
I believe that we need to use something that is delegated to the {{BlobStore}}
implementation.
A change in {{SegmentBlob}} would suffer from the same problem as a change in
{{AbstractBlob}}. It is backed by an arbitrary {{BlobStore}} implementation,
thus we cannot rely on the semantics of {{Blob#getContentIdentity()}}, as it
may change depending on the backing {{BlobStore}}.
I have [posted on the mailing
list|http://jackrabbit.markmail.org/thread/mzwgde4v7r2xq6yu] to see if someone
can clarify whether {{Blob#getReference()}} is suited.
was (Author: jsedding):
Thanks [~amitjain]. I am wondering if we could compare {{Blob#getReference()}},
but the contract is not very clear regarding its equality semantics. Basically
I believe that we need to use something that is delegated to the {{BlobStore}}
implementation.
A change in {{SegmentBlob}} would suffer from the same problem as a change in
{{AbstractBlob}}. It is backed by an arbitrary {{BlobStore}} implementation,
thus we cannot rely on the semantics of {{Blob#getContentIdentity()}}, as it
may change depending on the backing {{BlobStore}}.
I have posted on the mailing list to see if someone can clarify whether
{{Blob#getReference()}} is suited.
> Optimize AbstractBlob#equal to not do content equals when possible
> --
>
> Key: OAK-5253
> URL: https://issues.apache.org/jira/browse/OAK-5253
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.6, 1.5.16, 1.4.11
>
> Attachments: OAK-5253.1.patch
>
>
> AbstractBlob#equals tries to match content when length is equal and content
> identities is not null and different. Matching content triggers an expensive
> download of binaries for S3DataStore.
> Since, right now the content identity is the content hash the check can be
> short -circuited when the content identities is not null and not equal to
> return false.
> This can be revisited if we change the identity to something different.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-5253) Optimize AbstractBlob#equal to not do content equals when possible
[
https://issues.apache.org/jira/browse/OAK-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15735027#comment-15735027
]
Julian Sedding commented on OAK-5253:
-
Thanks [~amitjain]. I am wondering if we could compare {{Blob#getReference()}},
but the contract is not very clear regarding its equality semantics. Basically
I believe that we need to use something that is delegated to the {{BlobStore}}
implementation.
A change in {{SegmentBlob}} would suffer from the same problem as a change in
{{AbstractBlob}}. It is backed by an arbitrary {{BlobStore}} implementation,
thus we cannot rely on the semantics of {{Blob#getContentIdentity()}}, as it
may change depending on the backing {{BlobStore}}.
I have posted on the mailing list to see if someone can clarify whether
{{Blob#getReference()}} is suited.
> Optimize AbstractBlob#equal to not do content equals when possible
> --
>
> Key: OAK-5253
> URL: https://issues.apache.org/jira/browse/OAK-5253
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.6, 1.5.16, 1.4.11
>
> Attachments: OAK-5253.1.patch
>
>
> AbstractBlob#equals tries to match content when length is equal and content
> identities is not null and different. Matching content triggers an expensive
> download of binaries for S3DataStore.
> Since, right now the content identity is the content hash the check can be
> short -circuited when the content identities is not null and not equal to
> return false.
> This can be revisited if we change the identity to something different.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-5253) Optimize AbstractBlob#equal to not do content equals when possible
[ https://issues.apache.org/jira/browse/OAK-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734957#comment-15734957 ] Amit Jain commented on OAK-5253: Reverted commits: * trunk - http://svn.apache.org/viewvc?rev=1773355=rev * 1.4 - http://svn.apache.org/viewvc?rev=1773353=rev > Optimize AbstractBlob#equal to not do content equals when possible > -- > > Key: OAK-5253 > URL: https://issues.apache.org/jira/browse/OAK-5253 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.6, 1.5.16, 1.4.11 > > Attachments: OAK-5253.1.patch > > > AbstractBlob#equals tries to match content when length is equal and content > identities is not null and different. Matching content triggers an expensive > download of binaries for S3DataStore. > Since, right now the content identity is the content hash the check can be > short -circuited when the content identities is not null and not equal to > return false. > This can be revisited if we change the identity to something different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OAK-5253) Optimize AbstractBlob#equal to not do content equals when possible
[ https://issues.apache.org/jira/browse/OAK-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734916#comment-15734916 ] Amit Jain commented on OAK-5253: Ok will back out the changes and try to make change in the SegmentBlob itself. > Optimize AbstractBlob#equal to not do content equals when possible > -- > > Key: OAK-5253 > URL: https://issues.apache.org/jira/browse/OAK-5253 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob >Reporter: Amit Jain >Assignee: Amit Jain > Fix For: 1.6, 1.5.16, 1.4.11 > > Attachments: OAK-5253.1.patch > > > AbstractBlob#equals tries to match content when length is equal and content > identities is not null and different. Matching content triggers an expensive > download of binaries for S3DataStore. > Since, right now the content identity is the content hash the check can be > short -circuited when the content identities is not null and not equal to > return false. > This can be revisited if we change the identity to something different. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (OAK-5253) Optimize AbstractBlob#equal to not do content equals when possible
[
https://issues.apache.org/jira/browse/OAK-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding reopened OAK-5253:
-
I am a bit concerned about this optimization.
The javadoc of
[{{Blob#getContentIdentity}}|http://static.javadoc.io/org.apache.jackrabbit/oak-core/1.5.14/org/apache/jackrabbit/oak/api/Blob.html#getContentIdentity()]
is pretty clear (emphasis mine):
bq. If two values have the same identifier, the content of the value is
guaranteed to be the same. However it is *not guaranteed* that two values with
the *same content* will return the *same identifier*.
This means that, according to the contract, we need to compare the blob
contents iff their identifiers are not equal. That's exactly what the previous
implementation did.
IMHO the implementation of {{AbstractBlob}} cannot rely on implementation
details of particular {{Blob}} implementations. Can you please look for a
solution that implements this optimization in the specific {{Blob}}
implementation you want to optimize? Your implementation is free to override
methods inherited from {{AbstractBlob}}.
> Optimize AbstractBlob#equal to not do content equals when possible
> --
>
> Key: OAK-5253
> URL: https://issues.apache.org/jira/browse/OAK-5253
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob
>Reporter: Amit Jain
>Assignee: Amit Jain
> Fix For: 1.6, 1.5.16, 1.4.11
>
> Attachments: OAK-5253.1.patch
>
>
> AbstractBlob#equals tries to match content when length is equal and content
> identities is not null and different. Matching content triggers an expensive
> download of binaries for S3DataStore.
> Since, right now the content identity is the content hash the check can be
> short -circuited when the content identities is not null and not equal to
> return false.
> This can be revisited if we change the identity to something different.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-5254) MultiplexingNodeStoreService does not pick up Observers registered through the whiteboard
[
https://issues.apache.org/jira/browse/OAK-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734832#comment-15734832
]
Tomek Rękawek commented on OAK-5254:
Fixed for trunk in [r1773349|https://svn.apache.org/r1773349] with a minor
change (stop observer in unregisterMultiplexingNodeStore, since it started in
registerMultiplexingNodeStore).
> MultiplexingNodeStoreService does not pick up Observers registered through
> the whiteboard
> -
>
> Key: OAK-5254
> URL: https://issues.apache.org/jira/browse/OAK-5254
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
>Reporter: Robert Munteanu
> Fix For: 1.6, 1.5.16
>
> Attachments:
> 0001-OAK-5254-MultiplexingNodeStoreService-does-not-pick-.patch
>
>
> The {{MultiplexingNodeStoreService}} fails to pick up observer instances from
> the whiteboard. I noticed this when using it in an OSGi context and it failed
> to picked up the Lucene indexes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OAK-5254) MultiplexingNodeStoreService does not pick up Observers registered through the whiteboard
[
https://issues.apache.org/jira/browse/OAK-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek resolved OAK-5254.
Resolution: Fixed
> MultiplexingNodeStoreService does not pick up Observers registered through
> the whiteboard
> -
>
> Key: OAK-5254
> URL: https://issues.apache.org/jira/browse/OAK-5254
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
>Reporter: Robert Munteanu
> Fix For: 1.6, 1.5.16
>
> Attachments:
> 0001-OAK-5254-MultiplexingNodeStoreService-does-not-pick-.patch
>
>
> The {{MultiplexingNodeStoreService}} fails to pick up observer instances from
> the whiteboard. I noticed this when using it in an OSGi context and it failed
> to picked up the Lucene indexes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OAK-5255) Flags in the oak-upgrade should allow to set boolean parameter value
[
https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek resolved OAK-5255.
Resolution: Won't Fix
> Flags in the oak-upgrade should allow to set boolean parameter value
>
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
>Affects Versions: 1.4.10, 1.5.15
>Reporter: Tomek Rękawek
> Fix For: 1.6
>
> Attachments: OAK-5255.patch
>
>
> There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
> seems that these flags accepts parameters (passed with =) but their value is
> ignored. As a result specifying:
> * {{\-\-copy\-binaries}}
> * {{\-\-copy\-binaries=true}}
> * {{\-\-copy\-binaries=false}}
> * {{\-\-copy\-binaries=xyz}}
> has the same effect. On the other hand, the only way to unset this flag is
> skipping the parameter at all.
> We should change this behaviour. The argument may be still optional, but
> oak-upgrade should only accept boolean values and interpret them accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (OAK-5255) Flags in the oak-upgrade should allow to set boolean parameter value
[
https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734820#comment-15734820
]
Tomek Rękawek edited comment on OAK-5255 at 12/9/16 9:40 AM:
-
Created a patch, but it seems that the parser we use is somehow limited and
doesn't support the required case. No values should be used for flags.
Resolving as won't fix.
was (Author: tomek.rekawek):
Created a patch, but it seems that the parser we use is somehow limited and
doesn't support the required case. Resolving as won't fix.
> Flags in the oak-upgrade should allow to set boolean parameter value
>
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
>Affects Versions: 1.4.10, 1.5.15
>Reporter: Tomek Rękawek
> Fix For: 1.6
>
> Attachments: OAK-5255.patch
>
>
> There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
> seems that these flags accepts parameters (passed with =) but their value is
> ignored. As a result specifying:
> * {{\-\-copy\-binaries}}
> * {{\-\-copy\-binaries=true}}
> * {{\-\-copy\-binaries=false}}
> * {{\-\-copy\-binaries=xyz}}
> has the same effect. On the other hand, the only way to unset this flag is
> skipping the parameter at all.
> We should change this behaviour. The argument may be still optional, but
> oak-upgrade should only accept boolean values and interpret them accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5255) Flags in the oak-upgrade should allow to set boolean parameter value
[
https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-5255:
---
Attachment: OAK-5255.patch
> Flags in the oak-upgrade should allow to set boolean parameter value
>
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
>Affects Versions: 1.4.10, 1.5.15
>Reporter: Tomek Rękawek
> Fix For: 1.6
>
> Attachments: OAK-5255.patch
>
>
> There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
> seems that these flags accepts parameters (passed with =) but their value is
> ignored. As a result specifying:
> * {{\-\-copy\-binaries}}
> * {{\-\-copy\-binaries=true}}
> * {{\-\-copy\-binaries=false}}
> * {{\-\-copy\-binaries=xyz}}
> has the same effect. On the other hand, the only way to unset this flag is
> skipping the parameter at all.
> We should change this behaviour. The argument may be still optional, but
> oak-upgrade should only accept boolean values and interpret them accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-5255) Flags in the oak-upgrade should allow to set boolean parameter value
[
https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734820#comment-15734820
]
Tomek Rękawek commented on OAK-5255:
Created a patch, but it seems that the parser we use is somehow limited and
doesn't support the required case. Resolving as won't fix.
> Flags in the oak-upgrade should allow to set boolean parameter value
>
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
>Affects Versions: 1.4.10, 1.5.15
>Reporter: Tomek Rękawek
> Fix For: 1.6
>
> Attachments: OAK-5255.patch
>
>
> There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
> seems that these flags accepts parameters (passed with =) but their value is
> ignored. As a result specifying:
> * {{\-\-copy\-binaries}}
> * {{\-\-copy\-binaries=true}}
> * {{\-\-copy\-binaries=false}}
> * {{\-\-copy\-binaries=xyz}}
> has the same effect. On the other hand, the only way to unset this flag is
> skipping the parameter at all.
> We should change this behaviour. The argument may be still optional, but
> oak-upgrade should only accept boolean values and interpret them accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (OAK-5227) Update Oak 1.2 and Oak 1.4 to Jackrabbit 2.12.6
[ https://issues.apache.org/jira/browse/OAK-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain resolved OAK-5227. Resolution: Fixed *1.2 - http://svn.apache.org/viewvc?rev=1773336=rev * 1.4 - http://svn.apache.org/viewvc?rev=1773343=rev > Update Oak 1.2 and Oak 1.4 to Jackrabbit 2.12.6 > --- > > Key: OAK-5227 > URL: https://issues.apache.org/jira/browse/OAK-5227 > Project: Jackrabbit Oak > Issue Type: Task > Components: parent >Reporter: Amit Jain >Assignee: Amit Jain >Priority: Minor > Fix For: 1.4.11, 1.2.22 > > > Update Oak 1.2 and 1.4 branches once Jackrabbit 2.12.6 released. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-5255) Flags in the oak-upgrade should allow to set boolean parameter value
[
https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-5255:
---
Description:
There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
seems that these flags accepts parameters (passed with =) but their value is
ignored. As a result specifying:
* {{\-\-copy\-binaries}}
* {{\-\-copy\-binaries=true}}
* {{\-\-copy\-binaries=false}}
* {{\-\-copy\-binaries=xyz}}
has the same effect. On the other hand, the only way to unset this flag is
skipping the parameter at all.
We should change this behaviour. The argument may be still optional, but
oak-upgrade should only accept boolean values and interpret them accordingly.
was:
There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
seems that these flags accepts parameters (passed with =) but their value is
ignored. As a result specifying:
* {{\-\-copy\-binaries}}
* {{\-\-copy\-binaries=true}}
* {{\-\-copy\-binaries=false}}
* {{\-\-copy\-binaries=xyz}}
Has the same effect. On the other hand, the only way to unset this flag is
skipping the parameter at all.
We should change this behaviour. The argument may be still optional, but
oak-upgrade should only accept boolean values and interpret them accordingly.
> Flags in the oak-upgrade should allow to set boolean parameter value
>
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
>Affects Versions: 1.4.10, 1.5.15
>Reporter: Tomek Rękawek
> Fix For: 1.6
>
>
> There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
> seems that these flags accepts parameters (passed with =) but their value is
> ignored. As a result specifying:
> * {{\-\-copy\-binaries}}
> * {{\-\-copy\-binaries=true}}
> * {{\-\-copy\-binaries=false}}
> * {{\-\-copy\-binaries=xyz}}
> has the same effect. On the other hand, the only way to unset this flag is
> skipping the parameter at all.
> We should change this behaviour. The argument may be still optional, but
> oak-upgrade should only accept boolean values and interpret them accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5255) Flags in the oak-upgrade should allow to set boolean parameter value
[
https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-5255:
---
Summary: Flags in the oak-upgrade should allow to set boolean parameter
value (was: Flags in the oak-upgrade should allow to set binary value)
> Flags in the oak-upgrade should allow to set boolean parameter value
>
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
>Affects Versions: 1.4.10, 1.5.15
>Reporter: Tomek Rękawek
> Fix For: 1.6
>
>
> There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
> seems that these flags accepts parameters (passed with =) but their value is
> ignored. As a result specifying:
> * {{\-\-copy\-binaries}}
> * {{\-\-copy\-binaries=true}}
> * {{\-\-copy\-binaries=false}}
> * {{\-\-copy\-binaries=xyz}}
> Has the same effect. On the other hand, the only way to unset this flag is
> skipping the parameter at all.
> We should change this behaviour. The argument may be still optional, but
> oak-upgrade should only accept boolean values and interpret them accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5255) Flags in the oak-upgrade should allow to set binary value
[
https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-5255:
---
Description:
There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
seems that these flags accepts parameters (passed with =) but their value is
ignored. As a result specifying:
* {{\-\-copy\-binaries}}
* {{\-\-copy\-binaries=true}}
* {{\-\-copy\-binaries=false}}
* {{\-\-copy\-binaries=xyz}}
Has the same effect. On the other hand, the only way to unset this flag is
skipping the parameter at all.
We should change this behaviour. The argument may be still optional, but
oak-upgrade should only accept boolean values and interpret them accordingly.
was:It seems that if the {{\-\-copy\-binaries}} parameter is present, its
binary value is ignored and oak-upgrade always assume {{true}}.
Issue Type: Improvement (was: Bug)
Summary: Flags in the oak-upgrade should allow to set binary value
(was: Copy binaries parameter value is ignored)
> Flags in the oak-upgrade should allow to set binary value
> -
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
>Affects Versions: 1.4.10, 1.5.15
>Reporter: Tomek Rękawek
> Fix For: 1.6
>
>
> There are a few flags in oak-upgrade (copy-binaries, disable-mmap, etc.). It
> seems that these flags accepts parameters (passed with =) but their value is
> ignored. As a result specifying:
> * {{\-\-copy\-binaries}}
> * {{\-\-copy\-binaries=true}}
> * {{\-\-copy\-binaries=false}}
> * {{\-\-copy\-binaries=xyz}}
> Has the same effect. On the other hand, the only way to unset this flag is
> skipping the parameter at all.
> We should change this behaviour. The argument may be still optional, but
> oak-upgrade should only accept boolean values and interpret them accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-5255) Copy binaries parameter value is ignored
[
https://issues.apache.org/jira/browse/OAK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek updated OAK-5255:
---
Description: It seems that if the {{\-\-copy\-binaries}} parameter is
present, its binary value is ignored and oak-upgrade always assume {{true}}.
(was: It seems that if the {{\-\-copy\-binaries}} parameter is present, it's
binary value is ignored and oak-upgrade always assume {{true}}.)
> Copy binaries parameter value is ignored
>
>
> Key: OAK-5255
> URL: https://issues.apache.org/jira/browse/OAK-5255
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
>Affects Versions: 1.4.10, 1.5.15
>Reporter: Tomek Rękawek
> Fix For: 1.6
>
>
> It seems that if the {{\-\-copy\-binaries}} parameter is present, its binary
> value is ignored and oak-upgrade always assume {{true}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OAK-5255) Copy binaries parameter value is ignored
Tomek Rękawek created OAK-5255:
--
Summary: Copy binaries parameter value is ignored
Key: OAK-5255
URL: https://issues.apache.org/jira/browse/OAK-5255
Project: Jackrabbit Oak
Issue Type: Bug
Components: upgrade
Affects Versions: 1.5.15, 1.4.10
Reporter: Tomek Rękawek
Fix For: 1.6
It seems that if the {{\-\-copy\-binaries}} parameter is present, it's binary
value is ignored and oak-upgrade always assume {{true}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
