[jira] [Assigned] (KUDU-2032) Kerberos authentication fails with rdns disabled in krb5.conf

2017-08-15 Thread Todd Lipcon (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon reassigned KUDU-2032: - Assignee: Todd Lipcon > Kerberos authentication fails with rdns disabled in krb5.conf >

[jira] [Resolved] (KUDU-2091) Certificates with intermediate CA's do not work with Kudu

2017-08-15 Thread Todd Lipcon (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved KUDU-2091. --- Resolution: Fixed Fix Version/s: 1.5.0 Resolved for 1.5.0. Worth noting that this applies only

[jira] [Commented] (KUDU-2033) Add a 'torture' scenario to verify Java client's behavior during fail-over

2017-08-15 Thread Mike Percy (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128092#comment-16128092 ] Mike Percy commented on KUDU-2033: -- Linking to KUDU-1188 for tracking RYW / leader leases > Add a

[jira] [Assigned] (KUDU-2100) Verify Java client's behavior for tserver and master fail-over scenario

2017-08-15 Thread Edward Fancher (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Fancher reassigned KUDU-2100: Assignee: Edward Fancher > Verify Java client's behavior for tserver and master fail-over

[jira] [Updated] (KUDU-2100) Verify Java client's behavior for tserver and master fail-over scenario

2017-08-15 Thread Alexey Serbin (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin updated KUDU-2100: Description: This is to introduce a scenario where both the leader tserver and leader master

[jira] [Updated] (KUDU-2100) Verify Java client's behavior for tserver and master fail-over scenario

2017-08-15 Thread Alexey Serbin (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin updated KUDU-2100: Description: This is to introduce a scenario where both the leader tserver and leader master

[jira] [Created] (KUDU-2100) Verify Java client's behavior for tserver and master fail-over scenario

2017-08-15 Thread Alexey Serbin (JIRA)
Alexey Serbin created KUDU-2100: --- Summary: Verify Java client's behavior for tserver and master fail-over scenario Key: KUDU-2100 URL: https://issues.apache.org/jira/browse/KUDU-2100 Project: Kudu

[jira] [Updated] (KUDU-2033) Add a 'torture' scenario to verify Java client's behavior during fail-over

2017-08-15 Thread Alexey Serbin (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin updated KUDU-2033: Description: For the Kudu Java client we have {{TestLeaderFailover}} test which verifies how the

[jira] [Commented] (KUDU-2096) Document necessary configuration for Kerberos with master CNAMEs

2017-08-15 Thread Todd Lipcon (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127962#comment-16127962 ] Todd Lipcon commented on KUDU-2096: --- If you check out the chart in KUDU-2032, you can actually see the

[jira] [Commented] (KUDU-2096) Document necessary configuration for Kerberos with master CNAMEs

2017-08-15 Thread Attila Bukor (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127878#comment-16127878 ] Attila Bukor commented on KUDU-2096: [~tlipcon] this approach wouldn't work if the user has CNAME-s for

[jira] [Commented] (KUDU-2096) Document necessary configuration for Kerberos with master CNAMEs

2017-08-15 Thread Todd Lipcon (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127875#comment-16127875 ] Todd Lipcon commented on KUDU-2096: --- It appears the JDK Kerberos implementation does some limited

[jira] [Commented] (KUDU-2032) Kerberos authentication fails with rdns disabled in krb5.conf

2017-08-15 Thread Todd Lipcon (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127869#comment-16127869 ] Todd Lipcon commented on KUDU-2032: --- Wrote a quick program to test out the different behavior of the

[jira] [Commented] (KUDU-2032) Kerberos authentication fails with rdns disabled in krb5.conf

2017-08-15 Thread Todd Lipcon (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127859#comment-16127859 ] Todd Lipcon commented on KUDU-2032: --- Just dropping a few more notes from more reading I did today: There

[jira] [Created] (KUDU-2099) Drop Java 7 Support

2017-08-15 Thread Grant Henke (JIRA)
Grant Henke created KUDU-2099: - Summary: Drop Java 7 Support Key: KUDU-2099 URL: https://issues.apache.org/jira/browse/KUDU-2099 Project: Kudu Issue Type: Task Components: java

[jira] [Assigned] (KUDU-1726) Avoid fsync-per-block in tablet copy

2017-08-15 Thread Hao Hao (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hao Hao reassigned KUDU-1726: - Assignee: Hao Hao > Avoid fsync-per-block in tablet copy > > >

[jira] [Updated] (KUDU-2033) Add a 'torture' scenario to verify Java client's behavior during fail-over

2017-08-15 Thread Alexey Serbin (JIRA)
[ https://issues.apache.org/jira/browse/KUDU-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Serbin updated KUDU-2033: Description: For the Kudu Java client we have {{TestLeaderFailover}} test which verifies how the