| clear query|facets|time |
Search criteria: .
Results from 111 to 120 from
488 (0.144s).
|
|
|
Loading phrases to help you
refine your search...
|
|
[HDFS-3955] QJM: Make acceptRecovery() atomic - HDFS - [issue]
|
|
...Per one of the TODOs in Journal.java, there is currently a lack of atomicity in the acceptRecovery() code path. In particular, we have the following actions executed non-atomically: Download...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3955
Author: Todd Lipcon,
2012-09-19, 19:57
|
|
|
[HDFS-3958] Integrate upgrade/finalize/rollback with external journals - HDFS - [issue]
|
|
...Currently the NameNode upgrade/rollback/finalize framework only supports local storage. With edits being stored in pluggable Journals, this could create certain difficulties - in particular,...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3958
Author: Todd Lipcon,
2012-09-19, 10:36
|
|
|
[HDFS-3943] QJM: remove currently unused "md5sum" field. - HDFS - [issue]
|
|
...Per later discussion in HDFS-3859, it turns out to be rather difficult to integrate md5sum verification into QJM at this point. The crux of the issue is that different replicas may be semant...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3943
Author: Todd Lipcon,
2012-09-17, 22:52
|
|
|
[HDFS-3859] QJM: implement md5sum verification - HDFS - [issue]
|
|
...When the QJM passes journal segments between nodes, it should use an md5sum field to make sure the data doesn't get corrupted during transit. This also serves as an extra safe-guard to make ...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3859
Author: Todd Lipcon,
2012-09-17, 22:28
|
|
|
[HDFS-3894] QJM: testRecoverAfterDoubleFailures can be flaky due to IPC client caching - HDFS - [issue]
|
|
...TestQJMWithFaults.testRecoverAfterDoubleFailures fails really occasionally. Looking into it, the issue seems to be that it's possible by random chance for an IPC server port to be reused bet...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3894
Author: Todd Lipcon,
2012-09-14, 00:00
|
|
|
[HDFS-3906] QJM: quorum timeout on failover with large log segment - HDFS - [issue]
|
|
...In doing some stress tests, I ran into an issue with failover if the current edit log segment written by the old active is large. With a 327MB log segment containing 6.4M transactions, the J...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3906
Author: Todd Lipcon,
2012-09-11, 07:32
|
|
|
[HDFS-862] Potential NN deadlock in processDistributedUpgradeCommand - HDFS - [issue]
|
|
...Haven't seen this in practice, but the lock order is inconsistent. processReport locks FSNamesystem, then calls UpgradeManager.startUpgrade, getUpgradeState, and getUpgradeStatus (each of wh...
|
|
|
http://issues.apache.org/jira/browse/HDFS-862
Author: Todd Lipcon,
2012-09-11, 06:57
|
|
|
[HDFS-3915] QJM: Failover fails with auth error in secure cluster - HDFS - [issue]
|
|
...When testing failover in a secure cluster with QJM, we ran into the following error:java.io.IOException: Exception trying to open authenticated connection to http://xxxxx:8480/getJournal?jid...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3915
Author: Todd Lipcon,
2012-09-11, 05:53
|
|
|
[HDFS-3914] QJM: acceptRecovery should abort current segment - HDFS - [issue]
|
|
...Found this bug with randomized testing. The following sequence causes a problem: JN writing segment starting at txid 1, and successfully wrote txid 1, but no more JN becomes partitioned from...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3914
Author: Todd Lipcon,
2012-09-11, 00:21
|
|
|
[HDFS-3899] QJM: Writer-side metrics - HDFS - [issue]
|
|
...We already have some metrics on the server side (JournalNode) but it's useful to also gather metrics from the client side (NameNode). This is important in order to monitor that the client is...
|
|
|
http://issues.apache.org/jira/browse/HDFS-3899
Author: Todd Lipcon,
2012-09-10, 23:40
|
|
|
|
