[jira] [Comment Edited] (KNOX-400) Administrative user interface for Knox
[ https://issues.apache.org/jira/browse/KNOX-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658052#comment-16658052 ] Phil Zampino edited comment on KNOX-400 at 10/21/18 2:16 AM: - [~risdenk] I would say it's mostly done now. The Admin UI does *+not+* yet provide the ability to: * View logs * View gateway config * Modify gateway config * Restart the gateway IMO, we could close this one, and log new individual issues for each of these. was (Author: pzampino): [~risdenk] I would say it's mostly done now. The Admin UI does *+not+* yet provide the ability to: * View logs * View gateway config * Modify gateway config * Restart the gateway > Administrative user interface for Knox > -- > > Key: KNOX-400 > URL: https://issues.apache.org/jira/browse/KNOX-400 > Project: Apache Knox > Issue Type: New Feature > Components: Server >Affects Versions: 0.4.0 >Reporter: Kevin Minder >Priority: Major > Fix For: Future > > > Initially only read only operations > Build information > Deployed topologies > Consider reading config? > Consider reading logs? > Eventually write operations > Deploy/Undeploy topologies > Modify Configuration > Restart server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-400) Administrative user interface for Knox
[ https://issues.apache.org/jira/browse/KNOX-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658052#comment-16658052 ] Phil Zampino commented on KNOX-400: --- [~risdenk] I would say it's mostly done now. The Admin UI does *+not+* yet provide the ability to: * View logs * View gateway config * Modify gateway config * Restart the gateway > Administrative user interface for Knox > -- > > Key: KNOX-400 > URL: https://issues.apache.org/jira/browse/KNOX-400 > Project: Apache Knox > Issue Type: New Feature > Components: Server >Affects Versions: 0.4.0 >Reporter: Kevin Minder >Priority: Major > Fix For: Future > > > Initially only read only operations > Build information > Deployed topologies > Consider reading config? > Consider reading logs? > Eventually write operations > Deploy/Undeploy topologies > Modify Configuration > Restart server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KNOX-256) Oozie output/input Dir configuration rewrite rules
[
https://issues.apache.org/jira/browse/KNOX-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated KNOX-256:
--
Summary: Oozie output/input Dir configuration rewrite rules (was: Ozzie
output/input Dir configuration rewrite rules)
> Oozie output/input Dir configuration rewrite rules
> --
>
> Key: KNOX-256
> URL: https://issues.apache.org/jira/browse/KNOX-256
> Project: Apache Knox
> Issue Type: Bug
>Affects Versions: 0.3.0
>Reporter: Vladimir Tkhir
>Priority: Major
> Fix For: Future
>
> Attachments: README, oozie-examples.jar, workflow-configuration.xml,
> workflow.xml
>
>
> Steps to reproduce:
> Save attached files to /tmp/oozie folder
> # 0. Optionally cleanup the test directory in case a previous example was run
> without cleaning up.
> curl -i -k -u guest:guest-password -X DELETE \
>
> 'https://localhost:8443/gateway/sandbox/webhdfs/v1/user/guest/example?op=DELETE=true'
> # 1. Create the inode for workflow definition file in /user/guest/example
> curl -i -k -u guest:guest-password -X PUT \
>
> 'https://localhost:8443/gateway/sandbox/webhdfs/v1/user/guest/example/workflow.xml?op=CREATE'
> # 2. Upload the workflow definition file.
> curl -i -k -u guest:guest-password -T /tmp/oozie/workflow.xml -X PUT \
> '{Value Location header from command above}'
> # 3. Create the inode for oozie-examples.jar in /user/guest/example/lib
> curl -i -k -u guest:guest-password -X PUT \
>
> 'https://localhost:8443/gateway/sandbox/webhdfs/v1/user/guest/example/lib/oozie-examples.jar?op=CREATE'
> # 4. Upload oozie-examples.jar to /user/guest/example/lib.
> curl -i -k -u guest:guest-password -T /tmp/oozie/oozie-examples.jar -X PUT \
> '{Value Location header from command above}'
> # 5. Create the inode for a sample input file readme in
> /user/guest/example/input.
> curl -i -k -u guest:guest-password -X PUT \
>
> 'https://localhost:8443/gateway/sandbox/webhdfs/v1/user/guest/example/input/README?op=CREATE'
> # 6. Upload readme.txt to /user/guest/example/input.
> curl -i -k -u guest:guest-password -T /tmp/oozie/README -X PUT \
> '{Value of Location header from command above}'
> # 7. Submit the job via Oozie
> # Take note of the Job ID in the JSON response as this will be used in the
> next step.
> curl -ikv -u guest:guest-password -H Content-Type:application/xml -T
> /tmp/oozie/workflow-configuration.xml \
> -X POST
> 'https://localhost:8443/gateway/sandbox/oozie/v1/jobs?action=start'
> Job started, but failed with exception message:
> java.lang.IllegalArgumentException: Pathname
> /user/guest/Oozie1SysTest/output-data/hdfs:/hdp:8020/map-reduce from
> hdfs://hdp:8020/user/guest/Oozie1SysTest/output-data/hdfs:/hdp:8020/map-reduce
> is not a valid DFS filename.
> Knox interprets outputDir parameter value as a absolute path and rewrites it
> to /hdp:8020/map-reduce.
> mapred.output.dir parameter in workflow definition uses outputDir parameter
> in its value: /user/${wf:user()}/${examplesRoot}/output-data/${outputDir} and
> resulting parameter value is incorrect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KNOX-400) Administrative user interface for Knox
[ https://issues.apache.org/jira/browse/KNOX-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657978#comment-16657978 ] Kevin Risden commented on KNOX-400: --- [~lmccay] - This is done now right? Knox has an admin ui. > Administrative user interface for Knox > -- > > Key: KNOX-400 > URL: https://issues.apache.org/jira/browse/KNOX-400 > Project: Apache Knox > Issue Type: New Feature > Components: Server >Affects Versions: 0.4.0 >Reporter: Kevin Minder >Priority: Major > Fix For: Future > > > Initially only read only operations > Build information > Deployed topologies > Consider reading config? > Consider reading logs? > Eventually write operations > Deploy/Undeploy topologies > Modify Configuration > Restart server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-416) Improve Knox Contributor's Page
[ https://issues.apache.org/jira/browse/KNOX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657972#comment-16657972 ] Kevin Risden commented on KNOX-416: --- The Knox dev-guide has most of this information: https://knox.apache.org/books/knox-1-1-0/dev-guide.html#Development+Processes > Improve Knox Contributor's Page > --- > > Key: KNOX-416 > URL: https://issues.apache.org/jira/browse/KNOX-416 > Project: Apache Knox > Issue Type: Improvement >Reporter: Vinay Shukla >Priority: Major > > Would be good to add the following to contributor's page > # When to use Manual testing against a Knox instance > # How to build a Knox tarball > # How to install Knox tarball and start/stop Knox - Link to user guide where > this is explained. > # Useful ant targets such as ant start-test-ldap, ant start-test-gateway & > ant start-debug-gateway -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KNOX-416) Improve Knox Contributor's Page
[ https://issues.apache.org/jira/browse/KNOX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden closed KNOX-416. - > Improve Knox Contributor's Page > --- > > Key: KNOX-416 > URL: https://issues.apache.org/jira/browse/KNOX-416 > Project: Apache Knox > Issue Type: Improvement >Reporter: Vinay Shukla >Priority: Major > > Would be good to add the following to contributor's page > # When to use Manual testing against a Knox instance > # How to build a Knox tarball > # How to install Knox tarball and start/stop Knox - Link to user guide where > this is explained. > # Useful ant targets such as ant start-test-ldap, ant start-test-gateway & > ant start-debug-gateway -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KNOX-416) Improve Knox Contributor's Page
[ https://issues.apache.org/jira/browse/KNOX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden resolved KNOX-416. --- Resolution: Fixed > Improve Knox Contributor's Page > --- > > Key: KNOX-416 > URL: https://issues.apache.org/jira/browse/KNOX-416 > Project: Apache Knox > Issue Type: Improvement >Reporter: Vinay Shukla >Priority: Major > > Would be good to add the following to contributor's page > # When to use Manual testing against a Knox instance > # How to build a Knox tarball > # How to install Knox tarball and start/stop Knox - Link to user guide where > this is explained. > # Useful ant targets such as ant start-test-ldap, ant start-test-gateway & > ant start-debug-gateway -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KNOX-416) Improve Knox Contributor's Page
[ https://issues.apache.org/jira/browse/KNOX-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-416: -- Fix Version/s: (was: Future) > Improve Knox Contributor's Page > --- > > Key: KNOX-416 > URL: https://issues.apache.org/jira/browse/KNOX-416 > Project: Apache Knox > Issue Type: Improvement >Reporter: Vinay Shukla >Priority: Major > > Would be good to add the following to contributor's page > # When to use Manual testing against a Knox instance > # How to build a Knox tarball > # How to install Knox tarball and start/stop Knox - Link to user guide where > this is explained. > # Useful ant targets such as ant start-test-ldap, ant start-test-gateway & > ant start-debug-gateway -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-777) Address websocket scalability
[ https://issues.apache.org/jira/browse/KNOX-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657966#comment-16657966 ] Kevin Risden commented on KNOX-777: --- [~smore] - Do you have more details about how the implementation is taxing? > Address websocket scalability > - > > Key: KNOX-777 > URL: https://issues.apache.org/jira/browse/KNOX-777 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Sandeep More >Priority: Major > Fix For: 1.2.0 > > > Current websocket implementation is a bit taxing on memory it should be > lightweight and Knox should be able to support 500 - 1K concurrent > connections. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KNOX-888) testConcurrentProcessor fails intermittently with Timeout error
[
https://issues.apache.org/jira/browse/KNOX-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden closed KNOX-888.
-
Assignee: Kevin Risden
> testConcurrentProcessor fails intermittently with Timeout error
> ---
>
> Key: KNOX-888
> URL: https://issues.apache.org/jira/browse/KNOX-888
> Project: Apache Knox
> Issue Type: Bug
>Reporter: Yesha Vora
>Assignee: Kevin Risden
>Priority: Major
>
> testConcurrentProcessor fails intermittently with below error message.
> {code}
> Error Message
> test timed out after 12 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 12
> milliseconds
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1258)
> at java.lang.Thread.join(Thread.java:1332)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest.testConcurrentProcessor(JdbmQueueTest.java:201)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.lang.Thread.run(Thread.java:722)
> Standard Output
> Running org.apache.hadoop.gateway.audit.JdbmQueueTest#testConcurrentProcessor
> Standard Error
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at jdbm.recman.CacheRecordManager.rollback(CacheRecordManager.java:360)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.enqueue(JdbmQueue.java:60)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Producer.run(JdbmQueueTest.java:219)
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at jdbm.recman.CacheRecordManager.rollback(CacheRecordManager.java:360)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.enqueue(JdbmQueue.java:60)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Producer.run(JdbmQueueTest.java:219)
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at
> jdbm.recman.CacheRecordManager.getNamedObject(CacheRecordManager.java:376)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.getStat(JdbmQueue.java:136)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.dequeue(JdbmQueue.java:68)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.process(JdbmQueue.java:95)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Processor.run(JdbmQueueTest.java:260){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KNOX-888) testConcurrentProcessor fails intermittently with Timeout error
[
https://issues.apache.org/jira/browse/KNOX-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden updated KNOX-888:
--
Fix Version/s: (was: Future)
> testConcurrentProcessor fails intermittently with Timeout error
> ---
>
> Key: KNOX-888
> URL: https://issues.apache.org/jira/browse/KNOX-888
> Project: Apache Knox
> Issue Type: Bug
>Reporter: Yesha Vora
>Priority: Major
>
> testConcurrentProcessor fails intermittently with below error message.
> {code}
> Error Message
> test timed out after 12 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 12
> milliseconds
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1258)
> at java.lang.Thread.join(Thread.java:1332)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest.testConcurrentProcessor(JdbmQueueTest.java:201)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.lang.Thread.run(Thread.java:722)
> Standard Output
> Running org.apache.hadoop.gateway.audit.JdbmQueueTest#testConcurrentProcessor
> Standard Error
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at jdbm.recman.CacheRecordManager.rollback(CacheRecordManager.java:360)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.enqueue(JdbmQueue.java:60)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Producer.run(JdbmQueueTest.java:219)
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at jdbm.recman.CacheRecordManager.rollback(CacheRecordManager.java:360)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.enqueue(JdbmQueue.java:60)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Producer.run(JdbmQueueTest.java:219)
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at
> jdbm.recman.CacheRecordManager.getNamedObject(CacheRecordManager.java:376)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.getStat(JdbmQueue.java:136)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.dequeue(JdbmQueue.java:68)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.process(JdbmQueue.java:95)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Processor.run(JdbmQueueTest.java:260){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KNOX-888) testConcurrentProcessor fails intermittently with Timeout error
[
https://issues.apache.org/jira/browse/KNOX-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Risden resolved KNOX-888.
---
Resolution: Cannot Reproduce
> testConcurrentProcessor fails intermittently with Timeout error
> ---
>
> Key: KNOX-888
> URL: https://issues.apache.org/jira/browse/KNOX-888
> Project: Apache Knox
> Issue Type: Bug
>Reporter: Yesha Vora
>Priority: Major
>
> testConcurrentProcessor fails intermittently with below error message.
> {code}
> Error Message
> test timed out after 12 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 12
> milliseconds
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1258)
> at java.lang.Thread.join(Thread.java:1332)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest.testConcurrentProcessor(JdbmQueueTest.java:201)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.lang.Thread.run(Thread.java:722)
> Standard Output
> Running org.apache.hadoop.gateway.audit.JdbmQueueTest#testConcurrentProcessor
> Standard Error
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at jdbm.recman.CacheRecordManager.rollback(CacheRecordManager.java:360)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.enqueue(JdbmQueue.java:60)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Producer.run(JdbmQueueTest.java:219)
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at jdbm.recman.CacheRecordManager.rollback(CacheRecordManager.java:360)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.enqueue(JdbmQueue.java:60)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Producer.run(JdbmQueueTest.java:219)
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at
> jdbm.recman.CacheRecordManager.getNamedObject(CacheRecordManager.java:376)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.getStat(JdbmQueue.java:136)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.dequeue(JdbmQueue.java:68)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.process(JdbmQueue.java:95)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Processor.run(JdbmQueueTest.java:260){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KNOX-888) testConcurrentProcessor fails intermittently with Timeout error
[
https://issues.apache.org/jira/browse/KNOX-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657964#comment-16657964
]
Kevin Risden commented on KNOX-888:
---
I've been running a lot of tests lately and haven't seen this reproduce.
> testConcurrentProcessor fails intermittently with Timeout error
> ---
>
> Key: KNOX-888
> URL: https://issues.apache.org/jira/browse/KNOX-888
> Project: Apache Knox
> Issue Type: Bug
>Reporter: Yesha Vora
>Priority: Major
>
> testConcurrentProcessor fails intermittently with below error message.
> {code}
> Error Message
> test timed out after 12 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 12
> milliseconds
> at java.lang.Object.wait(Native Method)
> at java.lang.Thread.join(Thread.java:1258)
> at java.lang.Thread.join(Thread.java:1332)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest.testConcurrentProcessor(JdbmQueueTest.java:201)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.lang.Thread.run(Thread.java:722)
> Standard Output
> Running org.apache.hadoop.gateway.audit.JdbmQueueTest#testConcurrentProcessor
> Standard Error
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at jdbm.recman.CacheRecordManager.rollback(CacheRecordManager.java:360)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.enqueue(JdbmQueue.java:60)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Producer.run(JdbmQueueTest.java:219)
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at jdbm.recman.CacheRecordManager.rollback(CacheRecordManager.java:360)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.enqueue(JdbmQueue.java:60)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Producer.run(JdbmQueueTest.java:219)
> java.lang.IllegalStateException: ERR_538 RecordManager has been closed
> at
> jdbm.recman.CacheRecordManager.checkIfClosed(CacheRecordManager.java:400)
> at
> jdbm.recman.CacheRecordManager.getNamedObject(CacheRecordManager.java:376)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.getStat(JdbmQueue.java:136)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.dequeue(JdbmQueue.java:68)
> at
> org.apache.hadoop.gateway.audit.log4j.appender.JdbmQueue.process(JdbmQueue.java:95)
> at
> org.apache.hadoop.gateway.audit.JdbmQueueTest$Processor.run(JdbmQueueTest.java:260){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KNOX-955) Provide Knox client DSL for Kafka REST API
[ https://issues.apache.org/jira/browse/KNOX-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden reassigned KNOX-955: - Assignee: (was: Rick Kellogg) > Provide Knox client DSL for Kafka REST API > -- > > Key: KNOX-955 > URL: https://issues.apache.org/jira/browse/KNOX-955 > Project: Apache Knox > Issue Type: New Feature > Components: ClientDSL >Reporter: Rick Kellogg >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KNOX-955) Provide Knox client DSL for Kafka REST API
[ https://issues.apache.org/jira/browse/KNOX-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-955: -- Fix Version/s: (was: 1.2.0) > Provide Knox client DSL for Kafka REST API > -- > > Key: KNOX-955 > URL: https://issues.apache.org/jira/browse/KNOX-955 > Project: Apache Knox > Issue Type: New Feature > Components: ClientDSL >Reporter: Rick Kellogg >Assignee: Rick Kellogg >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-955) Provide Knox client DSL for Kafka REST API
[ https://issues.apache.org/jira/browse/KNOX-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657962#comment-16657962 ] Kevin Risden commented on KNOX-955: --- Removed fix version and unassigned since no patch. > Provide Knox client DSL for Kafka REST API > -- > > Key: KNOX-955 > URL: https://issues.apache.org/jira/browse/KNOX-955 > Project: Apache Knox > Issue Type: New Feature > Components: ClientDSL >Reporter: Rick Kellogg >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-1218) LDAP Group Lookup appears twice in User Guide TOC
[ https://issues.apache.org/jira/browse/KNOX-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657961#comment-16657961 ] Kevin Risden commented on KNOX-1218: This is still an issue with 1.1.0 user guide. > LDAP Group Lookup appears twice in User Guide TOC > - > > Key: KNOX-1218 > URL: https://issues.apache.org/jira/browse/KNOX-1218 > Project: Apache Knox > Issue Type: Bug > Components: Site >Affects Versions: 1.0.0, 1.1.0 >Reporter: Phil Zampino >Priority: Major > Fix For: 1.2.0 > > > In the User Guide TOC, under "Authentication", "LDAP Group Lookup" appears > twice, consecutively. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KNOX-1218) LDAP Group Lookup appears twice in User Guide TOC
[ https://issues.apache.org/jira/browse/KNOX-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1218: --- Affects Version/s: 1.1.0 > LDAP Group Lookup appears twice in User Guide TOC > - > > Key: KNOX-1218 > URL: https://issues.apache.org/jira/browse/KNOX-1218 > Project: Apache Knox > Issue Type: Bug > Components: Site >Affects Versions: 1.0.0, 1.1.0 >Reporter: Phil Zampino >Priority: Major > Fix For: 1.2.0 > > > In the User Guide TOC, under "Authentication", "LDAP Group Lookup" appears > twice, consecutively. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KNOX-1218) LDAP Group Lookup appears twice in User Guide TOC
[ https://issues.apache.org/jira/browse/KNOX-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1218: --- Fix Version/s: (was: 1.0.0) 1.2.0 > LDAP Group Lookup appears twice in User Guide TOC > - > > Key: KNOX-1218 > URL: https://issues.apache.org/jira/browse/KNOX-1218 > Project: Apache Knox > Issue Type: Bug > Components: Site >Affects Versions: 1.0.0, 1.1.0 >Reporter: Phil Zampino >Priority: Major > Fix For: 1.2.0 > > > In the User Guide TOC, under "Authentication", "LDAP Group Lookup" appears > twice, consecutively. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KNOX-1237) Knox DSL should support HBase Stateless Scanner
[ https://issues.apache.org/jira/browse/KNOX-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1237: --- Fix Version/s: 1.2.0 > Knox DSL should support HBase Stateless Scanner > --- > > Key: KNOX-1237 > URL: https://issues.apache.org/jira/browse/KNOX-1237 > Project: Apache Knox > Issue Type: Improvement > Components: ClientDSL >Reporter: Kevin Risden >Assignee: Dequan Chen >Priority: Minor > Fix For: 1.2.0 > > Attachments: KNOX-1237.patch > > > KNOX-8 added support for HBase REST apis via Knox. The Knox DSL supports > stateful scanners as shown in the documentation > (https://knox.apache.org/books/knox-1-0-0/user-guide.html#table(String+tableName).scanner().create()+-+Scanner+Creation). > HBase REST supports stateless scanners > ([https://hbase.apache.org/1.2/apidocs/org/apache/hadoop/hbase/rest/package-summary.html#operation_stateless_scanner]) > which can be easily load balanced. The feature is not well documented in > HBase REST. > Currently if using stateful scanners and Knox or HBase REST is being load > balanced, there will be an issue using that scanner. The stateless scanners > avoid this since they have all the information necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-1237) Knox DSL should support HBase Stateless Scanner
[ https://issues.apache.org/jira/browse/KNOX-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657957#comment-16657957 ] Kevin Risden commented on KNOX-1237: Thanks set the flag patch available and fix version to 1.2.0 to make sure to look at it. > Knox DSL should support HBase Stateless Scanner > --- > > Key: KNOX-1237 > URL: https://issues.apache.org/jira/browse/KNOX-1237 > Project: Apache Knox > Issue Type: Improvement > Components: ClientDSL >Reporter: Kevin Risden >Assignee: Dequan Chen >Priority: Minor > Fix For: 1.2.0 > > Attachments: KNOX-1237.patch > > > KNOX-8 added support for HBase REST apis via Knox. The Knox DSL supports > stateful scanners as shown in the documentation > (https://knox.apache.org/books/knox-1-0-0/user-guide.html#table(String+tableName).scanner().create()+-+Scanner+Creation). > HBase REST supports stateless scanners > ([https://hbase.apache.org/1.2/apidocs/org/apache/hadoop/hbase/rest/package-summary.html#operation_stateless_scanner]) > which can be easily load balanced. The feature is not well documented in > HBase REST. > Currently if using stateful scanners and Knox or HBase REST is being load > balanced, there will be an issue using that scanner. The stateless scanners > avoid this since they have all the information necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KNOX-1237) Knox DSL should support HBase Stateless Scanner
[ https://issues.apache.org/jira/browse/KNOX-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1237: --- Status: Patch Available (was: Open) > Knox DSL should support HBase Stateless Scanner > --- > > Key: KNOX-1237 > URL: https://issues.apache.org/jira/browse/KNOX-1237 > Project: Apache Knox > Issue Type: Improvement > Components: ClientDSL >Reporter: Kevin Risden >Assignee: Dequan Chen >Priority: Minor > Attachments: KNOX-1237.patch > > > KNOX-8 added support for HBase REST apis via Knox. The Knox DSL supports > stateful scanners as shown in the documentation > (https://knox.apache.org/books/knox-1-0-0/user-guide.html#table(String+tableName).scanner().create()+-+Scanner+Creation). > HBase REST supports stateless scanners > ([https://hbase.apache.org/1.2/apidocs/org/apache/hadoop/hbase/rest/package-summary.html#operation_stateless_scanner]) > which can be easily load balanced. The feature is not well documented in > HBase REST. > Currently if using stateful scanners and Knox or HBase REST is being load > balanced, there will be an issue using that scanner. The stateless scanners > avoid this since they have all the information necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-1316) API 404 responses should not contain server details
[
https://issues.apache.org/jira/browse/KNOX-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657956#comment-16657956
]
Kevin Risden commented on KNOX-1316:
Pretty sure this is possible as shown here:
https://stackoverflow.com/questions/15652902/remove-the-http-server-header-in-jetty-9
> API 404 responses should not contain server details
> ---
>
> Key: KNOX-1316
> URL: https://issues.apache.org/jira/browse/KNOX-1316
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
>Affects Versions: 1.0.0
>Reporter: Phil Zampino
>Priority: Minor
> Fix For: 1.2.0
>
>
> For an invalid resource request, which results in a 404 response:
> {noformat}
> GET /gatewayipxllql46j/manager/api/v1/topologies/my-new-desc{noformat}
> Knox currently returns some server details and the request URL.
> {noformat}
> HTTP/1.1 404 Not Found
> Date: Thu, 10 May 2018 12:16:13 GMT
> Cache-Control: must-revalidate,no-cache,no-store
> Content-Type: text/html; charset=ISO-8859-1
> Content-Length: 333
> Connection: close
> Server: Jetty(9.2.15.v20160210)
> content="text/html;charset=ISO-8859-1"/>Error 404
> HTTP ERROR: 404Problem accessing
> /gatewayipxllql46j/manager/api/v1/topologies/my-new-desc. Reason: Not
> FoundPowered by
> Jetty://{noformat}
> Generic responses are preferred for security reasons, and Jetty should
> support the configuration of such a generic response for these cases.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KNOX-1321) Livy service.xml does not apply addusername rule to /batches endpoint
[
https://issues.apache.org/jira/browse/KNOX-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657951#comment-16657951
]
Kevin Risden commented on KNOX-1321:
[~jesus.alv] - Are you planning to submit a patch for this?
> Livy service.xml does not apply addusername rule to /batches endpoint
> -
>
> Key: KNOX-1321
> URL: https://issues.apache.org/jira/browse/KNOX-1321
> Project: Apache Knox
> Issue Type: Bug
>Affects Versions: 0.14.0
>Reporter: Jesus Alvarez
>Assignee: Jesus Alvarez
>Priority: Major
>
> When a request is made to Livy via Knox today:
> 1, Spark Magic sends a JSON body to knox, ex:
> {"driverMemory":"2G","executorCores":4,"executorMemory":"8G","proxyUser":"alice"}
> 2, Knox's service.xml will rewrite the proxyUser "alice" to the actual
> authenticated username:
>
> {code:java}
>
>
>
>
>
> {code}
>
>
> Using the rewrite.xml rules:
>
> {code:java}
>
>
>
>
>
>
>
>
> {code}
>
>
> The issue here is that requests made to
> *knox:port/gateway/topology/livy/v1/batches* will not apply the same rewrite
> rule.
>
>
> https://livy.incubator.apache.org/docs/latest/rest-api.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KNOX-1407) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/KNOX-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1407: --- Fix Version/s: 1.2.0 > Please delete old releases from mirroring system > > > Key: KNOX-1407 > URL: https://issues.apache.org/jira/browse/KNOX-1407 > Project: Apache Knox > Issue Type: Task > Environment: https://dist.apache.org/repos/dist/release/knox/ >Reporter: Sebb >Priority: Major > Fix For: 1.2.0 > > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > AFAICT all but the latest release should be deleted from the mirrors. > It's unfair to expect the 3rd party mirrors to carry old releases. > However you can still link to the archives for historic releases. > Please also update your release procedures (if relevant) > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KNOX-1407) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/KNOX-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16657950#comment-16657950 ] Kevin Risden commented on KNOX-1407: We should take care of this as part of the 1.2.0 release. > Please delete old releases from mirroring system > > > Key: KNOX-1407 > URL: https://issues.apache.org/jira/browse/KNOX-1407 > Project: Apache Knox > Issue Type: Task > Environment: https://dist.apache.org/repos/dist/release/knox/ >Reporter: Sebb >Priority: Major > Fix For: 1.2.0 > > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > AFAICT all but the latest release should be deleted from the mirrors. > It's unfair to expect the 3rd party mirrors to carry old releases. > However you can still link to the archives for historic releases. > Please also update your release procedures (if relevant) > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
