zhangsong created KUDU-2010:
---
Summary: java kudu client get wrong column info from kudu-master
Key: KUDU-2010
URL: https://issues.apache.org/jira/browse/KUDU-2010
Project: Kudu
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KUDU-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangsong updated KUDU-1989:
Description:
kudu-tserver version: 1.0.0
1 firstly node crashed
2 when trying to restart the kudu-tserver ,
zhangsong created KUDU-1989:
---
Summary: kudu-tserver met checksum mismatch after node crash and
restart.
Key: KUDU-1989
URL: https://issues.apache.org/jira/browse/KUDU-1989
Project: Kudu
Issue
[
https://issues.apache.org/jira/browse/KUDU-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangsong resolved KUDU-1847.
-
Resolution: Invalid
Fix Version/s: 1.0.0
> kudu-tserver should remove itself from raft-peer-config
[
https://issues.apache.org/jira/browse/KUDU-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangsong reassigned KUDU-1579:
---
Assignee: zhangsong
> into "safe mode" when large number of node crash
>
[
https://issues.apache.org/jira/browse/KUDU-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823558#comment-15823558
]
zhangsong commented on KUDU-1579:
-
After experiencing several node failure cases(using kudu-tserver
[
https://issues.apache.org/jira/browse/KUDU-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731317#comment-15731317
]
zhangsong edited comment on KUDU-1794 at 12/8/16 6:47 AM:
--
Yes,this issue map to
[
https://issues.apache.org/jira/browse/KUDU-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731317#comment-15731317
]
zhangsong edited comment on KUDU-1794 at 12/8/16 6:47 AM:
--
Yes,this issue map to
zhangsong created KUDU-1794:
---
Summary: kuduScanner 's problem causing impala crash.
Key: KUDU-1794
URL: https://issues.apache.org/jira/browse/KUDU-1794
Project: Kudu
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KUDU-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715098#comment-15715098
]
zhangsong commented on KUDU-1721:
-
[~mpercy] sure, yes~
> Expose ability to force an unsafe Raft
[
https://issues.apache.org/jira/browse/KUDU-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangsong reassigned KUDU-1721:
---
Assignee: zhangsong
> Expose ability to force an unsafe Raft configuration change
>
[
https://issues.apache.org/jira/browse/KUDU-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692771#comment-15692771
]
zhangsong commented on KUDU-1759:
-
May be related with 1483
> Tablet/table unable to serve write after
[
https://issues.apache.org/jira/browse/KUDU-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangsong resolved KUDU-1758.
-
Resolution: Duplicate
Fix Version/s: 1.0.1
> Tablet/table unable to serve write after node crash
zhangsong created KUDU-1759:
---
Summary: Tablet/table unable to serve write after node crash and
restart.
Key: KUDU-1759
URL: https://issues.apache.org/jira/browse/KUDU-1759
Project: Kudu
Issue
zhangsong created KUDU-1758:
---
Summary: Tablet/table unable to serve write after node crash and
restart.
Key: KUDU-1758
URL: https://issues.apache.org/jira/browse/KUDU-1758
Project: Kudu
Issue
[
https://issues.apache.org/jira/browse/KUDU-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15634917#comment-15634917
]
zhangsong edited comment on KUDU-1736 at 11/4/16 1:55 AM:
--
Sorry, i forgot to dump
[
https://issues.apache.org/jira/browse/KUDU-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15634917#comment-15634917
]
zhangsong edited comment on KUDU-1736 at 11/4/16 1:54 AM:
--
Sorry, i forgot to dump
[
https://issues.apache.org/jira/browse/KUDU-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15634917#comment-15634917
]
zhangsong edited comment on KUDU-1736 at 11/4/16 1:51 AM:
--
Sorry, i forgot to dump
[
https://issues.apache.org/jira/browse/KUDU-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15634917#comment-15634917
]
zhangsong commented on KUDU-1736:
-
Sorry, i forgot to dump the log, will check whether the log still exist
zhangsong created KUDU-1736:
---
Summary: kudu crash in debug build: unordered undo delta
Key: KUDU-1736
URL: https://issues.apache.org/jira/browse/KUDU-1736
Project: Kudu
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KUDU-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607179#comment-15607179
]
zhangsong commented on KUDU-1551:
-
[~tlipcon] for the workaround , in below code , pit_schema will be empty
[
https://issues.apache.org/jira/browse/KUDU-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15604950#comment-15604950
]
zhangsong commented on KUDU-1483:
-
Agree this is a potential risk , especially when met large number of
[
https://issues.apache.org/jira/browse/KUDU-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangsong resolved KUDU-1462.
-
Resolution: Cannot Reproduce
Fix Version/s: 0.9.0
0.9.1
> when init Tablet
[
https://issues.apache.org/jira/browse/KUDU-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473790#comment-15473790
]
zhangsong commented on KUDU-1442:
-
Every time i restart a kudu-tserver , i first see these logs:
"Log line
[
https://issues.apache.org/jira/browse/KUDU-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473790#comment-15473790
]
zhangsong edited comment on KUDU-1442 at 9/8/16 12:53 PM:
--
Every time i restart a
zhangsong created KUDU-1591:
---
Summary: kudu table can not be deleted when tablets of it only has
one leader .
Key: KUDU-1591
URL: https://issues.apache.org/jira/browse/KUDU-1591
Project: Kudu
[
https://issues.apache.org/jira/browse/KUDU-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457444#comment-15457444
]
zhangsong edited comment on KUDU-1573 at 9/2/16 4:06 AM:
-
Great~
So the root cause
zhangsong created KUDU-1579:
---
Summary: into "safe mode" when large number of node crash
Key: KUDU-1579
URL: https://issues.apache.org/jira/browse/KUDU-1579
Project: Kudu
Issue Type: New Feature
zhangsong created KUDU-1578:
---
Summary: kudu-tserver should refuse service or "freeze" instead of
crash
Key: KUDU-1578
URL: https://issues.apache.org/jira/browse/KUDU-1578
Project: Kudu
Issue
[
https://issues.apache.org/jira/browse/KUDU-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432525#comment-15432525
]
zhangsong commented on KUDU-1576:
-
last line of kudu-tserver.INFO on replica 2:
I0819 11:08:39.935573
[
https://issues.apache.org/jira/browse/KUDU-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432525#comment-15432525
]
zhangsong edited comment on KUDU-1576 at 8/23/16 9:52 AM:
--
the time line is like:
zhangsong created KUDU-1551:
---
Summary: kudu-tserver can not start up after experience node crash
Key: KUDU-1551
URL: https://issues.apache.org/jira/browse/KUDU-1551
Project: Kudu
Issue Type: Bug
zhangsong created KUDU-1550:
---
Summary: remote_bootstrap should avoid starting the entire process
over again when `bootstrap_source` node crashes before remote_bootstrap
complete.
Key: KUDU-1550
URL:
zhangsong created KUDU-1549:
---
Summary: recovery speed of kudu-tserver should be faster.
Key: KUDU-1549
URL: https://issues.apache.org/jira/browse/KUDU-1549
Project: Kudu
Issue Type: Improvement
34 matches
Mail list logo