[jira] [Assigned] (KUDU-2254) Detect and warn about misusage of KuduContext in spark applications
[ https://issues.apache.org/jira/browse/KUDU-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao reassigned KUDU-2254: - Assignee: Hao Hao > Detect and warn about misusage of KuduContext in spark applications > --- > > Key: KUDU-2254 > URL: https://issues.apache.org/jira/browse/KUDU-2254 > Project: Kudu > Issue Type: Improvement > Components: spark >Affects Versions: 1.5.0 >Reporter: Hao Hao >Assignee: Hao Hao > > Since KuduContext carries a bunch of information for client connection, such > as authentication token, KuduContext should be created in the driver and > shared with executors. > Even if we have put comments for KuduContext class > (https://github.com/apache/kudu/blob/master/java/kudu-spark/src/main/scala/org/apache/kudu/spark/kudu/KuduContext.scala#L43), > it would be great to provide a way to warn users (e.g Logging) about such > behavior since this kind of issues are very subtle to detect. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KUDU-2115) Fix rowset compaction selection race
[ https://issues.apache.org/jira/browse/KUDU-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wong updated KUDU-2115: -- Resolution: Fixed Fix Version/s: 1.7.0 Status: Resolved (was: In Review) Fixed in f2adee0046c553ca2a697b661da11846d34559fd > Fix rowset compaction selection race > > > Key: KUDU-2115 > URL: https://issues.apache.org/jira/browse/KUDU-2115 > Project: Kudu > Issue Type: Bug > Components: tablet >Affects Versions: 1.3.0 >Reporter: Will Berkeley >Assignee: Andrew Wong > Fix For: 1.7.0 > > > KUDU-1956 identified a race in selecting rowsets for compaction. Todd applied > a workaround that prevents the server from crashing when this happens, but > the race itself remains. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KUDU-1867) Improve the "Could not lock .../block_manager_instance" error message
[
https://issues.apache.org/jira/browse/KUDU-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320704#comment-16320704
]
Jean-Daniel Cryans commented on KUDU-1867:
--
[~evinhas] this is not a bug, this jira is about improving an error message.
You're still going to get an error due to the underlying issue which might be
that the file has the wrong permissions or something like that.
> Improve the "Could not lock .../block_manager_instance" error message
> -
>
> Key: KUDU-1867
> URL: https://issues.apache.org/jira/browse/KUDU-1867
> Project: Kudu
> Issue Type: Bug
> Components: fs
>Affects Versions: 1.2.0
>Reporter: Jean-Daniel Cryans
> Labels: newbie
>
> It's possible for users to encounter a rather cryptic error when trying to
> run Kudu while it's already running or with a different user than what was
> previously used:
> {code}
> Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could
> not lock /path/to/data/block_manager_instance: Could not lock
> /path/to/data/block_manager_instance: lock
> /path/to/data/block_manager_instance: Resource temporarily unavailable (error
> 11)
> {code}
> This is the log line that we FATAL with, so unless you already know what it
> means you're left to your own guessing and log digging. Instead, the error
> message could be more prescriptive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KUDU-1867) Improve the "Could not lock .../block_manager_instance" error message
[
https://issues.apache.org/jira/browse/KUDU-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans updated KUDU-1867:
-
Target Version/s: Backlog (was: 1.5.0)
> Improve the "Could not lock .../block_manager_instance" error message
> -
>
> Key: KUDU-1867
> URL: https://issues.apache.org/jira/browse/KUDU-1867
> Project: Kudu
> Issue Type: Bug
> Components: fs
>Affects Versions: 1.2.0
>Reporter: Jean-Daniel Cryans
> Labels: newbie
>
> It's possible for users to encounter a rather cryptic error when trying to
> run Kudu while it's already running or with a different user than what was
> previously used:
> {code}
> Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could
> not lock /path/to/data/block_manager_instance: Could not lock
> /path/to/data/block_manager_instance: lock
> /path/to/data/block_manager_instance: Resource temporarily unavailable (error
> 11)
> {code}
> This is the log line that we FATAL with, so unless you already know what it
> means you're left to your own guessing and log digging. Instead, the error
> message could be more prescriptive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (KUDU-1867) Improve the "Could not lock .../block_manager_instance" error message
[
https://issues.apache.org/jira/browse/KUDU-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319971#comment-16319971
]
Ed Vin edited comment on KUDU-1867 at 1/10/18 10:06 AM:
Excuse me but, is there any plan for getting solved this issue? It was proposed
to be fixed by version 1.5, but it wasn't. Current version 1.6 is not solving
the issue.
Please, could anyone update the issue to add the expected target version when
issue will be solved?
Thanks in advance.
was (Author: evinhas):
Excuse me but, is there any plan for getting solved this issue?
> Improve the "Could not lock .../block_manager_instance" error message
> -
>
> Key: KUDU-1867
> URL: https://issues.apache.org/jira/browse/KUDU-1867
> Project: Kudu
> Issue Type: Bug
> Components: fs
>Affects Versions: 1.2.0
>Reporter: Jean-Daniel Cryans
> Labels: newbie
>
> It's possible for users to encounter a rather cryptic error when trying to
> run Kudu while it's already running or with a different user than what was
> previously used:
> {code}
> Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could
> not lock /path/to/data/block_manager_instance: Could not lock
> /path/to/data/block_manager_instance: lock
> /path/to/data/block_manager_instance: Resource temporarily unavailable (error
> 11)
> {code}
> This is the log line that we FATAL with, so unless you already know what it
> means you're left to your own guessing and log digging. Instead, the error
> message could be more prescriptive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KUDU-1867) Improve the "Could not lock .../block_manager_instance" error message
[
https://issues.apache.org/jira/browse/KUDU-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16319971#comment-16319971
]
Ed Vin commented on KUDU-1867:
--
Excuse me but, is there any plan for getting solved this issue?
> Improve the "Could not lock .../block_manager_instance" error message
> -
>
> Key: KUDU-1867
> URL: https://issues.apache.org/jira/browse/KUDU-1867
> Project: Kudu
> Issue Type: Bug
> Components: fs
>Affects Versions: 1.2.0
>Reporter: Jean-Daniel Cryans
> Labels: newbie
>
> It's possible for users to encounter a rather cryptic error when trying to
> run Kudu while it's already running or with a different user than what was
> previously used:
> {code}
> Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could
> not lock /path/to/data/block_manager_instance: Could not lock
> /path/to/data/block_manager_instance: lock
> /path/to/data/block_manager_instance: Resource temporarily unavailable (error
> 11)
> {code}
> This is the log line that we FATAL with, so unless you already know what it
> means you're left to your own guessing and log digging. Instead, the error
> message could be more prescriptive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
