[
https://issues.apache.org/jira/browse/HDDS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613849#comment-16613849
]
Nilotpal Nandi commented on HDDS-451:
-
Reran the test -
50GB putKey operation was successful
> PutKey
[
https://issues.apache.org/jira/browse/HDDS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-451:
Attachment: all-node-ozone-logs-1536841590.tar.gz
> PutKey failed due to error "Rejecting write
[
https://issues.apache.org/jira/browse/HDDS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16613417#comment-16613417
]
Nilotpal Nandi commented on HDDS-451:
-
logs from all nodes present here :
Nilotpal Nandi created HDDS-451:
---
Summary: PutKey failed due to error "Rejecting write chunk
request. Chunk overwrite without explicit request"
Key: HDDS-451
URL: https://issues.apache.org/jira/browse/HDDS-451
[
https://issues.apache.org/jira/browse/HDDS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609702#comment-16609702
]
Nilotpal Nandi commented on HDDS-420:
-
[~shashikant] : logs from all nodes present in this tar file:
[
https://issues.apache.org/jira/browse/HDDS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-420:
Attachment: all-node-ozone-logs-1536607597.tar.gz
> putKey failing with KEY_ALLOCATION_ERROR
>
[
https://issues.apache.org/jira/browse/HDDS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-420:
Priority: Blocker (was: Critical)
> putKey failing with KEY_ALLOCATION_ERROR
>
Nilotpal Nandi created HDDS-420:
---
Summary: putKey failing with KEY_ALLOCATION_ERROR
Key: HDDS-420
URL: https://issues.apache.org/jira/browse/HDDS-420
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi resolved HDDS-321.
-
Resolution: Fixed
> ozoneFS put/copyFromLocal command does not work for a directory when the
>
[
https://issues.apache.org/jira/browse/HDDS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16607070#comment-16607070
]
Nilotpal Nandi commented on HDDS-321:
-
it is working now :
ran hadoop@7ebaa76cfa20:~/bin/test2$
[
https://issues.apache.org/jira/browse/HDDS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi reassigned HDDS-321:
---
Assignee: Nilotpal Nandi
> ozoneFS put/copyFromLocal command does not work for a directory
Nilotpal Nandi created HDDS-410:
---
Summary: ozone scmcli is not working properly
Key: HDDS-410
URL: https://issues.apache.org/jira/browse/HDDS-410
Project: Hadoop Distributed Data Store
Issue
Nilotpal Nandi created HDDS-408:
---
Summary: Read (getKey) operation is very slow
Key: HDDS-408
URL: https://issues.apache.org/jira/browse/HDDS-408
Project: Hadoop Distributed Data Store
Issue
[
https://issues.apache.org/jira/browse/HDDS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605807#comment-16605807
]
Nilotpal Nandi commented on HDDS-407:
-
Issue is with the nodes having ozone manager and scm , for other
Nilotpal Nandi created HDDS-407:
---
Summary: ozone logs are wriiten to ozone.log. instead of
ozone.log
Key: HDDS-407
URL: https://issues.apache.org/jira/browse/HDDS-407
Project: Hadoop Distributed Data
Nilotpal Nandi created HDDS-403:
---
Summary: infoKey shows wrong "createdOn", "modifiedOn" metadata
for key
Key: HDDS-403
URL: https://issues.apache.org/jira/browse/HDDS-403
Project: Hadoop Distributed
[
https://issues.apache.org/jira/browse/HDDS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi reassigned HDDS-337:
---
Assignee: Dinesh Chitlangia (was: Nilotpal Nandi)
> keys created with key name having
[
https://issues.apache.org/jira/browse/HDDS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598248#comment-16598248
]
Nilotpal Nandi commented on HDDS-337:
-
[~dineshchitlangia] - assigning it to you.
> keys created with
[
https://issues.apache.org/jira/browse/HDDS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578266#comment-16578266
]
Nilotpal Nandi commented on HDDS-314:
-
Thanks for reviewing the patch [~elek] . I have uploaded a new
[
https://issues.apache.org/jira/browse/HDDS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-314:
Attachment: HDDS-314.003.patch
> ozoneShell putKey command overwrites the existing key having same
[
https://issues.apache.org/jira/browse/HDDS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-314:
Attachment: HDDS-314.002.patch
> ozoneShell putKey command overwrites the existing key having same
[
https://issues.apache.org/jira/browse/HDDS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-338:
Description:
steps taken :
--
1. created a directory through ozoneFS
Nilotpal Nandi created HDDS-338:
---
Summary: ozoneFS allows to create file key and directory key with
same keyname
Key: HDDS-338
URL: https://issues.apache.org/jira/browse/HDDS-338
Project: Hadoop
Nilotpal Nandi created HDDS-337:
---
Summary: keys created with key name having special
character/wildcard should not allowed
Key: HDDS-337
URL: https://issues.apache.org/jira/browse/HDDS-337
Project:
[
https://issues.apache.org/jira/browse/HDDS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi reassigned HDDS-337:
---
Assignee: Nilotpal Nandi
> keys created with key name having special character/wildcard
[
https://issues.apache.org/jira/browse/HDDS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-314:
Attachment: HDDS-314.001.patch
> ozoneShell putKey command overwrites the existing key having same
[
https://issues.apache.org/jira/browse/HDDS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-314:
Status: Patch Available (was: Open)
> ozoneShell putKey command overwrites the existing key having
[
https://issues.apache.org/jira/browse/HDDS-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-301:
Attachment: HDDS-301.002.patch
> ozone does not contain subcommand to run ozoneFS commands
>
Nilotpal Nandi created HDDS-321:
---
Summary: ozoneFS put/copyFromLocal command does not work for a
directory when the directory contains file(s) as well as subdirectories
Key: HDDS-321
URL:
Nilotpal Nandi created HDDS-318:
---
Summary: ratis INFO logs should not shown during ozoneFs
command-line execution
Key: HDDS-318
URL: https://issues.apache.org/jira/browse/HDDS-318
Project: Hadoop
Nilotpal Nandi created HDDS-315:
---
Summary: ozoneShell infoKey does not work for directories created
as key and throws 'KEY_NOT_FOUND' error
Key: HDDS-315
URL: https://issues.apache.org/jira/browse/HDDS-315
[
https://issues.apache.org/jira/browse/HDDS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi reassigned HDDS-314:
---
Assignee: Nilotpal Nandi
> ozoneShell putKey command overwrites the existing key having same
Nilotpal Nandi created HDDS-314:
---
Summary: ozoneShell putKey command overwrites the existing key
having same name
Key: HDDS-314
URL: https://issues.apache.org/jira/browse/HDDS-314
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDDS-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-301:
Status: Patch Available (was: Open)
> ozone does not contain subcommand to run ozoneFS commands
>
[
https://issues.apache.org/jira/browse/HDDS-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-301:
Attachment: HDDS-301.001.patch
> ozone does not contain subcommand to run ozoneFS commands
>
Nilotpal Nandi created HDDS-301:
---
Summary: ozone does not contain subcommand to run ozoneFS commands
Key: HDDS-301
URL: https://issues.apache.org/jira/browse/HDDS-301
Project: Hadoop Distributed Data
[
https://issues.apache.org/jira/browse/HDDS-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi reassigned HDDS-301:
---
Assignee: Nilotpal Nandi
> ozone does not contain subcommand to run ozoneFS commands
>
[
https://issues.apache.org/jira/browse/HDDS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-283:
Attachment: HDDS-283.001.patch
> Need an option to list all volumes created in the cluster
>
[
https://issues.apache.org/jira/browse/HDDS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-283:
Status: Patch Available (was: Open)
> Need an option to list all volumes created in the cluster
>
[
https://issues.apache.org/jira/browse/HDDS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi reassigned HDDS-283:
---
Assignee: Nilotpal Nandi
> Need an option to list all volumes created in the cluster
>
Nilotpal Nandi created HDDS-283:
---
Summary: Need an option to list all volumes created in the cluster
Key: HDDS-283
URL: https://issues.apache.org/jira/browse/HDDS-283
Project: Hadoop Distributed Data
Nilotpal Nandi created HDDS-281:
---
Summary: Need container size distribution metric in OzoneManager UI
Key: HDDS-281
URL: https://issues.apache.org/jira/browse/HDDS-281
Project: Hadoop Distributed Data
[
https://issues.apache.org/jira/browse/HDDS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-275:
Status: Patch Available (was: Open)
> DeleteVolume command does not give any confirmation message
[
https://issues.apache.org/jira/browse/HDDS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-275:
Attachment: HDDS-275.001.patch
> DeleteVolume command does not give any confirmation message on
[
https://issues.apache.org/jira/browse/HDDS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi reassigned HDDS-275:
---
Assignee: Nilotpal Nandi
> DeleteVolume command does not give any confirmation message on
Nilotpal Nandi created HDDS-275:
---
Summary: DeleteVolume command does not give any confirmation
message on successful execution
Key: HDDS-275
URL: https://issues.apache.org/jira/browse/HDDS-275
Nilotpal Nandi created HDDS-264:
---
Summary: 'oz' subcommand reference is not present in 'ozone'
command help
Key: HDDS-264
URL: https://issues.apache.org/jira/browse/HDDS-264
Project: Hadoop Distributed
[
https://issues.apache.org/jira/browse/HDDS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-208:
Status: Patch Available (was: Open)
> ozone createVolume command ignores the first character of the
[
https://issues.apache.org/jira/browse/HDDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-207:
Status: Patch Available (was: Open)
> ozone listVolume command accepts random values as argument
>
[
https://issues.apache.org/jira/browse/HDDS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-210:
Description:
ozone getKey command always expects the filename to be present along with the
[
https://issues.apache.org/jira/browse/HDDS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-210:
Description:
ozone getKey command always expects the filename to be present along with the
[
https://issues.apache.org/jira/browse/HDDS-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-210:
Environment:
was:
ozone getKey command always expects the filename to be present along with
Nilotpal Nandi created HDDS-210:
---
Summary: ozone getKey command always expects the filename to be
present along with file-path in "-file" argument
Key: HDDS-210
URL: https://issues.apache.org/jira/browse/HDDS-210
[
https://issues.apache.org/jira/browse/HDDS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-209:
Description:
user "test_user3" does not exist locally.
When -createVolume command is ran for the
Nilotpal Nandi created HDDS-209:
---
Summary: createVolume command throws error when user is not
present locally but creates the volume
Key: HDDS-209
URL: https://issues.apache.org/jira/browse/HDDS-209
[
https://issues.apache.org/jira/browse/HDDS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi reassigned HDDS-208:
---
Assignee: Lokesh Jain
> ozone createVolume command ignores the first character of the "volume
Nilotpal Nandi created HDDS-208:
---
Summary: ozone createVolume command ignores the first character of
the "volume name" given as argument
Key: HDDS-208
URL: https://issues.apache.org/jira/browse/HDDS-208
[
https://issues.apache.org/jira/browse/HDDS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-206:
Status: Patch Available (was: Open)
> default port number taken by ksm is 9862 while listing the
[
https://issues.apache.org/jira/browse/HDDS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-207:
Description:
When no argument from listVolume is provided, it complains.
But a random argument is
Nilotpal Nandi created HDDS-207:
---
Summary: ozone listVolume command accepts random values as argument
Key: HDDS-207
URL: https://issues.apache.org/jira/browse/HDDS-207
Project: Hadoop Distributed Data
Nilotpal Nandi created HDDS-206:
---
Summary: default port number taken by ksm is 9862 while listing
the volumes
Key: HDDS-206
URL: https://issues.apache.org/jira/browse/HDDS-206
Project: Hadoop
201 - 261 of 261 matches
Mail list logo